What CLOCK_WATCHDOG_TIMEOUT means

A processor core stopped responding to the clock interrupt that the system expects at regular intervals. Unstable CPU settings, such as an overclock or an aggressive per-core undervolt, are a common cause, and BIOS problems or failing hardware can also produce it.

Common causes

  • An overclock or undervolt that is not stable, including per-core offsets such as Curve Optimizer
  • An outdated or faulty BIOS version
  • CPU cooling or power delivery problems
  • A failing processor or motherboard, less often

How to fix CLOCK_WATCHDOG_TIMEOUT

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

  1. Return the PC to stock settings. Reset the BIOS to defaults, then leave XMP or EXPO, CPU or GPU overclocks and undervolts (including per-core offsets such as Curve Optimizer) switched off while you test. If the crashes stop, re-enable one setting at a time to find the unstable one.
  2. Update the BIOS. Check the motherboard or laptop maker's support page for a newer BIOS, especially after installing a new CPU generation. Read the release notes and keep the PC on stable power during the update.
  3. Watch temperatures under load. Use a monitoring tool to log CPU, GPU and drive temperatures while you reproduce the problem. Sustained high readings, loud fans or thermal throttling point to dust, failed fans or poor airflow rather than a software fault.
  4. Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
  5. Reseat the CPU cooler and check power cables. With the PC off and unplugged, check that the CPU cooler is mounted evenly and that the 8-pin or 4+4-pin CPU power cable is fully seated.
When to stop and protect your data

If the crash persists at stock settings with current firmware and good temperatures, the CPU or motherboard may be faulty and needs testing with other parts.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other hardware and cpu errors