[SOLVED] BSOD Clock watchdog timeout and Whea uncorrectable error

[baphomelly]

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

 

[Colif]

WHEA UNCORRECTABLE RROR
CLOCK WATCHDOG TIMEOUT

not my fav two bsod to see.

what are rest of the parts in the PC?

no dumps doesn't really help. Have you changed the page file settings as that can cause no dumps. if it doesn't have the space to write them it can't do it.
could also be pointing at storage as possible cause of bsod since its not recording a dump. Since we have no dumps, have to use any clues we get.

whea = windows hardware error architecture
its an error called by CPU but not necessarily caused by it. It can be any hardware. Sometimes drivers too...
can be caused by overclocking
can be caused by heat (so clean out inside case)
can be fixed with updating BIOS. Depends which you have, if its the release version it might help but a bios from 2014 isn't suddenly going to be needed now.

Clock watchdog timeout is also another CPU related error.

try running this on cpu - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[baphomelly]

Thanks for the reply.

What other PC parts you need to know about? I'm booting from a Samsung 850 EVO and i'm on 2x8gb ram

I'm not able to run the Intel Diagnostic Tool from safe mode.

Case is clean and temperatures should be fine. Bios is updated to its latest version and right now settings are on default and untouched. I tried to run samsung magician and SSD looks fine, but under system compatibility it prompts me to install Intel RST for better performance. I thought I had it already actually. Should I try and install RST? If positive, I see three kind of different drivers in this page

No idea about the page file settings, can I do anything to restore it and see if it logs something? If the dump would be recorded on C: as I would expect, that drive has more than 50gb free space.

 

[Colif]

PSU?
Anything can cause WHEA so knowing what you have helps identify cause.

How fast do you get the errors? at startup?

Can't run much at all in safe mode. I would at least copy anything off PC you want to save - just in case.

make this on another PC - Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Hard to check the ssd out in safe mode.

given the 2 bsod I could guess that running off a Ubuntu Live USB probably have errors too. Just trying to figure out a way to test the ssd.
Do you have another PC? Could swap ssd into it and test it there.

 

[gahmelnek]

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.

 

[CluelessPCGamer]

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 the problem. But now that you're saying it returned, I'm a bit worried.

 

[Colif]

And I answered both but tbh I doubt there is anything other than chance. CPU don't have use by dates, and the details of the rest of hardware in system is unlikely to be the same (I did check that detail when I answered 2nd thread)

@gahmelnek I would start your own question with as much info as possible and set PC to collect minidumps for next time - see 1st post here: https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

 

[baphomelly]

PSU?
Anything can cause WHEA so knowing what you have helps identify cause.

How fast do you get the errors? at startup?

Can't run much at all in safe mode. I would at least copy anything off PC you want to save - just in case.

make this on another PC - Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Hard to check the ssd out in safe mode.

given the 2 bsod I could guess that running off a Ubuntu Live USB probably have errors too. Just trying to figure out a way to test the ssd.
Do you have another PC? Could swap ssd into it and test it there.

As soon as I log into windows with password and desktop loads, I get BSOD.

PSU is a Corsair CX650M

Unfortunately I don't have another PC to test the SSD.

I'm trying to boot again in safe mode and make the USB with memtest.

I thought that since the computer runs normally in safe mode and all the tests that I've done don't show any error we can rule out the hardware fault? It isn't the case?

 

[baphomelly]

I booted from the USB with memtest and it started automatically without me having to choose any test setting. I let it run, ok?

Edit: The 9 tests passed with no errors anyway. I'm just assuming it's 9 test because the 10th one was a "rest" one and I closed it

 

[baphomelly]

Nevermind I'm actually still doing the Test 13 — Hammer test. I'll update this later with the results. No errors so far

 

[baphomelly]

3 hours of testing or so, 0 errors

Can I just restore Windows now?

 

[Symbi0tic]

Well , what do you know....
just registered in here because my perfectly stable OCed i5 4690K which has had no problem running 10hours/day every day since 2015 is now running my Windows into a BSOD just a few seconds into Windows desktop (problem started just a few hours ago).
And as if the coincidence was not enough, it is yet another Haswell CPU, running on these specs:
i5 4690K
Asus Z97 Pro Gamer
RTX2060 , so a bit different in my case (which imo rules out the GPU as the problem)

Exactly the same symptoms as the others :

