Bad overclock or something else?

SsystemXx

[H]ard|Gawd
2FA
Joined
Aug 25, 2010
Messages
1,124
Randomly, like every few weeks to a month, I'll restart my PC or boot it up from a shut-down state and will get a boot failure message while trying to boot-up. It is not a SSD/HDD boot failure but a BIOS boot failure. When I get the message, there are options that allow me to load optimized BIOS defaults or enter the BIOS to make changes. This only started happening after I overclocked my CPU to 4 GHz. By the way, if I get the message and select the "enter BIOS" option, I just save and exit it without making any changes and it works fine after that (till the next boot failure). Using Windows and gaming is fine.

Here are my voltages:

3930K at 4 GHz: 1.205 volts
DRAM (DDR3-2133 CAS 9): 1.5 volts
IMC: 1.000 volts
VTT: 1.05 volts

I upped my Vcore to 1.210 volts to see if it makes any difference.
 
Do you have any problems when running stock?

How old is the CMOS battery?
I had a mobo years ago that was experiencing the same thing and in the end it was a weak battery.
 
Last edited:
Probably a bad overclock, yes. First thing you do when you have problems with an overclocked computer is set everything back to stock and see if it goes away. If it does, then it's an overclocking issue.

Do that, set all clocks to stock and see if the problem goes away.
 
Do you have any problems when running stock?

How old is the CMOS battery?
I had a mobo years ago that was experiencing the same thing and in the end it was a weak battery.

This my friend, is solid advice. I experienced this yesterday on a new build that I was making for my mom. Powering off the computer completely and shutting off power to it (via surge protector) would make the board lose all settings and reset to default. It was the BIOS battery that went bad.

The second is that it is indeed a bad overclock, either due to improper support by the motherboard, or the PSU is just not up to the task. I figured this out the hard way. I was installing an Intel E8200 into a Asus P5B-VM SE. According to Asus, it's supported. This is not entirely true, at least in my case. While you can get the computer to work, NONE of the power features work, either sleep or hibernate. The computer could not enter S3 properly and you'd have to hard reset, or when hibernating the computer would wake itself right back up. Removing that CPU and installing an E2180 fixed everything, which means either the PSU was too weak or the board just wasn't properly compatible.
 
Last edited:
Thanks for the replies.

I asked the same question on another forum and most also said it could be a bad CMOS battery. I built/bought all my parts in January, 2012 and it has been running since. So about 4 years on my motherboard.

As for the overclock, everything was fine with my 3930K running at 3.8 GHz with a Vcore of 1.200 volts. I upped to 4 GHz and changed to Vcore to 1.205 volts because there were some instabilities in games. With a Vcore of 1.205 volts, gaming was fine again. Then this issue started happening. Now I've upped the Vcore to 1.210 volts and will see if it happens again. However, with my original Vcore of 1.205 volts and the overclock at 4 GHz, I had no issues in Windows or while gaming.
 
Has the temperature changed in the room housing the PC?

Not really. During the summer, the A/C is on 24/7. In the winter (like these days), the A/C is off but the room is pretty much the same temp as during the summer with the A/C on.
 
Hello,

I have a new PC with Windows 10 and ASUS® SABERTOOTH X99: ATX, USB 3.1, SATA 6 GB/s

Frequently the log on process gets locked and I am forced to switch off and on the PC some time a couple of times. When I inspect the event log the only warning event that I see is:

Source: Kernel-PnP
Event ID: 219
Task Category: (212)
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2.

and one or two seconds after that, I have:
Source: Eventlog
Event ID: 6008
Task Category: None
The previous system shutdown at Time on Date was unexpected.

The two appear correlated even though I get the first one always and the second one when the log on process locks up.

Anyone else experiencing this same problem ? any solution to this annoying problem ?

Thanks a lot in advance.
 
Well, it's been a little over a month running 4 GHz @ 1.210 volts instead of 4 GHz @ 1.205 volts. No more boot failures (so far).
 
Okay, it's still happening. I even upped the Vcore to 1.215 volts and it still happened. Seems it's not the Vcore. By the way, when it happens, the BIOS time is not wonky or incorrect. Can I rule out a bad BIOS battery? I removed my overclock. My 3930K is now at 3.8 GHz at 1.200 volts. Can a 200 MHz overclock really cause this?

