Got a "clock watchdog timeout" blue screen? How do I fix and stop this from re-occuring?

Anna Rya 0 Reputation points
2024-04-09T01:10:53.5633333+00:00

Around and hour ago my laptop froze and I got a blue screen with the stop code "clock watchdog timeout". I didn't think it'd be a big deal until the percentage wouldn't move from 0%? It was stuck on 0% for 10-15 minutes while I was on my phone searching for the best way to handle this and just decided to turn off my laptop by pressing the power button.

After my laptop turned back on I checked if I had any missing updates, which I didn't, and then I did the Window's memory diagnostic which also said I didn't have any problems.

I'd like to know what caused this to happen, how to fix it, and how I can stop this from re-occurring again. And I'm not sure what exactly caused this as I was just using firefox normally, without anything in the background either.

From what I've searched and gathered, I think my BIOS has something to do with it? I'm not tech savvy so I'm not exactly sure how or why, but here is my System information if it's needed.

Screenshot 2024-04-08 200335

EjYWiutc

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,775 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,242 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li 5,040 Reputation points
    2024-04-09T07:29:14.2166667+00:00

    Hello

    CLOCK_WATCHDOG_TIMEOUT error is a Blue Screen of Death (BSOD) error that occurs in Windows systems. It usually indicates a problem with the processor or CPU.

    [Bug Check 0x101 CLOCK_WATCHDOG_TIMEOUT - Windows drivers | Microsoft Learn](https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdebugger%2Fbug-check-0x101---clock-watchdog-timeout&data=05%7C02%7Cwesleyl%40wicresoft.com%7C4f7beb1b0af44f37ea6e08dc586397a3%7Cb2ae8dd9097749768706861b488b1512%7C0%7C0%7C638482432000281984%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=46Tr4gCJtXhskhhVKsvkzn%2FvhFtWF5mv7v%2BfjL2j1fs%3D&reserved=0"原始 URL: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x101---clock-watchdog-timeout。如果你信任此链接, 请单击或点击。")

    In addition to checking for updates and memory diagnostics, you can take the following steps to troubleshoot and resolve this error:

    1.Check Hardware Connections:

    Ensure that all hardware components (CPU, RAM, GPU, etc.) are properly seated in their respective slots.

    Re-seat the CPU if necessary.

    2.Update Drivers:

    Outdated or incompatible drivers can cause this error. Update your chipset drivers, graphics drivers, and other relevant drivers.

    Use Windows Update to check for driver updates.

    3.Check for Overheating:

    Overheating can lead to system instability. Monitor your CPU temperature using tools like HWMonitor or Core Temp.

    Clean the CPU cooler and ensure proper airflow within the case.

    4.BIOS Update:

    Update your motherboard’s BIOS to the latest version. Check the manufacturer’s website for instructions.

    5.Check for Hardware Issues:

    Test your CPU using tools like Prime95 or Intel Processor Diagnostic Tool.

    6.Check Power Supply Unit (PSU):

    A faulty PSU can cause instability. Make sure your PSU is functioning correctly.

    Consider replacing it if necessary.

    7.Disable Overclocking:

    If you’ve overclocked your CPU, revert to default clock speeds and see if the error persists.

    8.Check for Malware:

    Run a full system scan using Windows Defender or a reliable third-party antivirus program.

    9.Check Event Viewer:

    Open Event Viewer and look for any critical or error events related to the CLOCK_WATCHDOG_TIMEOUT.

    Note down the details for further investigation.

    0 comments No comments