overclock fine, then trouble at startup.

[Cancer12]

Hi all

I'm overclocking my i750 on a Gigabyte p55-ud3r to 4ghz, at 1.375 vcore (cpuz shows 1.32v). Prime temps after an hour are around 70c.

My overclock seems fine, but when I start my computer after non usage it often restarts itself 3 times to get to windows and loses the overclock. During this time a bios recovery takes place.

Anyone have any idea why this might be happening?

 

[Hyperlite]

So when you go in and set the overclock, save and exit, it boots fine? Well then don't turn your rig off silly!

but really...that's kinda odd. maybe up Vdimm a bit? maybe you're hitting the limits of that i5?

 

[Cancer12]

Exactly. When I set the overclock it runs perfectly. Gets through prime without a problem (after I upped the voltage a bit anyway). But when I turn the computer on (like this morning) it restarts a few times and puts the bios to default before I get into windows. Its really troubling because I want to set my 4ghz and forget about it!

 

[kalrith]

My computer's overclock fails at BIOS every 2-3 months but passes PRIME just fine, so I just deal with it. I'm not sure what would cause your BIOS to default so often. You could at least put in the settings that you want and then save them as one of the saved BIOSes. That would make it easier to retrieve the settings.

You might also try to run Prime for longer than an hour. I run mine for 12-24 hours before certifying it as stable.

 

[angry hampster]

My setup listed below does that from time to time. I've never bothered trying to figure it out. I'll definitely keep an eye on this thread though.

 

[Cancer12]

Looks like one core failed after running prime for much longer. I'm trying to decide between feeding it a bit more juice or scaling back a touch.

 

[MadScientist]

My guess is you don't have a stable overclock.

From overclockersclub review of your MB:
"During the CPU overclocking and memory overclocking, I found that a failed overclock would need a series of three bad POSTs in a row to reset the CMOS to the defaults, to facilitate booting. Once into the BIOS, the settings that were set and resulted in a bad POST are still there, so you can see what you did wrong and learn from the mistake. Not once did I get so far out of bounds that I had to clear the CMOS to boot."

http://www.overclockersclub.com/reviews/gigabyte_ga_p55_ud3r/7.htm

What Prime95 test are you running SmallFFts or Blends and for how long?

Try running LinX at full memory, Intel's Linpack with an easy to use GUI. If your system is unstable it will tell you within minutes.
Download it here: http://www.xtremesystems.org/forums/showthread.php?t=201670

 

[MrK6]

My guess is you don't have a stable overclock.

From overclockersclub review of your MB:
"During the CPU overclocking and memory overclocking, I found that a failed overclock would need a series of three bad POSTs in a row to reset the CMOS to the defaults, to facilitate booting. Once into the BIOS, the settings that were set and resulted in a bad POST are still there, so you can see what you did wrong and learn from the mistake. Not once did I get so far out of bounds that I had to clear the CMOS to boot."

http://www.overclockersclub.com/reviews/gigabyte_ga_p55_ud3r/7.htm

What Prime95 test are you running SmallFFts or Blends and for how long?

Try running LinX at full memory, Intel's Linpack with an easy to use GUI. If your system is unstable it will tell you within minutes.
Download it here: http://www.xtremesystems.org/forums/showthread.php?t=201670

This is why I love Gigabyte boards; easy to overclock and even easier to recover.

OP, do you have any associated beeps when you fail to boot? Sounds like you don't have a stable overclock, but I could use more information. What's a full rundown of your specs and settings? Off hand, I'd say make sure your RAM timings and speed are set correctly, you lowered your QPI multiplier to x32, and your voltages are in check (VTT @ 1.21V, CPU PLL @ 1.9V, and appropriately set Vcore and Vdimm work well for me). Also, make sure you turn off all power saving features (C1; C4,C6,C7; EIST, etc.).

 

[Plester]

A bunch of boards from many manufacturers suffer from cold boot issues when overclocked. I suspect this is more of a problem in winter than summer.