One more thing. As I stated before, it only happens during a restart or boot up (and even then only once a month or once every few months). I can leave the PC on all day and night and it will run fine. No BSODs, no crashes, no auto-restarts, etc.
 
What kind of PSU do you have? Some Corsair and Seasonic units can introduce boot issues with some boards.
 
AX850. However, I've had this build since 2012 and it only recently started happening.
That chip should have enough headroom for that clockspeed. Especially with a VCore high like that.
I think if it happens on bootup it's probably a memory related problem.
Eventually the board boots up because it manages to find fail-safe timings by trial and error.
You may have an outdated BIOS that can't read the memory specs correctly and adjust timings.
The 200MHz overclock can do this because the baseclock is tied to the memory clock. Touching BCLK raises the memory speed. Try dropping your memory multiplier or bumping up the DDR and IMC voltages.

Edit: Not battery because wrong era, but you can use a cheapo voltmeter to check it out of board
Edit2: Not PSU because fairly new Corsair and it would shutdown during use, too.
 
That chip should have enough headroom for that clockspeed. Especially with a VCore high like that.
I think if it happens on bootup it's probably a memory related problem.
Eventually the board boots up because it manages to find fail-safe timings by trial and error.
You may have an outdated BIOS that can't read the memory specs correctly and adjust timings.
The 200MHz overclock can do this because the baseclock is tied to the memory clock. Touching BCLK raises the memory speed. Try dropping your memory multiplier or bumping up the DDR and IMC voltages.

Edit: Not battery because wrong era, but you can use a cheapo voltmeter to check it out of board
Edit2: Not PSU because fairly new Corsair and it would shutdown during use, too.

Already have the latest BIOS and they don't do any more updates for my motherboard (X79). I'm overclocking by increasing the multiplier, not the BCLK.
 
Already have the latest BIOS and they don't do any more updates for my motherboard (X79). I'm overclocking by increasing the multiplier, not the BCLK.

Okay, your problem is an odd one.
Double check: bios battery, a slightly lower OC (50-100 MHz).
Likely culprit: the CPU! First time I'm suspecting the CPU btw. Bump the IMC by a small increment, 0.05 or 0.1.
 
Okay, your problem is an odd one.
Double check: bios battery, a slightly lower OC (50-100 MHz).
Likely culprit: the CPU! First time I'm suspecting the CPU btw. Bump the IMC by a small increment, 0.05 or 0.1.

I only did a very minor overclock to 4.0 GHz from the stock 3.8 GHz. That is when I first started encountering the issue. I have now reset my overclock and returned to the stock 3.8 GHz. I'll keep it like this for a while and see if it happens again. If it does, I'll replace the CMOS battery. If it still happens again, I'll be a little scared. :eek:
 
X79 is a finicky platform. My Asus won't post after sleep if OCed past certain level so I had to resort to hibernate. Another MSI X79 build I've done had its own set of quirks. Try setting all voltages to manual (not offset, auto or anything similar) and bump them a bit more over the stock values. Have you changed anything regarding the memory? XMP profile active?
 
I only did a very minor overclock to 4.0 GHz from the stock 3.8 GHz. That is when I first started encountering the issue. I have now reset my overclock and returned to the stock 3.8 GHz. I'll keep it like this for a while and see if it happens again. If it does, I'll replace the CMOS battery. If it still happens again, I'll be a little scared. :eek:
If everything is fine at stock (max turbo?), and please make triple sure it is, then it's - again - a memory issue.
I'm assuming you have a Gigabyte. A few of them which I've seen do have trouble booting up when you stray away from the preset speeds.
If you are rock solid at stock, and the issue only makes itself known on cold bootup, it's a memory (DRAM or the Integrated Memory Controller) or motherboard (timing management?) problem.
I once had a GB board which would only boot overclocked (even by 1MHz) only on one version of some random beta BIOS. You may have to iterate over a few older BIOSes...
 
If everything is fine at stock (max turbo?), and please make triple sure it is, then it's - again - a memory issue.
I'm assuming you have a Gigabyte. A few of them which I've seen do have trouble booting up when you stray away from the preset speeds.
If you are rock solid at stock, and the issue only makes itself known on cold bootup, it's a memory (DRAM or the Integrated Memory Controller) or motherboard (timing management?) problem.
I once had a GB board which would only boot overclocked (even by 1MHz) only on one version of some random beta BIOS. You may have to iterate over a few older BIOSes...

