Fixes / Windows · Checked

Windows CLOCK_WATCHDOG_TIMEOUT: what it means and how to fix it

Short answer

CLOCK_WATCHDOG_TIMEOUT (bug check 0x101) means one of your processor's cores stopped responding to Windows' regular timer check, so Windows halted to protect your data. The most likely cause is an unstable CPU setting. Start by resetting your BIOS/UEFI to default settings, which turns off overclocking and XMP/EXPO. Then install the latest BIOS from your motherboard or PC maker.

What this message means

Windows sends a regular timer signal (a clock interrupt) to every processor core and expects each core to respond within a set time. When one core stops responding, usually because it has frozen or is stuck waiting on something, Windows cannot continue safely. It stops with bug check 0x101, CLOCK_WATCHDOG_TIMEOUT. Microsoft's documentation describes the cause as a processor that is "nonresponsive or deadlocked". In practice that points to the CPU and what feeds it: overclocking or undervolting, voltage or firmware problems, overheating, faulty RAM, or a driver that locks up a core. Unlike most stop codes, this one points more often to hardware or firmware than to Windows itself.

Common causes

CauseHow to tell
Overclocking, undervolting or memory profiles (XMP/EXPO) that make the CPU unstableYou or the PC builder enabled an overclock, a Precision Boost Overdrive/undervolt tweak or an XMP/EXPO memory profile. The crash usually happens under load (games, video export, compiling) or randomly at idle, and stops once BIOS defaults are restored.
Outdated BIOS/UEFI or CPU microcode, including the known Intel 13th/14th Gen desktop instabilityYou have an Intel Core i5/i7/i9 13th or 14th Gen desktop CPU (such as a 13900K or 14700K), or a board whose BIOS is more than a year old. Crashes come with other odd failures, such as games or shader compiles crashing with "out of video memory" errors.
A faulty, outdated or conflicting driver (chipset, graphics, storage, network, or antivirus/anti-cheat)Crashes started right after a driver, Windows or security-software update, or after installing a game with kernel-level anti-cheat. Device Manager may show a yellow exclamation mark on a device.
Overheating or power delivery problemsThe crash happens after several minutes of heavy load. The fans are loud or the case is dusty, and monitoring tools show CPU temperatures hitting 95 to 100 °C. Crashes are more frequent on warm days or right after new parts were added.
Faulty or poorly seated RAMCrashes are random and the stop code changes between crashes (for example MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL alongside CLOCK_WATCHDOG_TIMEOUT). Windows Memory Diagnostic or MemTest86 reports errors.
Newly added hardware or USB devicesThe crashes began right after you installed a new component, dock or USB device, and stop when you disconnect it.

How to fix it

1. Remove new hardware and unplug non-essential USB devices

  1. Shut down the PC completely.
  2. Disconnect everything except keyboard, mouse and monitor (external drives, docks, hubs, controllers, webcams).
  3. If you added a component (RAM, graphics card, SSD) shortly before the crashes started, remove it.
  4. Start the PC and use it normally. If the crash stops, reconnect devices one at a time to find the one causing it.

2. Reset BIOS/UEFI to defaults (turns off overclocking and XMP/EXPO)

  1. Restart the PC and press the setup key as it starts. Usually this is Del or F2 (some brands use F10, F1 or Esc).
  2. Alternatively, in Windows 11 go to Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > UEFI Firmware Settings > Restart (Windows 10: Settings > Update & Security > Recovery).
  3. Choose "Load Optimized Defaults", "Load Setup Defaults" or similar (often F5 or F9).
  4. Make sure XMP/EXPO/DOCP, CPU overclocking, Precision Boost Overdrive and any undervolt are Disabled or Auto.
  5. Save and exit (usually F10). Stop any overclocking utilities (Intel XTU, Ryzen Master, MSI Afterburner CPU profiles) from starting with Windows.
  6. Use the PC for a day. If it stays stable, re-enable XMP/EXPO later and check whether the crashes come back.

