When I try to preview a simple FPS project (Blank with Starter Content + character + character animation), I get a blue screen from Windows with the CLOCK_WATCHDOG_TIMEOUT error message. It seems that it indicates a problem on the CPU. The interesting part is that I can constantly replicate this issue. I just need to click “Play” with “Mobile Preview” checked.
Has anyone had similar issues?
Here’s the DxDiag.txt file.
Hi quinx,
From researching around the microsoft forums, it appears this is usually resolved by a BIOS update or BIOS re-install. See this thread for other possible solutions to try before that though: Redirecting
-.
Thanks, I found that the issue was related to my CPU overheating. Bought new cooler, problem solved. Thanks for the info!
Pasting answer from Microsoft forums for posterity.
All credit goes to Microsoft Forum Moderator Patrick Barker.
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:
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 - Download Speccy | Find your computer specs, free!
Clear your CMOS (or load optimized BIOS defaults) to ensure there’s no improper BIOS setting or to clear overclock settings - How to Clear CMOS (AKA Reset BIOS Settings)
Ensure your BIOS is up to date.
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.
If all of the above fail, the only left to do is replace your processor as it is faulty.
I found a website from which i get rid out of this error problem, now you can also check it once for your this error issue from here: http://www.techinpost.com/fixed-error-clock_watchdog_timeout-code-problem