Clock_Watchdog_Timeout BSOD Windows 10

[Swinzon]

So I received multiple BSOD`s the last week, CLOCK_WATCHDOG_TIMEOUT, googled this and it said it was a driver failure in WIndows 8 and MAY be a CPU failure in Windows 10.
My CPU is a i3 6100 Skylake, bought in August 2016.Never been OC`d as it`s a locked CPU.
Always been under watercooling by a Corsair H80i V2 so temps is not a issue.

What can have caused this?
 I don`t have any error codes, log files or anything...
Tried clean isntall of Windows, and also fresh new drives from Intel, Asus, Nvidia, Corsair etc etc, no third party crap

[another random person]

9 minutes ago, Swinzon said:

So I received multiple BSOD`s the last week, CLOCK_WATCHDOG_TIMEOUT, googled this and it said it was a driver failure in WIndows 8 and MAY be a CPU failure in Windows 10.
My CPU is a i3 6100 Skylake, bought in August 2016.Never been OC`d as it`s a locked CPU.
Always been under watercooling by a Corsair H80i V2 so temps is not a issue.

What can have caused this?
 I don`t have any error codes, log files or anything...
Tried clean isntall of Windows, and also fresh new drives from Intel, Asus, Nvidia, Corsair etc etc, no third party crap

 

 

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.

 

Source: https://answers.microsoft.com/en-us/windows/forum/windows_8-update/clockwatchdogtimeout-error/33b46641-fc90-45d9-8027-b834f44cfd03 

[slightlyjaded]

Okay, so possible issues...

 

You're running either windows 10, or windows 8, so you've got a janky AF operating system that doesn't actually work.

 

You've got a corsair water cooler that will fail after a year of use, if not sooner, and corsair will try to make you pay for their ineptitude.

 

The most common error for watchdog is a ssd that windows 8 or 10 does not directly support...Please note this is not an issue with the superceded, and outdated windows 7 that doesn't give AF what you've got in hardware.

[Mira Yurizaki]

According to https://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

 

Quote

Cause

The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

The last bit makes this annoying, because either the processor is really at fault, or it's stuck in a loop because some hardware isn't functioning. But my money is more on the processor because other hardware shouldn't be doing this.

 

EDIT:

Found something else that may point to this being a software issue: https://answers.microsoft.com/en-us/windows/forum/windows_8-update/clockwatchdogtimeout-error/33b46641-fc90-45d9-8027-b834f44cfd03

 