Yep, I too suspected a memory issue as it only started occurring after I overclocked the CPU. Pretty sure it is the IMC voltage that needs to be increased with the overclock. I'm going to try stock CPU clocks for a while and if it doesn't happen again it pretty much guarantees it's the RAM.
 
So, it happened again just now during a restart. This is at stock CPU clocks. I'll replace the CMOS battery but I wonder if my IMC is starting to show wear after running DDR3-2133 after all these years. This is supposedly quite a high MHz for RAM for X79.
 
Just changed the battery. Let's see how this goes. I also re-entered my overclock of 4 GHz at 1.200 volts.

By the way, when I restarted my computer today (before changing the battery) after having it run all night long, the same BIOS reset thing happened but instead of showing some options on the screen for BIOS reset and "enter BIOS to reconfigure settings", the computer just shut down after showing a blank screen for a while.
 
Just happened again and this is with the new battery. When I restarted my computer this morning after being left on all night, I had a blank screen on my monitor for maybe 4-5 seconds and then the computer shut down. It then turned itself on and I got the BIOS message saying to enter the BIOS and reconfigure settings or load the optimized defaults. I am pretty sure it is memory related. I have increased my IMC voltage from 1.000 volts to 1.020 volts. The rest of my voltages are as follows:

3930K at 4 GHz: 1.200 volts
DRAM (DDR3-2133 CAS 9): 1.5 volts
VTT: 1.05 volts

By the way, I noticed one thing today. After I reset my BIOS and re-entered the settings, I entered into the BIOS a noticed my RAM was running at 2147 MHz instead of 2133 MHz which XMP specifies. It was only for a second or so and then it returned to 2133 MHz. I wonder if, on random occasions, the RAM MHz frequency is jumping up over the rated speed during a restart or boot up causing a BIOS boot failure?
 
I think that if your IMC was failing, you wouldn't be able to keep the machine stable, and if I am reading correctly, it only fails on bootup?
Crap, this is a frustrating gremlin problem you have there.
At this point I'd be stabbing blindly so hopefully someone more current can chime in. I'll just leave one other suggestion - have you tried switching CAS to 10?
 
To be sure its memory related I would reduce the memory speed 10% ish and see if it improves.
Work from there.

Its also worth removing the memory and cleaning contacts on the ram sticks.
 
I haven't just yet started to play with RAM timings and latencies, but did do the following:

Okay, I reset my voltages to what they were set at when the last BIOS boot failure happened. They are as follows:

3930K at 4 GHz: 1.200 volts
DRAM (DDR3-2133 CAS 9): 1.5 volts
IMC: 1.000 volts
VTT: 1.05 volts

I ran MemTest86 for four hours and it reported no errors. As soon as I quit MemTest86 and restarted my computer to boot into Windows, boom: BIOS boot failure.

I have now increased the IMC voltage to 1.05 volts (i.e. matching the VTT voltage) and will see if it makes a difference. Note that this whole issue started as soon as I overclocked my processor for the first time to a mild 4 GHz. I even removed my overclock for a while and tested to see if it would happen again and it did. So, apparently, it is not the overclock.

I read around on the Internet searching for "intermittent BIOS POST failure" and quite a few people stated it could be the motherboard or power supply going bad. Not sure what to make of this. I can game all night long and all is fine. If I decide to restart the computer, it will *sometimes* result in a BIOS boot failure message.
 
Well, it's been a little over a month running 4 GHz @ 1.210 volts instead of 4 GHz @ 1.205 volts. No more boot failures (so far).

I applaud your resolve at this point :D

It's disappointing you were left with a weird problem like that.
It seems all of your hardware is perfectly fine, and so is the firmware (bios).
It really sounds like you're one of the few people that hit some unworkable memory<->chipset combo. Reminds me of the nvidia 6xx chipset days.
I think it's new mobo time :(
 
I applaud your resolve at this point :D

It's disappointing you were left with a weird problem like that.
It seems all of your hardware is perfectly fine, and so is the firmware (bios).
It really sounds like you're one of the few people that hit some unworkable memory<->chipset combo. Reminds me of the nvidia 6xx chipset days.
I think it's new mobo time :(
Did you go through a time warp?
 
I bet someone will notice me quoting a past post and ask if I'm living it up - backwards!
 
