i7-6700k, Nvidia 970 -> BSOD "Clock_Watchdog_Timeout"

[Hillhome]

Anyone else getting this exact BSOD when playing the game? It has happened to me twice now. I am especially interested in anyone else with the i7-6700k I have who is also having this issue. There was a lot of chatter in the betas about this error but in the open beta I did NOT get this issue.

In the full release I am getting the issue. It SEEMS to be related to the CPU timing out which could either be poor optimization of the game OR a video driver issue causing a CPU hang. If anyone has some ideas on a workaround or a fix please post them.

I am currently about to attempt setting CPU to "High Priority" and under affinity turning off core 7. Will update if that works or not as soon as my CPU test program gets done running its check (which will take a bit of time yet)

NOTE: I am not overclocking anything so to say "it's an overclock" is farking pointless. Thanks for trying to help which is appreciated ofc but that isn't it sadly. If it was it would be an easy freaking fix wouldn't it? Back down the overclock BAAAAM done.

But no. That's not possible when one isn't even overclocking to start with...

[Warcry™]

clock watch dog timout is bsod for windows 10 hello! check ur cpu temps when its at 100 percent usage if its over 80 u got a problem

[Pvt. Stash]

Clock watchdog isn't always because of overclocking. It's caused by all sorts of things, but has to do with process threading.

This guy has a fairly detailed response relating to USB plug and play drivers.
http://www.tomshardware.com/answers/id-2342759/fix-clock-watchdog-timeout-error.html

This guy is pointing to memory issues. (I've replaced memory sticks before and resolved it on my own PC)
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-blue-screen-clock-watchdog-timeout/d802a8ab-9823-464a-9f77-22343e30c94d

I had this on my work PC once where it would blow up about 30% of the time when my PC would come out of hibernation. My support staff couldn't resolve it so I wiped my partition and did a fresh OS install. It went away after that. Probably driver related.

[blackforce999]

I had this watch dog blue screen for about 20 days,
and i was over clocking for about 3 years on a 3930k and bam could not even boot
replaced it with a used 3930k and back up and running so just maybe your cpu is about to die.
but it could be a number of things.

[Anteronoid]

Hillhome님이 먼저 게시:

It's watercooled all that's fine. Just played for 2+ hours with no issues. Downloading the patch now will play also tonight. My GUESS is that something in windows was messed up and reinstalled windows fresh fixed w/e issue I was having.

A bit extreme as a fix but <shrug>

If it works for a few more hours straight tonight then I'll call it fixed. So here's what I did:

Updated my BIOS to current version
Updated chipset drivers
Deleted Partition and reinstalled Windows 10. Updated to current edition.
Installed newest Nvidia Drivers (released I think it was yesterday)
Now 2.4 gig patch being released also

Sort of a lot but it seems to have worked. Tis a silly error to have that says it's overclocking when you aren't overclocking anything though - especially odd to have it I think when the open beta worked great.

All that said ALL of my friends playing this game (and myself) see random spikes on our CPUs to 100%. It doesn't stay there & usually it's around 60% - 80% (in that range). Still odd to see the spikes though. I was watching the use % on task manager while playing the last 2.5 hours straight (no crashes or BSODs).

So really who knows what caused it but it SEEMS ok. Will test more tonight.

Great to hear!
Sometimes just doing it thoroghly fixes it, i hate doing it too but in the long run I get rid of the frustation and solve the problem faster than trying to troubleshoot it fruitlessy.

[Hillhome]

Anteronoid (VR Master Race)님이 먼저 게시:

Great to hear!
Sometimes just doing it thoroghly fixes it, i hate doing it too but in the long run I get rid of the frustation and solve the problem faster than trying to troubleshoot it fruitlessy.

Honestly it only took a couple of hours today. So far also my steam link isn't crashing yet with some games I was having issues with either. All around right now it looks like a good solution though I still feel it's a bit drastic.

I'm assuming some drivers or registry stuff was messed up and that was being triggered. I am also assuming that the 100% CPU spikes I see (which coincide perfectly with my friends when we are playing) are related to either the DRM or optimizations in the game itself. Time will tell on that because if that is the case then as patches roll out it should get fixed eventually.

[StuartAce]

Playing offline helped a lot with my cpu (I5 6600K). Still get really high cpu usage at times, it is a Ubisoft game though so thats par for the course.