Computer randomly restarts and reset BIOS settings

[hans030390]

Trying to figure out what is causing this. I've been messing with overclocking my i5 2500K on my Biostar TZ77XE3 motherboard. Wanted to see if I could take it past 4.5GHz. I've experimented with clocks around 4.8-4.9GHz at fairly high voltages (1.45V+, temps are fine, not meant to be permanent OC).

One problem I've been having is that my computer will randomly restart and reset my BIOS settings. It only seems to happen when I'm browsing the internet (Chrome) and doing little to nothing else. No BSOD, no error in event logs, nothing. Just an instant, random restart and reset BIOS. I'm running Windows 8, BTW (legit, got it through MSDN AA).

Now, this is a bit odd, because my CPU tested stable for around 18 hours on OCCT large, 6 hours OCCT small, and 1 hour on OCCT Linpack with AVX. Of course, I know those tests can't guarantee stability.

I've also recently updated my BIOS. I hadn't really tried taking my OC past 4.5GHz until now. I think I had a similar BIOS reset issue a while back when I tried to take it to 4.7GHz without overvolting the PLL, but that didn't even boot into Windows. Instant restart, and my BIOS settings were reset. At least, I THINK this happened before I updated my BIOS.

I've also recently installed an HD7970 and have that overclocked (stable).

So, what's likely the issue? Unstable OC? Perhaps the BIOS version has a problem? New GPU? I'm guessing it's just an unstable OC, but it seems a bit weird how and when it's crashing plus the BIOS settings being reset.

 

[lenjack]

mb battery?

 

[Steltek]

Does the BIOS maybe have a function when overclocking to automatically reset to defaults in event of a crash?

If you start it up, get to the desktop, then do a complete successful shutdown followed by a restart, does the BIOS still reset to defaults when it crashes?

 

[hans030390]

mb battery?

Perhaps...any way I could test for this? Just not sure the situation points to that.

Does the BIOS maybe have a function when overclocking to automatically reset to defaults in event of a crash?

If you start it up, get to the desktop, then do a complete successful shutdown followed by a restart, does the BIOS still reset to defaults when it crashes?

I don't know...it might have that function. But it's only done this random restart/BIOS reset twice, and it's only been at 4.8 and 4.9GHz at decently high voltages. And it's only done it while I was lightly using it. No issues on bootup or shutdown from what I can tell. I had been running it for a few weeks prior at 4.5GHz without issue.

I should also mention that I had plenty of crashes at high OCs when doing stress testing at too low of voltages (BSODs and freezes). These never reset my BIOS settings. And, then, when I can finally run stress tests for hours and hours on end, my computer has randomly restarted twice for no reason and reset the BIOS settings.

I'm still guessing it's just not a stable OC...but it's weird. Never seen anything quite like this.

 

[hans030390]

Just had another weird issue. Booted up the computer without my monitor turned on. Didn't realize it wasn't turned on, so I started hitting the delete button to get into my BIOS while the monitor turned on. After a bit, the monitor said it had no signal. Hit the restart button on my computer and went into the BIOS. CPU settings were again reset to default. ***? I've never had issues at 4.5GHz at this voltage before. Might have just been an odd coincidence...

I also noticed that if you go into the CPU settings in the BIOS after it resets, it gives this error message at the top:

"BIOS setting causes system boot fail. Please load default or set again properly!"

I'm assuming it has done this in previous reset situations. I just hadn't noticed until now.

Could it have something to do with the PLL voltage? My motherboard has a setting called "internal PLL override," which I'm assuming overvolts the PLL. I've heard this might be needed for higher clocks and, sure enough, I couldn't clock above 4.6GHz at all without this setting enabled.

Technically, I still have this enabled at 4.5GHz. When I was running it without ANY issues previously at this clock, I did not have the PLL override enabled.

Edit: the BIOS always displays that error. Guess it's nothing, then!

 

[Dstoop]

If you're getting error messages in the BIOS about the config, and it's constantly resetting itself, smart money is on one of two things: Dying CMOS battery or corrupted BIOS.

First thing i'd try would be restoring the BIOS to complete factory defaults, then flashing to the latest version using the most reliable method available from your mobo manufacturer (usually boot media, stay away from the windows-based flashers like Gigabyte @bios). If you're already on the latest version, try it anyway to see if it will flash over the current one for a fresh start.

If you dont have the equipment to test the CMOS battery, it'd probably be cheaper to just replace it and see if it makes a difference than it would be to get the stuff and test.

 

[denis280]

If you dont have the equipment to test the CMOS battery, it'd probably be cheaper to just replace it and see if it makes a difference than it would be to get the stuff and test.

that would be the best

 

[hans030390]

Upgrading/downgrading the BIOS doesn't make a difference, and I've gone as far as resetting it to factory defaults before and after installing the BIOS (through jumper, removing CMOS battery, and default settings "button" in BIOS itself). Also, that error message is always displayed, and I edited my previous post to reflect that. It's not actually related to the issues I've been having.

Anyway, I dropped back down to 4.6GHz and no longer have the PLL voltage override setting enabled. At 1.38V currently (can probably go lower, haven't tested). No issues to report of as of now. I just might not be able to go above that for whatever reason, be it the CPU or motherboard!

 

[Sheep221]

Seems like voltage regulators were damaged when you peaked your OC at 4.9 and ran it through stress.

Advice:

Run your CPU on stock and do the things that were running when the issue started.
If problem persists, remove CPU and put it to another board, if it works there without issues, your MB is damaged.

 

[hans030390]

Eh, I'll monitor it for a while as-is. It's been fine for a few days now. If it keeps messing up down the road, I'll just get a different MB.