Quick answer

CLOCK_WATCHDOG_TIMEOUT (stop code 0x101) means a secondary logical processor failed to process a clock interrupt within Windows’ timeout interval—the core hung or deadlocked. Revert any CPU overclock, AMD Curve Optimizer negative offset, Intel voltage offset, or XMP/EXPO profile to stock defaults first, check CPU temperatures under load, and update your motherboard BIOS and chipset drivers before suspecting a faulty CPU.

Fix steps

5 steps

Diagnostic workbench
Contents

At a glance

Applies to
Windows 11 and Windows 10, stop code 0x00000101
What hung
A CPU core stopped answering inter-processor clock interrupts
Parameter 4
Logs the exact logical processor index that stopped responding
First action
Reset CPU overclock / Curve Optimizer / undervolt & XMP/EXPO to stock

Provenance

  • Nov 21, 2026Published

When Windows shows CLOCK_WATCHDOG_TIMEOUT (0x00000101), one core on your CPU stopped answering the rest of the chip.

In a multi-core PC, cores coordinate constantly using hardware clock interrupts. According to Microsoft’s 0x101 reference, Windows throws 0x101 when a secondary logical processor fails to acknowledge a clock interrupt within the allotted tick count—meaning that thread is either frozen electrically (starved for voltage, overheated, or unstable at its current clock) or deadlocked at hardware interrupt level by firmware or a low-level driver.

Step 1. Read Parameter 4 in Event Viewer to see which logical core hung

Microsoft’s 0x101 parameter layout hands tuners a surprisingly specific clue before you even enter BIOS:

ParameterOfficial Microsoft fieldWhy it helps
Parameter 1 (Arg1)Clock interrupt timeout interval (in nominal clock ticks)Confirms how long Windows waited before declaring the core dead
Parameter 2 (Arg2)0Reserved
Parameter 3 (Arg3)Address of the Processor Control Block (PRCB) for the unresponsive processorInspectable in WinDbg with !prcb <Arg3>
Parameter 4 (Arg4)Index of the hung logical processorTells you which thread (0, 1, 2…) locked up—and whether the same core hangs every time

To check Parameter 4 in sixty seconds:

  1. Open Event Viewer > Windows Logs > System.
  2. Open the Kernel-Power (Event ID 41) event logged right after the reboot and switch to the Details tab.
  3. Confirm BugcheckCode reads 257 (257 decimal = 0x101 hex; if you also see BugcheckCode 292 / 0x124, pair this page with our WHEA_UNCORRECTABLE_ERROR (0x124) guide).
  4. Write down BugcheckParameter4 across your last two or three crashes:
    • Same logical processor index every time (remember SMT/Hyper-Threading gives each physical core two logical indices, such as 0/1 for Core 0, 2/3 for Core 1): strongly points to a per-core voltage/frequency deficit (like an aggressive Curve Optimizer negative offset on that core) or a single weak core at default motherboard boost limits.
    • Random core index every crash: points to an all-core voltage/power setting, memory/infinity-fabric instability, thermal runaway, BIOS microcode, or a kernel driver/virtualization lockup.

Step 2. Remove every CPU undervolt, overclock, and memory profile first

More 0x101 blue screens come from “100% stable in gaming” CPU tweaks meeting a shader-compile burst or idle C-state drop than from any other source. Test true stock before troubleshooting Windows:

  1. Clear software tuning utilities inside Windows first: if AMD Ryzen Master, Intel Extreme Tuning Utility (XTU), or a motherboard tuning suite (Armoury Crate, MSI Center, Gigabyte Control Center) applies clocks or voltage offsets at login, reset it to default and disable auto-apply on startup.
  2. Enter BIOS and run Load Optimized Defaults:
    • On AMD Ryzen (AM5 / AM4): set Precision Boost Overdrive (PBO) and Curve Optimizer back to Auto / Disabled (an aggressive -25 or -30 all-core Curve Optimizer offset is the textbook 0x101 trigger—see our Ryzen 7 9800X3D undervolt stability guide).
    • On Intel (LGA1700 / LGA1851): select Intel Default Settings (not an uncapped motherboard “Unlimited” power profile) and remove any negative Vcore / Adaptive Offset undervolt.
    • Leave XMP / EXPO off (Auto / JEDEC) during the initial test so an unstable memory controller (UCLK / FCLK / NGU) cannot masquerade as a core hang.
  3. Save & Exit, then run the exact workload (Unreal Engine 5 shader compilation, Cinebench, or game launch) that used to trigger 0x101. If the machine runs rock-solid at BIOS defaults, re-introduce XMP/EXPO alone for 48 hours before dialing back a gentler CPU curve.

Step 3. Check CPU junction temperature and cooler mounting