3. Update the BIOS/UEFI firmware (critical for Intel 13th/14th Gen)

  1. Find your motherboard or PC model: press Windows key + R, type msinfo32 and press Enter. Note "BaseBoard Manufacturer", "BaseBoard Product" and "BIOS Version/Date".
  2. Go to the support page for that exact model on the manufacturer's website (ASUS, MSI, Gigabyte, ASRock, Dell, HP, Lenovo and so on).
  3. Download the latest BIOS. On Intel 13th/14th Gen desktop CPUs, choose a version that includes Intel microcode 0x12B or newer.
  4. Follow the maker's flashing instructions exactly (usually a USB stick and the built-in flash tool). Keep the PC on mains power and do not turn it off during the update.
  5. After updating, check that BIOS defaults are loaded, or load them again.

4. Install Windows updates and update chipset and graphics drivers

  1. Select Start > Settings > Windows Update > Check for updates and install everything, including optional driver updates (Windows 11: Advanced options > Optional updates; Windows 10: View optional updates).
  2. Install the latest chipset driver from AMD, Intel or your PC maker's support page.
  3. Install the latest graphics driver from NVIDIA, AMD or Intel.
  4. Right-click Start > Device Manager. For any device with a yellow exclamation mark, right-click it and select Update driver.
  5. If the crashes began right after a specific driver or Windows update, roll it back: Device Manager > device > Properties > Driver > Roll Back Driver, or Settings > Windows Update > Update history > Uninstall updates.

5. Check temperatures and test your RAM

  1. Clean dust from the fans and heatsinks, and check that all case and CPU fans spin.
  2. Watch CPU temperatures under load with a monitoring tool (such as HWiNFO). Sustained temperatures near 100 °C point to a cooling problem, such as a failed pump, a loose cooler or dried thermal paste.
  3. To test memory, press the Windows key, type Windows Memory Diagnostic, open it, and select "Restart now and check for problems".
  4. If errors are reported, test one RAM stick at a time to find the faulty one, and reseat the sticks firmly in their slots.

6. Repair system files and use System Restore

  1. Right-click Start and open Terminal (Admin) (Windows 10: Windows PowerShell (Admin) or Command Prompt as administrator).
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. When it finishes, run: sfc /scannow and restart.
  4. If crashes started recently, open Start, type "Create a restore point", open it, select System Restore and pick a point from before the problem began.
  5. If Windows crashes before you can reach the desktop, boot into Safe Mode: go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4. Uninstall the most recent driver or software from there.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the crashes continue after you've loaded BIOS defaults, updated the BIOS and tested the RAM, the processor, motherboard or power supply is probably failing. Note the exact CPU model and look in C:\Windows\Minidump for crash dump files. An IT person can open them in WinDbg with !analyze -v to see which core and driver were involved. Contact your PC maker or retailer for warranty service. Intel extended the warranty on affected 13th and 14th Gen desktop CPUs, so request a replacement through Intel if your CPU shows ongoing instability even with an updated BIOS. As a last software step, you can reset or reinstall Windows in Settings > System > Recovery (Windows 10: Update & Security > Recovery). That rules out software, but it won't fix a hardware fault.

Questions people ask

Is CLOCK_WATCHDOG_TIMEOUT a hardware or software problem?

Usually hardware or firmware. The error means a CPU core stopped responding, which most often comes from overclocking, outdated BIOS/microcode, overheating or bad RAM. Drivers can also cause it, so update them too, but start with BIOS defaults and a BIOS update.

Does CLOCK_WATCHDOG_TIMEOUT mean my CPU is dying?

Not necessarily. Most cases go away after you remove an overclock, disable XMP/EXPO or update the BIOS. If it continues with default settings, current firmware and good RAM, the CPU or motherboard may be faulty. On Intel 13th/14th Gen desktop chips, degradation is a known possibility.

Why does it happen when gaming?

Games load all CPU cores heavily and quickly change clock speed and voltage, which exposes unstable overclocks, undervolts, insufficient cooling and voltage issues. Kernel-level anti-cheat drivers can also be involved, so update the game and its anti-cheat after checking the BIOS settings.

Can XMP or EXPO cause CLOCK_WATCHDOG_TIMEOUT?

Yes. XMP/EXPO overclocks the memory and often raises memory controller voltages, which can destabilize the CPU. Disable it in the BIOS to test. If the crashes stop, try a lower memory speed or a BIOS update rather than going back to the full profile.

What is the error code number for CLOCK_WATCHDOG_TIMEOUT?

It is bug check 0x00000101 (often written 0x101). The fourth parameter in the crash dump shows the index of the processor core that stopped responding.

Sources

Related errors