Skip to content
PCDecoder
0x00000101CLOCK_WATCHDOG_TIMEOUTStop codeWidely reported

CLOCK_WATCHDOG_TIMEOUT (0x101): what it means and how to fix it

Updated Oct 2, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This error means a secondary processor in your computer has stopped responding to system signals. It is usually caused by hardware instability or outdated system drivers. Start by checking for pending Windows updates to ensure your system firmware and drivers are current.

What it means

Understanding the CLOCK_WATCHDOG_TIMEOUT error

When you see the CLOCK_WATCHDOG_TIMEOUT (0x00000101) error, your computer has encountered a serious communication failure between its processors. Modern computers use multiple processor cores to handle tasks simultaneously. To keep everything synchronized, the main processor periodically sends a signal—a clock interrupt—to the other cores to ensure they are still active and working correctly.

This error occurs when one of those secondary processor cores fails to respond to that signal within the expected time. Windows considers this a critical failure because it cannot guarantee that the system is operating safely or correctly. When a core stops responding, it is often because it has become deadlocked, meaning it is stuck waiting for a resource that will never become available, or it has simply stopped processing instructions entirely.

While this error is technical in nature, it almost always points to a breakdown in the relationship between your hardware and the software that manages it. It is rarely a sign of a single broken piece of software, but rather a sign that the hardware is struggling to keep up with the demands placed upon it or that the instructions being sent to the hardware are causing it to freeze.

Common causes

  • Hardware instability or overheating of the processor.
  • Outdated or incompatible system drivers.
  • Corrupted system files required for processor communication.
  • Improperly configured hardware settings in the BIOS.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run Windows Update

    Use this first to ensure your system has the latest stability patches and driver updates.

    1. Select the Start button and open Settings.
    2. Go to Windows Update or Update & Security.
    3. Select Check for updates.
    4. Install all available updates and restart your computer.
    Did this fix it?

  2. Check for overheating

    Use this if your computer feels hot or the fans are running at maximum speed constantly.

    1. Ensure all air vents on your computer case or laptop are clear of dust and debris.
    2. Make sure the computer is placed on a hard, flat surface to allow for proper airflow.
    3. Verify that all internal cooling fans are spinning correctly.
    Did this fix it?

  3. Run the System File Checker

    Use this if you suspect system file corruption is causing the processor to hang.

    1. Type cmd in the Windows search bar.
    2. Right-click Command Prompt and select Run as administrator.
    3. Type sfc /scannow and press Enter.
    4. Wait for the process to complete and restart your computer if any files were repaired.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is my processor physically broken?

Not necessarily. While it can indicate hardware failure, it is more commonly caused by software conflicts, driver issues, or overheating.

Why does this happen when I play games?

Demanding tasks like gaming put a high load on all processor cores, which can trigger the error if the hardware is unstable or overheating.

Will this error damage my computer?

The error itself is a safety mechanism that stops the computer to prevent data corruption, so it is not inherently damaging, but the underlying cause should be addressed.

More stop codes decoded