clock_watchdog_timeout error!

Question

Hi!

I recently did some updates and now my computer keeps getting a clock_watchdog_timeout blue screen.

It usually happens when I play any video game, or sometimes just randomly freezing my computer.

I did some research on the error, and it mentions something about the processor. I recently updated the chipset as well with a driver. I'm running a P8P67 ASUS motherboard with an intel i5-2500k processor (not overclocked) on Windows 8.

I've attached a dmp file: http://sdrv.ms/18AzoGU

Any help would be appretiated!

Answer 1

Thanks for the DMP!

It is of course of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

Note that this is a hardware only bugcheck, most of the time. The only software that can generally cause this bugcheck are OS to BIOS utilities or software such as Asus' AI Suite that provide a direct bridge from the OS to BIOS to perform on the fly adjustments, monitor voltages and BIOS settings, etc.

If we run an !errrec on the 2nd parameter which is the address of the WER structure, we get the following:

===============================================================================

Section 2     : x86/x64 MCA

---

Descriptor    @ fffffa800dcd6138

Section       @ fffffa800dcd62c0

Offset        : 664

Length        : 264

Flags         : 0x00000000

Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 3)

  Status      : 0xbe00000000800400

  Address     : 0x000000006ba52315

  Misc.       : 0x0000000000000000

It seems an internal CPU timer failed on Processor 0 (first and primary CPU core) and Cache Bank 3. As we of course have only seen ONE *124 dumps, it's hard to make any calls in regards to the CPU possibly being the issue.

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting or to clear overclock settings - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. As I said above, the only usual software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Answer 2

I have not changed anything and after last update I am getting same message clock watch dog time out Ox80070652 and tells me to contact microsoft

Answer 3

BSOD is very annoying error which generally occurs due to some wrong configuration in the installation location of windows and you need to try 4-5 solution to fix this BSOD errors, below reference might help you out

https://wildtricks.com/clock-watchdog-timeout-windows-10-8/

Answer 4

I encountered the CLOCK_WATCHDOG_TIMEOUT blue screen error repeatedly when trying to complete a fresh Windows 10 Pro x64 installation on my PC.  I was using the OEM copy of Windows 10 I'd purchased a few months ago on Amazon.  I incorrectly assumed it would be a relatively new version of Windows 10, but it wasn't...it was dated 7/10/2015.  I simply couldn't get it to avoid the CLOCK_WATCHDOG_TIMEOUT blue screen error long enough for the OS to update and fix itself.  I tried many workarounds, but here was the fix that worked best for me:

1. Download the Microsoft Window 10 Installation Media Creation Tool from here:

https://www.microsoft.com/en-us/software-download/windows10 2. If you have a DVD burner, create an ISO.  If you don't have a DVD burner, consider using a formatted USB flash drive (at least 8GB in size) to make a bootable USB drive installer.  If you make an ISO, use this command to burn a new Windows 10 installation disc of the ISO:

ISOBURN.EXE /Q "C:\Temp\Windows10x64-v10.0.16299.iso

Note: Adjust the path in the above command to point to the Windows 10 ISO file you just created. 3. Optionally, mount the ISO (right click on it and select "Mount", or just double-click on the ISO), then use this process to confirm the Windows version of the ISO: https://answers.microsoft.com/en-us/windows/forum/windows_10-update-winpc/how-can-i-identify-os-build-number-on-an-iso/951bab96-81d5-48d0-9703-6eeb8a02f506

Note: the path used in the /WimFile command line parameter may need to be changed to "E:\sources\install.esd", where "E" is the drive letter for your mounted Windows 10 installation ISO image.

My ISO was Windows version 10.0.16299, created on September 29, 2017. 4. Optionally, compare this to the Windows version of installation disc you were originally using.  

Note: the path used in the /WimFile command line parameter may need to be changed to "D:\sources\install.wim", where "D" is the drive letter for your DVD drive.

My OEM installation disc was Windows version 10.0.10240, created on July 10, 2015. 5. Install Windows fresh from your new installation media.  With luck, you shouldn't get the CLOCK_WATCHDOG_TIMEOUT blue screen error any more.  After I installed fresh from the new ISO, my nVidia graphics card was autmatically recognized and the correct drivers installed.  When I was using the OEM installation disc, the graphics card was not automatically recognized, and I had trouble getting the drivers installed correctly.

Added bonus: since you used an up-to-date Windows 10 installer, you won't need to download or install too many Windows updates!

Answer 5

Hi!

I recently did some updates and now my computer keeps getting a clock_watchdog_timeout blue screen.

It usually happens when I play any video game, or sometimes just randomly freezing my computer.

I did some research on the error, and it mentions something about the processor. I recently updated the chipset as well with a driver. I'm running a P8P68 v Pro ASUS motherboard with an intel i7-2600k processor (not overclocked) on Windows 8.

I've attached a dmp file: http://sdrv.ms/18AzoGU

Any help would be appretiated!