The Problem

CLOCK_WATCHDOG_TIMEOUT (stop code 0x00000101) means one CPU core sent an interrupt to another core and never got a reply within the expected window. Windows assumes that core has hung and stops everything.

In practice that comes from three places: the CPU is running outside its stable envelope (overclock, undervolt, bad memory timings), a driver is holding an interrupt for far too long, or the processor is overheating and stalling. It is a processor-level stop code, so software-only fixes rarely help on their own.

Getting a different stop code each time? That pattern points at RAM or power — start with how to fix a BSOD. Hardware reporting its own faults? See fix WHEA_UNCORRECTABLE_ERROR.

Symptoms

Blue screen reading CLOCK_WATCHDOG_TIMEOUT, often within seconds of a heavy task starting.
Crashes during gaming, rendering, compiling, or a large file copy — anything that loads every core.
The PC hangs completely for a second or two before the blue screen appears.
Repeats even in Safe Mode, which effectively rules out most third-party software.

Step 1: Return the CPU and Memory to Stock Settings

An unstable all-core overclock or an aggressive undervolt is the leading cause of this exact stop code.

Enter firmware setup: how to enter BIOS or UEFI.
Choose Load Optimized Defaults.
Leave XMP / EXPO off for the first test — memory instability shows up as a CPU-side timeout surprisingly often.
Reset any undervolt curve in Intel XTU, Ryzen Master, or ThrottleStop back to default and close the tool so it does not reapply at startup.
Save, exit, and load the PC hard for 20 minutes — a game or a video export is a good test.

Stable at stock? Reintroduce one setting at a time, testing for a day between changes.

Step 2: Confirm the CPU Is Not Overheating

Open Task Manager → Performance → CPU and note the base and current speed.
Install HWiNFO or your motherboard vendor's monitor and record peak core temperature during load.
Anything sustained above 95 °C, or a clock that collapses far below base speed under load, means cooling.
Clean the heatsink and fans, and check the cooler is properly seated: fix CPU overheating and thermal throttling and clean your laptop and devices safely.

Step 3: Read the Crash Dump to Name the Culprit

Press Windows + R, type eventvwr.msc, press Enter.
Filter Windows Logs → System for source BugCheck and read the parameters recorded with each crash.
Check that dumps are actually being written: Windows + R → sysdm.cpl → Advanced → Startup and Recovery → Settings → set Write debugging information to Small memory dump (256 KB).
Dumps land in C:\Windows\Minidump. If a specific .sys file is named repeatedly, that driver is your target — see Step 4.
Full method: how to use Event Viewer to find why your PC crashed.

Step 4: Roll Back or Reinstall the Named Driver

Chipset, storage, and GPU drivers are the usual offenders.

Right-click Start → Device Manager.
Find the device matching the .sys file from the dump, right-click → Properties → Driver tab.
If Roll Back Driver is available, use it and reboot.
If not, choose Uninstall device, tick Attempt to remove the driver, reboot, and install the current version from the vendor's site.
For graphics drivers specifically, do a clean removal: clean install GPU drivers with DDU.
General guidance: how to update outdated drivers.

Step 5: Update Motherboard Firmware

Microcode updates for newer CPUs ship in BIOS releases and fix exactly this class of core-synchronisation fault.

Windows + R → msinfo32 → note System Model and BIOS Version/Date.
Get the latest BIOS from the motherboard or laptop manufacturer's support page.
Install the matching chipset driver first, reboot, then flash the firmware following the vendor's instructions.
Never interrupt a firmware flash. On a laptop, keep it plugged in and above 50 % battery.

Step 6: Test the Memory

Bad RAM produces this stop code even though the CPU is what reports it.

Windows + R → mdsched.exe → Restart now and check for problems.
Press F1 during the test and set Test Mix to Extended.
For a real answer, run MemTest86 from USB for four passes or more.
Any error means bad memory or an unstable memory profile. Test sticks individually.
Related: fix MEMORY_MANAGEMENT BSOD and check and upgrade your RAM.

Step 7: Disable Fast Startup and Test a Clean Boot

Open Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable.
Untick Turn on fast startup (recommended) and save. This forces a full cold boot each time so hardware is initialised cleanly.
Windows + R → msconfig → Services → tick Hide all Microsoft services → Disable all.
In Task Manager → Startup apps, disable everything, then reboot.
Pay particular attention to RGB, fan-control, and monitoring utilities — they install kernel drivers that can stall interrupts. More on this: disable startup programs.

Step 8: Repair Windows and Test Power Delivery

In Terminal (Admin):

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Reboot and re-run sfc /scannow. Step-by-step: how to run SFC and DISM.
On a desktop, reseat the 8-pin EPS CPU power connector at both ends — a partially seated connector causes core stalls under load.
On a laptop, test with the original charger only.

What Not to Do

Don't disable CPU cores or hyperthreading as a "fix". It masks instability and cripples the processor.
Don't raise CPU voltage blindly to chase stability — you will trade blue screens for degradation.
Don't reinstall Windows before testing stock settings and RAM. This stop code survives clean installs when the cause is hardware.

Still Not Working?

If the PC crashes at stock settings, with one RAM stick, with clean drivers and current firmware, and temperatures are normal, the CPU or motherboard VRM is the remaining suspect. Test the same drive and RAM in another machine if you can, and get your data backed up first: set up automatic backups.

How to Fix CLOCK_WATCHDOG_TIMEOUT in Windows 11