What is CLOCK-WATCHDOG-TIMEOUT?
CLOCK_WATCHDOG_TIMEOUT (0x00000101) is a critical-severity Windows operating system issue. The processor waited too long for a response from another processor or core and caused a BSOD. Common triggers are unstable CPU or RAM overclocking (XMP) and incorrect setting of C-states in BIOS. Use the steps below to track down and fix the cause.
Common Causes
- Unstable CPU or RAM overclocking (XMP)
- Incorrect setting of C-states in BIOS
- Defective processor (rare)
Step-by-Step Fix Guide
-
1
Disable XMP/EXPO and leave RAM at JEDEC speed
Disable XMP/EXPO and leave RAM at JEDEC speed tends to be the quickest win here, addressing the most typical cause of CLOCK-WATCHDOG-TIMEOUT.
-
2
Reset BIOS to default
If it comes back, the next steps in the sequence are there specifically for atypical windows instability cases.
-
3
Reduce CPU power in idle state (Idle)
Still seeing CLOCK-WATCHDOG-TIMEOUT after that? "Reduce CPU power in idle state (Idle)" is the next thing to check.
Commands & Diagnostics
msinfo32
Frequently Asked Questions
In most cases, unstable CPU or RAM overclocking (XMP) is behind CLOCK-WATCHDOG-TIMEOUT. Incorrect setting of C-states in BIOS and defective processor (rare) can trigger it too.
The fastest fix is "Disable XMP/EXPO and leave RAM at JEDEC speed". Only move on to the later steps if CLOCK-WATCHDOG-TIMEOUT keeps coming back.
CLOCK-WATCHDOG-TIMEOUT is rated critical severity in our database. It's worth acting on quickly rather than letting it recur.
You shouldn't need to. Work through the guide above first — a reinstall is only worth considering if none of those steps help.
Sometimes. Microsoft regularly releases patches that fix known BSOD triggers including CLOCK-WATCHDOG-TIMEOUT. Make sure Windows is fully up to date via Settings → Windows Update before attempting more advanced fixes.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database