Stop_watchdog_Timeout issue

[Stephie_Girl]

So I've been getting 2 problems recently.

 

1.) Random freezing on the desktop, once a day or so

 

and 

 

2.) This Stop_Watchdog_Timeout popping up on windows 8 (Always after it freezes)

 

I upped the voltage to 1.38V and it seemed fine for a few days and it came back.  So now I put my CPU clock down from 4.5GHz to 4.2GHz.  This CPU ran at about 1.36V @ 4.4GHz on an H100I for about 2 years before I got it, so I hope it isn't failing.  But could it be another driver issue or a corrupted OS (I believe my OS is corrupted).

 

Thanks

Steph

[helping]

do a repair reinstall then. 

[Sarcasm]

I wouldn't think it's a CPU issue at all, so first things first, back down the voltage. I'd say a RAM or OS issue. I'd start by reinstalling the OS, but that's just because I like clean installs pretty much with the change of the seasons. Stops the crap from building up.

[Stephie_Girl]

do a repair reinstall then. 

I am thinking about wiping it and reloading it next weekend.  90% of my data is on the storage drive.

[Stephie_Girl]

I wouldn't think it's a CPU issue at all, so first things first, back down the voltage. I'd say a RAM or OS issue. I'd start by reinstalling the OS, but that's just because I like clean installs pretty much with the change of the seasons. Stops the crap from building up.

That error according to a google search and such points to a CPU core or architecture failure.  The problem is it isn't stable @ 1.35V, 1.38V it runs fine I ran AIDA64 for a little while but it would freeze instantly at 1.35V.

What's strange is that it ONLY freezes when almost nothing is happening.  Temps peak around 65*C.

[Prince32780]

You get that when your voltage is too low for your clock speed, you can lower the frequency or up the voltage, your choice.

[Ryan Leech]

That happens to me whenever I undervolt my cpu, I'm pretty sure it has to do with cpu stability.

[Stephie_Girl]

That happens to me whenever I undervolt my cpu, I'm pretty sure it has to do with cpu stability.

Ughh 1.38V isn't enough, so I lowered the CPU speed

[Prince32780]

That error according to a google search and such points to a CPU core or architecture failure.  The problem is it isn't stable @ 1.35V, 1.38V it runs fine I ran AIDA64 for a little while but it would freeze instantly at 1.35V.

What's strange is that it ONLY freezes when almost nothing is happening.  Temps peak around 65*C.

 

Are you overclocking with offset voltages?

[Stephie_Girl]

Are you overclocking with offset voltages?

On the Mpower board there is no voltage offset, only Vdroop which is set.  It was @ 4.5GHz @ 1.38V now down to 4.2GHz @ 1.38V

[Stephie_Girl]

Well I went into the Bios to move the voltage down from 1.38V to 1.35V since I lowered my clock speed and it was set to 1.35V, so I turned it back up @ 4.5Ghz and I'll see if it does it again.

[Prince32780]

I think you're trying too many configurations.

 

Pick a frequency that is fast enough for you, and optimize the voltage.

 

Windows isn't corrupt, its a common overclocking error on windows 8. I've gotten it at least 20 times.

[Stephie_Girl]

I think you're trying too many configurations.

 

Pick a frequency that is fast enough for you, and optimize the voltage.

 

Windows isn't corrupt, its a common overclocking error on windows 8. I've gotten it at least 20 times.

It's supposed to be 4.5GHz @ 1.38V.

 

Not idea why the voltage was set to 1.35V

[Prince32780]

It's supposed to be 4.5GHz @ 1.38V.

 

It's not supposed to be at a fixed voltage.

 

The amount of voltage required is different for every CPU. You'll have to keep testing with your CPU.

 

Protip: don't change your voltage and frequency simultaneously, change one at a time

[Canoas]

So I've been getting 2 problems recently.

 

1.) Random freezing on the desktop, once a day or so

 

and 

 

2.) This Stop_Watchdog_Timeout popping up on windows 8 (Always after it freezes)

 

I upped the voltage to 1.38V and it seemed fine for a few days and it came back.  So now I put my CPU clock down from 4.5GHz to 4.2GHz.  This CPU ran at about 1.36V @ 4.4GHz on an H100I for about 2 years before I got it, so I hope it isn't failing.  But could it be another driver issue or a corrupted OS (I believe my OS is corrupted).

 

Thanks

Steph

 

the watchdog timer is used in embedded systems as a reset mechanism where if every x minutes it's flagged then it assumes the system froze, so if there's a problem it'll just reset instead of freezing forever. I had no idea they implemented it in windows 8 but since they're using it on ARM as well then I guess it makes sense, but it doesn't really mean anything other than telling you the computer froze and as a result the watchdog timer deadlines was not met.

It might not be the hardware, something may not be freeing up the queue and as a consequence the computer feezes but once the watchdog timer deadline is missed it automatically takes the priority away. Does it happen often? You might want to try running an OS from a flash drive or just create a new partition for it to determine if it's really a hardware problem.

[Stephie_Girl]

It's not supposed to be at a fixed voltage.

 

The amount of voltage required is different for every CPU. You'll have to keep testing with your CPU.

 

Protip: don't change your voltage and frequency simultaneously, change one at a time

I think I bumped the voltage down for some reason.  The Mpower board doesn't allow much voltage change as it's a high end board design for 24/7 extreme OC.  CPU-Z and OCCT record it usually around 1.28-1.32V

 

EDIT: What I mean is there is no voltage offset.  Vdroop allows +12.5 +25 +37.5 etc up to 100%.  Strangely enough +12.5% actually lowers the voltage the most on idle.

[Prince32780]

leave the load line calibration on high, or whatever the equivalent to auto is on your motherboard

 

are you aiming for 4.5 or 4.8 ghz?

[Stephie_Girl]

leave the load line calibration on high, or whatever the equivalent to auto is on your motherboard

 

are you aiming for 4.5 or 4.8 ghz?

4.5GHz.

[Prince32780]

high llc (50 percent) will most likely give you the closest voltage to what you set in the bios, this may not always be the case.

 

set the voltage to manual @ 1.38v because you said it was stable at that voltage

 

now instead of going straight down to 1.35v try 1.375, then 1.370 then 1.365.. and do your normal rounds for stress testing until it is no longer stable.

 

say you get down to something like 1.355v and you get the error again, raise the voltage by .001 and try again, if it still crashes raise it by 0.001 again until it is stable

 

you might end up with a stable overclock at something like 1.358v and itll be fine for a day or two, maybe 3 or forever

 

if it crashes after that raise it by 0.002 and you will probably have a 99% stable overclock at 1.36v

 

 

 

I'm not saying your cpu will be stable at 1.36v, you have to keep testing with your particular cpu.

[Stephie_Girl]

Been on the PC all day it seems the voltage night have been the issue.  I'll give it a few days and see how much lower I can make it.

[Blake]

Typically this error means either core fault in the CPU or drivers need to be fixed (doing a quick google search on the MS website shows this).

-if you have not already do a clean install, and install the latest drivers.

-you have a hardware issue, most likely caused by the CPU.

 

I have the same thing occuring to me, but only with the Battlefield 4 Beta, so I know mine is caused by drivers (updated to the nVidia beta drivers for bf4 and the issue is resolved).

[mgsstar]

Tried updating the bios? I had a cpu timeout issue(not sure if it was this error) on stock clocks and after I updated the bios I didn't get that error anymore. Or you could just play with the voltage to remove this error.