Share via

clock_watchdog_timeout error!

Anonymous
2013-09-03T17:52:05+00:00

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!

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-09-05T23:30:42+00:00

    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.

    Was this answer helpful?

    90+ people found this answer helpful.
    0 comments No comments

23 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-09-03T19:14:05+00:00

    Hi,

    As it is a *101 bugcheck, we'll need a Kernel dump file to properly analyze it.

    Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Check 'Small Memory Dump' to 'Kernel Memory Dump.

    Regards,

    Patrick

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-03-23T22:49:45+00:00

    Hi,

    Thx for the tip.  I was getting the "clock_watchdog_timeout" after updating, problem was the ASUS AI Suite.  Glad I found this as I nearly sent CPU back to shop! :-)

    Regards,

    Mark

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-09-03T19:34:02+00:00

    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

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-03T19:18:41+00:00

    Hi,

    As it is a *101 bugcheck, we'll need a Kernel dump file to properly analyze it.

    Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Check 'Small Memory Dump' to 'Kernel Memory Dump.

    Regards,

    Patrick

    Hi Patrick thanks for the fast reply,

    What you have mentioned is already all checked. 

    Where is the Kernel Memory Dump and how can I access it to upload here?

    Thanks.

    Was this answer helpful?

    0 comments No comments