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

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.

As I was going to do this, I got another clock watchdog error, this time while playing a different video game.

However, this time I actually got the MEMORY.dmp file! Maybe we can isolate the problem now

Here is the upload:

http://sdrv.ms/1akxjCt

What do you think? Could it be lack of power from powersupply? Or the BIOS settings as you suggested? Or is it actually the processor?

Answer 3

Hi,

The strange thing is, The system properties show that it is to make a Kernel memory dump in here (%SystemRoot%\MEMORY.DMP).

What's interesting though is I browsed the folders in my Windows drive and saw a folder called "LiveKernelReports." Within it, it has two folders, one is called USBXHCI and the other is WATCHDOG. Sounds like the 2 errors!

Anyways here's the minidump of this latest whea_uncorrectable_error:

http://sdrv.ms/14o856X

What do you think?

Thanks Patrick!

Answer 4

Hi,

If it's only showing the Minidump files, it may not be set to Kernel Memory Dump. Did the *124 WHEA generate as a Minidump in the Minidump folder, or no? If it did, please upload that to Skydrive and paste the link here.

Regards,

Patrick

Answer 5

Kernel Memory Dumps are written to %systemroot% and are named MEMORY.DMP. They are also overwritten every time you get a new crash.

They can sometimes be rather large, so any website like Skydrive, Mediafire, etc, that will allow such size will work just fine.

Regards,

Patrick

So I went to my systemroot the day of, and I couldn't find any file called MEMORY.DMP. I figured maybe it got erased.

I recently just got another error called 'whea_uncorrectable_error.'

I went into my systemroot (C:/Windows) and looked for a memory.dmp file and couldn't find one. I ran a search of the windows directly for all .dmp files and the only ones it shows are really the minidump files.

What should I do?

By the way thank you so much for your help!