[SOLVED] BSOD Clock watchdog timeout and Whea uncorrectable error

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Nov 6, 2020
10
0
10
I'm getting BSOD since this morning alternating between with these two errors:

WHEA UNCORRECTABLE RROR
CLOCK WATCHDOG TIMEOUT

The BSOD is always stuck at 0% and never reboots automatically. Every time I'm forced to do a manual reboot. The BSOD occurs after a few seconds or minutes after Windows boots and i'm actually able to login into the desktop

I've googled and tried pretty much every advice, this is what I did
  • Resetted bios and cmos removing battery and keeping default options
  • Disconnected any usb device except for mouse and keyboard
  • Ran sfc scannow, mdsched and chkdsk with no errors
  • Did some brief prime95 torture tests with Large and Small FFTs and nothing happened
I'm able to boot in safe mode.

For some reason windows isn't logging anything. I've looked into minidump and windows folders for dmp files but I don't find anything. I don't know where else to look.

As for PC specs, (don't know if you need it)
Motherboard Asus Maximus VI Hero
CPU Intel i7 4770K
Radeon RX580
 
Last edited:
Solution
Since yesterday, I have the same problem.
Specs:

I5 4670k
TUF Gryphon Z87
16gb of RAM ddr3 2400 MHz
RX-470

Our configuration is very similar. Coincidence? Haswell CPUs and Polaris GPUs..

I already reinstall the w10 (v2004), but after install all the things the same problem return.

Detail: I use the PC for 14 hours and no signal of BSOD. Unfortunately, after shutting down and re-start today, the problem come back.

I made every single test as possible in my hardware: RAM, CPU OC, temps, drivers (in secure mode) and programs that start with the system. Nothing fix the situation.
I've just posted another thread, with the same issue. I have an i7 4770k, but running an RTX 2070.

I did a reset of Win 10, that seemed to remove...
Went through the reset (was pleased to find out it left a file called "Removed Apps" on the desktop, will be helpful with reinstalling all my apps). PC booted up just fine afterwards and ran with no issues. Tweaked a few settings, then shut down and connected all my other drives back up. Came back up again with no issues. Then I started working through my re-installs. I added Chrome, Firefox, Dropbox, 7-Zip, KeePass, and AI Suite 3. Restarted the computer to let the changes for AI Suite take effect. Back to the BSOD. 🙁

Currently running in safe mode and going to remove the apps I added to see if one is responsible.
 
Last edited:
Went through the reset (was pleased to find out it left a file called "Removed Apps" on the desktop, will be helpful with reinstalling all my apps). PC booted up just fine afterwards and ran with no issues. Tweaked a few settings, then shut down and connected all my other drives back up. Came back up again with no issues. Then I started working through my re-installs. I added Chrome, Firefox, Dropbox, 7-Zip, KeePass, and AI Suite 3. Restarted the computer to let the changes for AI Suite take effect. Back to the BSOD. 🙁

Currently running in safe mode and going to remove the apps I added to see if one is responsible.
Would love to hear how it turns out dude, I've reinstalled most of my applications, except for AI Suite and it's still booting fine. I'm going to bed now and letting memtest run, crossing my fingers that my memory isn't an issue.
 
@CluelessPCGamer From safe mode, I was able to remove all of the apps except for AI Suite, but that didn't resolve the problem. I ended up having to run the reset again. PC is back running and I've installed just Chrome for now. But I'm starting to wonder if AI Suite may be the culprit. Curious to know if anyone else who has seen this issue may be running it as well.

The version I had installed was AI Suite 3 v1.00.56 (Win 7/8 for the Sabertooth Z87).

I'm probably gonna stay away from that app for now while adding others back on slowly.
 
Created a new account to post this... I had the same issue with similar specs:

Mobo: Asus Gryphon Z87
CPU: i7 4770k 3.5 GHz (not overclocked)
GPU: RTX 2070
RAM: 2x 8GB Patriot DDR3-1866
Main Drive: Samsung 840 Pro Series 256 GB
PSU: PC Power & Cooling Silencer MK III 850 W

When looking into safe mode we found an error with the driver for Microsoft Hyper V Virtualization Infrastructure and removing that seems to have fixed the issue (for now).
 
Status
Not open for further replies.