Overclock Setting Fails to Post After PC Restart

udneekgnim

Senior member
Jun 27, 2008
247
0
0
When I restart my PC in XP my overclock setting fails to post and the mobo reverts back to non-OC settings. So there's something causing the OC setting to be unstable, but when I do a cold boot at the OC settings or change BIOS settings back to previous OC, it posts without an issue. I haven't done any extensive testing. Just 2 hours in Orthos and 10 runs of IBT and playing GTA 4 for 1-2 hours.

Idle Temp is 28
Orthos Load Temp is 45
IBT Load Temp is 60

Anyone have any experience with a similar situation before?

MOBO: GIGABYTE GA-EP45-UD3P
CPU: E8500 @ 4.25 GHz (9.5 * 448 FSB)
RAM: CORSAIR DOMINATOR 2 x 2GB DDR 2 1066
CPU HSF: Tuniq Tower
PSU: SILVERSTONE OLYMPIA OP650
VID CARD: VISIONTEK 4870 512

CPU VCore: 1.36 in CPUZ
NB Voltage: 1.4V
RAM Voltage: 2.1V
RAM Timings: 5 5 5 15
RAM Performance Boost: Standard

Everything else is on Normal or disabled/enabled per the stickied OC guide.
 

udneekgnim

Senior member
Jun 27, 2008
247
0
0
Originally posted by: Flipped Gazelle
What happens when you try a mild - say 10% - overclock?

Well this is my overclocking history with the E8500 E0,

9.5 * 400 FSB = 3.80 GHz
9.5 * 421 FSB = 4.00 GHz
9.5 * 431 FSB = 4.10 GHz
9.5 * 437 FSB = 4.15 GHz
9.5 * 442 FSB = 4.20 GHz
9.5 * 448 FSB = 4.25 GHz

I forgot to mention I'm using 2.0D strap (400 MHz) running memory 1:1.

My OC settings were not failing to post and getting reverted back to non-OC settings after restarting the PC in XP prior to OCing to 4.25 GHz. I just don't understand why it'll post when doing a cold boot or applying the OC setting in BIOS if it doesn't when restarting the PC in XP.
 

Udgnim

Diamond Member
Apr 16, 2008
3,662
104
106
well it's gotten a whole lot more unstable now. if I can get an OC to post, I haven't experienced any crashes or instability in Windows, but more often that not now, an OC will not post and it'll take the mobo multiple attempts to post and revert back to the non-OC default settings. I've OCed as little as a 5% increase (333 FSB to 352 FSB) to clock and it'll fail to post and take multiple attempts to get back to the original 333 FSB.

did I screw up the North Bridge by giving it too much voltage?