My desktop randomly restarted after about 13 minutes of uptime and recorded a CLOCK_WATCHDOG_TIMEOUT (0x101) bugcheck. The system has an Intel Core i7-11700, Gigabyte B560M DS3H V2 motherboard, 64 GB of DDR4 memory, Windows 11 Pro build 26200, and Gigabyte BIOS F6 from January 2022. The system uses UEFI and is not intentionally overclocked, although XMP may be enabled.
WinDbg reports that an expected clock interrupt was not received from a secondary processor. The dump identifies logical processor 6 as the hung processor and shows PROCESS_NAME as svchost.exe, MODULE_NAME as nt, and FAILURE_BUCKET_ID as CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks. There was also a nearby DCOM timeout, though it may be unrelated.
How should I approach diagnosing this? Does the 0x101 error mainly suggest CPU, BIOS, RAM/XMP, power, or cooling instability? Is logical processor 6 meaningful, and could the old BIOS or missing CPU microcode updates be responsible? Should I update the BIOS first, disable XMP, and return settings to defaults before running memory and CPU stability tests? I would prefer to rule out configuration and other hardware issues before assuming the processor is defective.
3 Answers
Software can technically trigger or expose this bugcheck, but in practice a 0x101 is commonly associated with low-level hardware or firmware instability. The old BIOS is a reasonable first thing to address, particularly because it may update microcode for the i7-11700. Keep the troubleshooting order conservative: back up important data, update using the board manufacturer’s documented method, load defaults, disable XMP, and then test RAM and CPU separately.
If it remains stable without XMP but fails when XMP is enabled, treat the memory profile or the integrated memory controller as unstable rather than immediately blaming the CPU. If it fails at stock settings across multiple tests, then CPU, motherboard power delivery, or the power supply should be investigated or warranty-tested.
The dump confirms that processor 6 was the one reported as hung, but that number usually identifies where the watchdog noticed the problem rather than a specific permanently bad core. A single affected logical processor is not enough to condemn that core or the CPU by itself.
After updating the BIOS, check whether the system is stable at completely stock settings. Run a bootable memory test for several passes, then use a CPU stress test while monitoring temperatures, clock behavior, and voltages. Test with one memory configuration at a time if errors appear. Also verify that the cooler is mounted correctly, the CPU power connectors are secure, and the power supply is reliable. More dumps or failures under controlled testing would provide stronger evidence than this one crash.
A 0x101 usually means one logical CPU stopped responding to the expected clock interrupts. That makes CPU, firmware or platform instability more likely than an ordinary Windows driver problem; svchost.exe and ntkrnlmp.exe are generally where the failure gets detected, not proof that either caused it.
Update the motherboard BIOS first, since F6 is several years old and newer releases may contain CPU microcode and firmware fixes. Before testing, load BIOS defaults and temporarily disable XMP or any enhanced turbo, undervolting, or manual voltage settings. Then test memory and CPU stability. If the machine still produces repeatable 0x101 crashes at stock settings with adequate temperatures and power, a defective CPU or motherboard becomes much more plausible.
That makes sense. I’ll update the BIOS, reset to defaults, and test with XMP disabled before making any replacement decision. I also want to check cooling and power while I’m at it.