Yep, I too suspected a memory issue as it only started occurring after I overclocked the CPU.

Gee, it's almost like pushing your components out of spec can cause bad things to happen!

Why spend $50 to get a slightly faster CPU at the time of build when you can just risk everything inside your case for free?!
 
Gee, it's almost like pushing your components out of spec can cause bad things to happen!

Why spend $50 to get a slightly faster CPU at the time of build when you can just risk everything inside your case for free?!

Have you even been reading what I've been posting? What processor was faster than my 3930K for $50 when it was new? Next step up was the 3960X for an additional $500 for a very marginal performance increase. Make sure you have everything down before you start schooling someone.

I'm actually surprised you think an overclock of 200 MHz while keeping the Vcore at stock could damage the CPU. This probably isn't even qualified to be called "an overclock" on this forum.
 
His comment made little sense, I decided to leave him to it.
Not worth considering.
 
Increasing the IMC voltage didn't help. Also tried increasing the DRAM voltage and that didn't help either.
 
Overclocked my 3930K to 4.2 GHz. I started at 1.200 Vcore and ran IntelBurnTest at the maximum stress level. Kept increasing the Vcore till the BSODs stopped. They eventually stopped when I set a Vcore of 1.230 volts. Let's see how this turns out.
 
Just happened again. I've noticed one thing though. During a successful POST boot, during the POST the fans in my case, including the H100's fan's, run at a very slightly lower speed and once the POST is completed successfully they run at their full required speed. During to a boot/restart that results in a BIOS boot failure, the fans would be running at an even lower speed as if the computer is not getting enough power. Basically, I've noticed that boots/restarts that result in a BIOS boot failure message all the fans in my case would be running at a lower speed than normal as if the computer is not getting enough power. Bad power supply or motherboard?
 
Happened today again but this time during POST the computer shut down. Left the computer on during the night and when I restarted it this morning, the computer shut down during POST. When I turned it back on, I got the BIOS boot failure message that I always get when this happens. Seems all this is more likely during a warm boot/restart instead of the cold boot/restart.

I will try to loosen RAM timings or reduce the RAM clock speed.
 
Ran MemTest86 overnight with XMP enabled. Completed 4 passes in 6 hours and 30 mins with no reported errors. As soon as I restarted the computer, I encountered the BIOS boot failure message. I even tried disabling XMP and running my RAM at 1333 MHz and still encountered the BIOS boot failure message during a restart. I guess it's not the RAM. Right now I have changed my LLC setting in the BIOS from Auto to Medium. Let's see if it helps.

Also found this thread with a similar issue: 2500K Occasional POST Failure
 
During to a boot/restart that results in a BIOS boot failure, the fans would be running at an even lower speed as if the computer is not getting enough power. Basically, I've noticed that boots/restarts that result in a BIOS boot failure message all the fans in my case would be running at a lower speed than normal as if the computer is not getting enough power. Bad power supply or motherboard?

When you have a dead board, the fans usually turn on just fine, at various speeds. Sometimes full on, sometimes not at all for a few seconds.

Normally after all you've tried, I'd finally give up and chalk it up to a rare incompatibility between your memory (likely) and motherboard/CPU.

However, the fan thing made me think of a last ditch test.
It could be that one of your fans is broken and has trouble spinning up, possibly creating a short or some overcurrent condition. That's so far fetched I have to type this post in a hoodie while looking around to make sure no fellow nerds are watching.
Lose the H cooler in favour of a known good air cooler, or, if you don't want to bother, temporarily disconnect all of your case fans.
For added safety and for a more comprehensive test, lose the overclock for now, but leave the Vcore and DRAM voltage slightly bumped.
That's literally all I've got without creating a huge ass checklist of odd tests like exposing the CPU area to moonlight on a Sunday etc.
 
Happened again even with the LLC setting in the BIOS set to Medium from the default Auto.

Even though I was already on the latest BIOS, I re-flashed the BIOS (same version). I just enabled XMP for my RAM, entered a manual Vcore of 1.200 volts (because leaving the Vcore on Auto puts in too much voltage), and disabled features I don't use/need such as on-board audio and unused SATA ports. Left everything else as it is. So far, I have done many random restarts and shut downs/boot ups just to see if it happens again and so far so good. No BIOS boot failure messages. Will keep it like this and see if it happens again.
 
Back
Top