If you have any motherboard utilities (like ASUS's AI Suite) installed, get rid of them

[DrMikeNZ]

There are several H/W issues that can cause it. I had that error a few months ago on my system which had a faulty VRM, replacing the motherboard fixed it in that particular case.

 

Swapping out components one at a time to determine which is at fault would be recommended if that is an option.

[Swinzon]

5 minutes ago, DrMikeNZ said:

There are several H/W issues that can cause it. I had that error a few months ago on my system which had a faulty VRM, replacing the motherboard fixed it in that particular case.

 

Swapping out components one at a time to determine which is at fault would be recommended if that is an option.

Okey, thanks
May be the VRM`s failing due to overheating beacuse the B150M-PLUS isn`t that great at gaming due to lack of cooling on the VRM`s. Tend to be a bit hot under heavy load.
How is it possible to determine that I have a bad VRM or maybe something else?

 

10 minutes ago, M.Yurizaki said:

According to https://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

 

The last bit makes this annoying, because either the processor is really at fault, or it's stuck in a loop because some hardware isn't functioning. But my money is more on the processor because other hardware shouldn't be doing this.

 

EDIT:

Found something else that may point to this being a software issue: https://answers.microsoft.com/en-us/windows/forum/windows_8-update/clockwatchdogtimeout-error/33b46641-fc90-45d9-8027-b834f44cfd03

 

If you have any motherboard utilities (like ASUS's AI Suite) installed, get rid of them

Don`t use that crap
Tried calling Microsoft but they were useless as hell.
 

[DrMikeNZ]

1 minute ago, Swinzon said:

How is it possible to determine that I have a bad VRM or maybe something else?

Intermittent non-specific H/W issues like this are always a pain. Swapping parts out one at a time until the faulty component is isolated, although is tedious and time consuming, is really the only way to be sure.

It was pretty easy in my case as the VRM exploded quite spectacularly a couple of weeks after the issue started, and the replacement board worked without issues (after waiting nearly 8 weeks for the RMA process).

[Swinzon]

1 minute ago, DrMikeNZ said:

Intermittent non-specific H/W issues like this are always a pain. Swapping parts out one at a time until the faulty component is isolated, although is tedious and time consuming, is really the only way to be sure.

It was pretty easy in my case as the VRM exploded quite spectacularly a couple of weeks after the issue started, and the replacement board worked without issues (after waiting nearly 8 weeks for the RMA process).

Okey, thanks
I really hope it`s not a motherboard issue, even tho I plan to get a "gaming" motherboard due to better cooling and expandabilty for the future. 
I`ll see what I can do, I know it`s not RAM og GPU related anyways.

[slightlyjaded]

Just now, Swinzon said:

Okey, thanks
I really hope it`s not a motherboard issue, even tho I plan to get a "gaming" motherboard due to better cooling and expandabilty for the future. 
I`ll see what I can do, I know it`s not RAM og GPU related anyways.

Cause "gaming" motherboards help with compatibility...and cooling... they might actually help with expandibilty as most are fricking huge compared to what they actually offer unless you're on x99

[kirashi]

Hey @Swinzon!

If you've got small memory dumps enabled, I can analyze your minidump files and let you know if it is indeed a driver related issue.

You'll need to upload your latest minidump file, located at C:\windows\minidump, or attach the last few minidumps in a ZIP file if you've had a few recently.

I'll run them through WinDbg and see if they reveal which driver files are causing this, if there are any.

[Swinzon]

19 minutes ago, slightlyjaded said:

Cause "gaming" motherboards help with compatibility...and cooling... they might actually help with expandibilty as most are fricking huge compared to what they actually offer unless you're on x99

That`s true. But they tend to have better cooling on the VRM`s etc
 

 

16 minutes ago, kirashi said:

Hey @Swinzon!

If you've got small memory dumps enabled, I can analyze your minidump files and let you know if it is indeed a driver related issue.

You'll need to upload your latest minidump file, located at C:\windows\minidump, or attach the last few minidumps in a ZIP file if you've had a few recently.

I'll run them through WinDbg and see if they reveal which driver files are causing this, if there are any.

Hello Kirashi, thanks But There are no dumps, log files or anything avalible anymore... They`re gone :I 

[slightlyjaded]

Just now, Swinzon said:

That`s true. But they tend to have better cooling on the VRM`s etc
 

The good ones tend to spread their power better. The cooling tends to be similar

What I think you mean is the description for "x" channel power. the less power they run through each choke, the more stable, and the less fluctuation. The less crap getting fed down the pipe tends to also result in less heat and the lesser cooling needed.

 

Personally I use a x99E-WS. About the only thing you're going to get more stable and with better cooling is maybe (big maybe) a sabertooth board. Unless you're doing a serious OC then this shouldn't be an issue unless you're using some cheap peice of crap like a dell/ HP/ or acer prebuilt.

[Swinzon]

8 minutes ago, slightlyjaded said:

The good ones tend to spread their power better. The cooling tends to be similar

What I think you mean is the description for "x" channel power. the less power they run through each choke, the more stable, and the less fluctuation. The less crap getting fed down the pipe tends to also result in less heat and the lesser cooling needed.

 

Personally I use a x99E-WS. About the only thing you're going to get more stable and with better cooling is maybe (big maybe) a sabertooth board. Unless you're doing a serious OC then this shouldn't be an issue unless you're using some cheap peice of crap like a dell/ HP/ or acer prebuilt.

True that, I got the Asus B150M-PLUS which is a cheap mobo, gonna see if I can find a better one eventually

[zMeul]

1 hour ago, Swinzon said:

May be the VRM`s failing due to overheating beacuse the B150M-PLUS isn`t that great at gaming due to lack of cooling on the VRM`s. Tend to be a bit hot under heavy load.

what do you mean? from pics I saw, the VRM has a radiator on the FETs

and the 6100 is a 51W CPU. it should not be a problem powering it