• RAM tested ok with Memtest
• All overclocks removed on CPU and GPU, problem remains the same
• Boots perfectly in Safe Mode

...
I remember allowing a reboot for an update earlier this week, so maybe there's that.

Attempting a reset now, but I'm quite unhappy about losing 600Gb of apps and games ...
Also: nothing tells me if and when another update will break my install again, so I'm not very reassured about this

 

[baphomelly]

That sounds exactly like my case. Let me know how the reset goes.

You're talking about Windows update? I remember doing the same a few days ago or maybe past week. Maybe rollback to just before that update? But then what? Never update windows ever again? =)

 

[mehmetkuc]

I have almost same setup (same CPU, same Mobo , Nvidia 1080gtx gpu, 32gb ram). I also suffered the BSOD with clock watchdog timeout and luckily I could restore to a restore point to fix this. I have just updated Nvidia drivers before bsod happens. I stopped all updates currently.

 

[Symbi0tic]

I tried to do a rollback but it would not let me remove the latest feature update.

Just did the reset and it is working just fine right now (sending this message from that very computer which would crash a few seconds into the desktop).
Running all the Windows updates right now, I'll tell you how it goes.

@mehmetkuc yeah it could very well be the Nvidia drivers causing this, but in my case the latest restore point was way back and I would have lost too much stuff

EDIT: I'll install the latest nvidia drivers and tell you how it goes.

 

[baphomelly]

Were you guys able to retrieve any log/dump files?

 

[Symbi0tic]

@baphomelly as you said above:

The BSOD is always stuck at 0% and never reboots automatically. Every time I'm forced to do a manual reboot.

and

For some reason windows isn't logging anything.

These are exactly my symptoms so no luck on my side.

 

[mehmetkuc]

I am not sure there was a log since the error resourcing stuck at 0%.

 

[bcrawford]

Created an account to chime in here as well. Experiencing exactly the same issue as described above:
-BSOD shortly after windows starts (I have about 10-15 seconds before everything locks up)
-BSOD error reports either Clock Watchdog Timeout or WHEA Uncorrectable Error
-BSOD never makes it past 0% and hard reboot is needed
-No dump logs are captured
-Works fine in safe mode

I have been using my set up for roughly 4-5 years with no issues. PC worked just fine yesterday.

I was also not able to roll back the feature update, but was able to roll back the quality update. Made no difference and still get the BSOD.

What occurs with the reset? Will I lose everything I have set up on my machine?

My setup is as follows:
MOBO: ASUS Sabertooth Z87
CPU: i7 4790K
GPU: NVIDIA GTX 970
HD: Crucial 250GB SSD

 

[mehmetkuc]

Did you tried a restore point?

 

[Symbi0tic]

@bcrawford exactly the same issue as you have
Just did the reset but chose to keep my files: i kept all documents and stuff on the desktop as well as some saved games.
But most of my apps, games and saves are gone.

@mehmetkuc no change after installing nvidia drivers, it all seems to work

 

[baphomelly]

Same. Was able to rollback the quality update but not the feature update. Result, still BSOD

Was able to do a system restore to 6 days ago (the only restore point I had) and no difference, still BSOD.

The reset will maintain your files but not your apps. So not everything will be wiped.

 

[bcrawford]

Geez, super frustrated with this one. I guess I'll kick off the reset on this and see how that goes.

The only good thing is that I mostly only keep Windows specific files on my boot drive (have separate drives for games, videos, pics, etc).

I'll let you know how it turns out. Good luck to you guys and hopefully you can get your machines back up and running without too much trouble.

 

[Symbi0tic]

Ok after the reset I just put back the OC on the CPU just as it was, reinstalled nvidia drivers, MSI afterburner for monitoring, Steam and a small yet demanding game (Astroneer).
Boom. It all works and seems stable, I just can not figure out why this happened.

 

[CluelessPCGamer]

Ok after the reset I just put back the OC on the CPU just as it was, reinstalled nvidia drivers, MSI afterburner for monitoring, Steam and a small yet demanding game (Astroneer).
Boom. It all works and seems stable, I just can not figure out why this happened.

Did something similar. Although I threw the most demanding game I have after it (Star Citizen), played for 1½ hours, and aside from the buggy mess of the game itself, my PC ran just fine. Even tried restarting it a couple of times to see if I could reproduce the BSOD, so far, nothing.