Computer crashing occasionally. Got clock watchdog timeout black screen for first time.

Check Event Viewer for Event ID 1001 and analyze the corresponding crash dump, because those records can identify whether Windows captured the CLOCK_WATCHDOG_TIMEOUT stop error and what code or driver was executing at the time.

CLOCK_WATCHDOG_TIMEOUT is bug check 0x00000101: Windows did not receive an expected clock interrupt from a secondary processor within the allowed interval, typically because that processor was unresponsive or deadlocked. The stop code alone does not establish whether the underlying problem is firmware, hardware, overclocking, or a driver. ^1^

1. Correlate the crashes in Event Viewer

1. Right-click Start → Event Viewer.
2. Open Windows Logs → System.
3. Select Filter Current Log.
4. In Event IDs, enter:

      19,41,1001,1074,6008,7045
   

5. Find records at the exact times of the freezes and restarts.

Interpret them as follows:

• 1001, WER-SystemErrorReporting: Windows restarted from a bug check. Its details normally show the bug-check code, four parameters, and the saved dump path.
• 41, Kernel-Power: Windows did not shut down cleanly. By itself, this does not identify the cause.
• 6008, EventLog: the preceding shutdown was unexpected.
• 1074, User32: software or a user initiated an orderly restart.
• 19 or 7045: an update or newly installed service may help establish what changed shortly before the crashes began. ^2^

Also use Find in the System log to search for source:

Microsoft-Windows-WHEA-Logger

WHEA-Logger is Windows’ provider for recorded hardware-error events. Save the event’s ID and full General and Details text if one occurred immediately before a crash. ^3^

The Event ID 41 generated after the forced power-off may simply record that Windows did not shut down cleanly. A nonzero PowerButtonTimestamp indicates a long power-button shutdown, so do not treat that event alone as the original fault. [^4^](https://learn.microsoft.com/troubleshoot/windows-client/performance/event-id-41-restart#more-information "Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"")

2. Locate and analyze the crash dump

Check these locations:

C:\Windows\Minidump
C:\Windows\MEMORY.DMP

Copy any .dmp file to the Desktop before opening or sharing it. A small dump includes the stop parameters, loaded drivers, processor context, and kernel call stack, although it may not identify faults outside the thread that was executing. ^5^

To inspect it with WinDbg:

1. Start WinDbg.
2. Select File → Open Crash Dump and open the dump.
3. In the command window, run:

      !analyze -v
      .bugcheck
      lm
   

4. Record these fields from !analyze -v:
   • BUGCHECK_CODE
   • the four bug-check arguments
   • MODULE_NAME
   • IMAGE_NAME
   • FAILURE_BUCKET_ID
   • the stack trace

!analyze performs the initial automatic analysis, while .bugcheck displays the bug-check code and parameters. ^6^

Do not assume that a Microsoft kernel component named in the output caused the failure; the complete stack and repeated results across multiple dumps are more useful than a single filename.

3. If no dump was created

Configure Windows to retain one for the next crash:

1. Search for View advanced system settings.
2. Open Advanced → Startup and Recovery → Settings.
3. Set Write debugging information to Small memory dump (256 KB).
4. Leave the directory as:

      %SystemRoot%\Minidump
   

5. Restart Windows.

Crash-dump creation requires a paging file on the boot volume. ^7^

If Event ID 41 has zero bug-check values, check nearby events for volmgr Event ID 46, “Crash dump initialization failed.” That points to dump/page-file configuration rather than proving that no stop error occurred. [^4^](https://learn.microsoft.com/troubleshoot/windows-client/performance/event-id-41-restart#more-information "Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"")

4. Conditional next checks

If no useful dump exists and Event ID 41 contains zero bug-check data, return the system temporarily to its default configuration:

• Disable CPU/GPU overclocking or undervolting, including automatic tuning profiles.
• Check CPU temperature under load.
• Check the power supply’s capacity and connections.
• Install current Windows updates and hardware drivers from the PC or component manufacturer.

Microsoft’s Event ID 41 guidance identifies default clock settings, memory, power, and overheating as relevant checks when Windows cannot record a bug-check code. [^4^](https://learn.microsoft.com/troubleshoot/windows-client/performance/event-id-41-restart#more-information "Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"")

Avoid enabling Driver Verifier at this stage. It deliberately stresses drivers and can cause additional crashes; use it only if several dumps remain inconclusive and after creating a restore point.

When sharing a dump publicly, use a temporary link and remove it afterward: crash dumps can contain portions of memory and potentially sensitive data.

References

1. Bug check 0x101: CLOCK_WATCHDOG_TIMEOUT
2. Troubleshoot unexpected reboots using system event logs
3. Querying the System Event Log for Hardware Error Events
4. Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
5. How to read the small memory dump file that is created by Windows if a crash occurs
6. Analyze a kernel-mode dump file by using WinDbg
7. Configure system failure and recovery options in Windows