CLOCK_WATCHDOG_TIMEOUT (0x00000101)? A CPU Core Stopped Responding
Your PC blue-screens with CLOCK_WATCHDOG_TIMEOUT (stop code 0x00000101).
Why: Microsoft’s bug-check page says 0x101 “indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, wasn’t received within the allocated interval.” Its cause section is blunt: “The specified processor isn’t processing interrupts. Typically, this bug check occurs when the processor is nonresponsive or is deadlocked.” That points at the CPU and what drives it — overclocks, firmware, and low-level drivers — not generic file corruption.
Fix 1: Undo CPU overclocking and reset BIOS defaults
A core deadlocking under an unstable overclock is the classic 0x101 trigger.
- Reboot and enter BIOS/UEFI (usually Del or F2 at startup).
- Disable any CPU overclock and reset to optimized defaults.
- Turn off XMP / EXPO memory profiles to run RAM at stock speed — unstable memory can also hang a core.
- Save, exit, and see if the crashes stop.
Fix 2: Update the BIOS/UEFI and chipset drivers
CPU stability and microcode fixes ship in firmware and chipset updates.
- On your PC or motherboard maker’s support page, install the latest BIOS/UEFI for your exact model (follow their flashing steps precisely).
- Install the latest chipset drivers from the same maker.
Fix 3: Update low-level drivers and undo recent changes
A buggy kernel-mode driver can stall a core too.
- Press Win + X → Device Manager and update drivers for storage, network, and the GPU from the hardware makers.
- If the crashes started after a recent driver update, roll it back: device Properties → Driver → Roll Back Driver.
- Uninstall recently added low-level software (overclocking utilities, monitoring tools, third-party antivirus) to test.
Fix 4: Check cooling, power, and the CPU itself
A nonresponsive core can be a genuine hardware fault.
- Make sure the CPU isn’t overheating — check the cooler is seated and fans/vents are clean.
- Confirm the PSU is adequate and power connectors are firmly seated; instability under load can hang a core.
- Run the hardware diagnostics your PC or motherboard maker supplies, and the Windows Memory Diagnostic (
mdsched.exe) to rule out RAM.
FAQ
Will SFC or DISM fix CLOCK_WATCHDOG_TIMEOUT? Usually not. 0x101 is a processor that stopped responding — a hardware/firmware/driver problem — not corrupted system files. Start with the overclock and BIOS fixes.
It only happens under heavy load or gaming. That fits an unstable overclock, inadequate cooling, or an underpowered PSU — work through Fixes 1 and 4.
Sources: Microsoft Learn — Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT