Windows stopped with a CLOCK_WATCHDOG_TIMEOUT (bug check 0x00000101) because an expected clock interrupt was not received by a secondary processor within the allocated interval. This indicates that a processor in the system has stopped or is stuck, and the primary processor's watchdog has detected the hang. It is predominantly a hardware issue — most commonly caused by CPU overclocking, faulty RAM, or a failing CPU.
CPU overclocking or aggressive performance settings in BIOS/UEFI are causing one or more CPU cores to become unresponsive.
Faulty or incompatible RAM is causing memory access failures that stall a CPU core.
The CPU is overheating, causing a core to throttle or hang.
A BIOS/UEFI firmware bug or incompatible power/performance settings are causing inter-processor clock interrupt failures.
Rarely, a hardware fault in the CPU itself causes a core to stop responding.
How to fix it
Disable all CPU overclocking in BIOS/UEFI and reset to stock settings. Disable XMP/EXPO memory profiles and run memory at its base speed to eliminate instability.
Check CPU temperatures under load using HWiNFO64 or CPU-Z. Clean the cooler, reseat it, and reapply thermal paste if temperatures are high.
Run MemTest86 from USB for multiple passes to test RAM. Replace any faulty modules.
Update BIOS/UEFI firmware — many CLOCK_WATCHDOG_TIMEOUT crashes are caused by firmware bugs fixed in updates, especially on newer AMD or Intel platforms.
In BIOS, check that CPU power limits (PL1/PL2 on Intel, TDP limits on AMD) are not set to extreme values causing instability.
Run `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth` to rule out system file corruption as a contributing factor.
If the issue persists after all above steps, test with known-good RAM, and contact the CPU or motherboard manufacturer if hardware fault is suspected.