Modern AMD and Intel processors throttle automatically near their specified thermal ceiling (TjMax—see safe CPU temperatures by chip), yet a dead AIO pump, forgotten peel-off coldplate sticker, or dried paste can spike core temperatures fast enough under all-core AVX compilation to hang a core before clean throttling settles:

Step 4. Update motherboard BIOS (microcode / AGESA) and chipset drivers

Both Intel and AMD adjust voltage-frequency (V/F) curves, C-state boost limits, and microcode protections through motherboard BIOS updates:

  1. Check your exact motherboard model and PCB revision on the maker’s support page and flash the current non-beta BIOS / UEFI following our BIOS update guide. Note that flashing BIOS resets settings—keep stock defaults for your first 48 hours of testing afterward.
  2. Install the latest AMD Chipset Drivers (directly from amd.com) or Intel Chipset + Management Engine (ME) + Dynamic Tuning drivers from your board maker’s page so Windows schedules P-cores, E-cores, and 3D V-Cache CCDs properly.

Step 5. Rule out kernel/hypervisor deadlocks (WinDbg & DISM/SFC)

If your CPU is running at 100% stock BIOS defaults, current microcode, JEDEC memory, and normal temperatures—and 0x101 still fires:

  1. Check virtualization and anti-cheat interactions: Android emulators (BlueStacks, LDPlayer), older third-party hypervisors (older VirtualBox/VMware builds), low-level RGB/hardware-monitoring Ring-0 drivers, or overclocking remnants can deadlock a core at high IRQL. Uninstall unused emulators and monitoring overlays to test.
  2. Inspect the crash dump in Microsoft Store WinDbg: open the newest .dmp from C:\Windows\Minidump and run !analyze -v followed by !prcb <Arg3>. Check whether a non-Microsoft .sys driver was executing on the active cores at the moment of the timeout.
  3. Repair system files from Terminal (Admin):
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    
  4. Persistent stock failure on the same Parameter 4 core: if a fully stock system on current BIOS with clean thermals and freshly verified RAM repeatedly logs 0x101 (or 0x124 WHEA_UNCORRECTABLE_ERROR) on the same core index, save your Event Viewer XML logs and BIOS version details to open a processor warranty (RMA) claim with Intel or AMD.

Frequently asked questions

What causes CLOCK_WATCHDOG_TIMEOUT (0x101)?
Microsoft’s Bug Check 0x101 documentation states that an expected clock interrupt on a secondary processor in a multi-processor system was not received within the allocated interval, meaning that logical processor is nonresponsive or deadlocked. On desktop PCs, the leading triggers are an unstable CPU overclock or undervolt (such as an overly aggressive PBO Curve Optimizer offset), outdated BIOS microcode/AGESA, severe thermal throttling, or a kernel driver/hypervisor deadlock.
Does CLOCK_WATCHDOG_TIMEOUT mean my CPU is damaged?
Usually not. Any voltage setting too low for the requested boost clock will starve a core and trigger 0x101 even on a brand-new processor. Suspect physical CPU degradation or a hardware fault only when 0x101 persists at complete BIOS Load Optimized Defaults (stock CPU clocks, stock voltage, JEDEC memory, latest BIOS microcode, and healthy temperatures).
How can I tell which CPU core hung in a 0x101 crash?
Open Event Viewer > Windows Logs > System, select the Kernel-Power Event ID 41 entry from the crash, and click Details. When BugcheckCode is 257 (0x101), Microsoft’s parameter table states that BugcheckParameter4 holds the logical processor index of the hung core—useful when tuning per-core Curve Optimizer or Intel per-core ratios.
Why do I get CLOCK_WATCHDOG_TIMEOUT during shader compilation or Cinebench?
All-core AVX/shader-compilation bursts push power draw, VRM current and junction temperature simultaneously, while light-thread boost transitions test low-load voltage curves. Either edge exposes an optimistic undervolt, an uncapped motherboard power profile, or a marginal cooler mount within seconds.
What is the difference between CLOCK_WATCHDOG_TIMEOUT (0x101) and DPC_WATCHDOG_VIOLATION (0x133)?
Despite similar names, 0x133 (DPC_WATCHDOG_VIOLATION) means a software Deferred Procedure Call ran too long at DISPATCH_LEVEL—almost always a storage, GPU or network driver bug. Stop code 0x101 (CLOCK_WATCHDOG_TIMEOUT) is lower-level: a CPU core stopped processing hardware clock interrupts altogether.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 3 cited sources, listed below, each checked against the original page on the date above. The stop-code definition, Parameters 1 through 4 (timeout interval in clock ticks, PRCB address, and hung logical processor index), and WinDbg inspection commands (!analyze, !prcb, !pcr, !irql) come directly from Microsoft Learn’s Bug Check 0x101 reference opened November 21, 2026 (UTC), paired with Microsoft’s Event ID 41 documentation.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.