e6400, p5b deluxe OC problem

[clawlan]

Ok, I got the computer to boot and run stable at 400mhz fsb. Opening cpu-Z showed a clock speed of 3.2ghz. All is fine and well. I restarted the computer, went back into teh bios, reset everything back to default, and then booted back up. All is fine and good. I then decided to overclock again to benchmark and went into the BIOS, changed all teh settings to how I had them before when it worked to 3.2ghz, but when I boot up now, cpu-Z says im running at only 2.568ghz. Why the hell would it do this?

Heres some cpu-Z info:
Multiplier - x8
Bus - 321.1
Voltage - 1.360 (even though i set 1.4 in BIOS)
FSBRAM - 1:1

Bah!!!!! Please help!

 

[n7]

No idea man.

However, here are my settings (maybe they'll be of help)
CPU:
http://img146.imageshack.us/img146/8960/img0885largezg8.jpg
Voltages etc:
http://img138.imageshack.us/img138/4204/img0620largezy4.jpg

BTW, having the vcore measure lower in Windows than bios is normal unfortunately.
Asus C2D mobos all seem to have pretty bad vdroop.

 

[clawlan]

thanks for the pics. I have xms2-ddr2 ram btw.

UPDATE: So apparently my rig had a seizure. After restarting again, it randomly restarted, was having errors, and then said i had to reinstall my soundmax drivers. Jesus, what the hell did i do? Anyways, reinstalled the soundmax drivers and set all bios settings to default and we seem to be back to normal. lol. would like to know why isd wont go back to 3.2 though.

 

[zizo]

Originally posted by: n7
No idea man.

However, here are my settings (maybe they'll be of help)
CPU:
http://img146.imageshack.us/img146/8960/img0885largezg8.jpg
Voltages etc:
http://img138.imageshack.us/img138/4204/img0620largezy4.jpg

BTW, having the vcore measure lower in Windows than bios is normal unfortunately.
Asus C2D mobos all seem to have pretty bad vdroop.

I wouldn't worry about that vcore drop because the difference between full load and idle is less than .08. Actually, I don't know if the difference between bios and windows vcore is called vdrop! (real question )

n7 have you tired 400FSB performance? Just do me a favor and compare it with your 426FSB because I see too much of performance drop after 400FSB up to 430 .

Anyway here is what I settled for!
pic

 

[zizo]

Originally posted by: clawlan
thanks for the pics. I have xms2-ddr2 ram btw.

UPDATE: So apparently my rig had a seizure. After restarting again, it randomly restarted, was having errors, and then said i had to reinstall my soundmax drivers. Jesus, what the hell did i do? Anyways, reinstalled the soundmax drivers and set all bios settings to default and we seem to be back to normal. lol. would like to know why isd wont go back to 3.2 though.

try 401FSB

 

[n7]

Up to 399, it uses the 1066 strap with tighter timings
At 400, it switches to the 1333 strap, however, it seems it still uses the tighter timings
Then 401+ it's 1333 strap with loose timings, which is why you see the performance drop.

I haven't tested this for myself, mainly since others already have, & i have no interest in lowering my OC to 3.2 GHz

 

[clawlan]

Originally posted by: n7
Up to 399, it uses the 1066 strap with tighter timings
At 400, it switches to the 1333 strap, however, it seems it still uses the tighter timings
Then 401+ it's 1333 strap with loose timings, which is why you see the performance drop.

I haven't tested this for myself, mainly since others already have, & i have no interest in lowering my OC to 3.2 GHz

Well, tried 401 an have the same issue, only clocking at 2.568. This time though on restart, it shut down and restarted on ita own and told me it was a RAM problem (thanks microsof error report). Si then i booted into UBCD and ran memtest. 10 passes and not one issue so its not bad ram. Bah. anyone have any other ideas?

 

[NoStateofMind]

Originally posted by: clawlan

Originally posted by: n7
Up to 399, it uses the 1066 strap with tighter timings
At 400, it switches to the 1333 strap, however, it seems it still uses the tighter timings
Then 401+ it's 1333 strap with loose timings, which is why you see the performance drop.

I haven't tested this for myself, mainly since others already have, & i have no interest in lowering my OC to 3.2 GHz

Well, tried 401 an have the same issue, only clocking at 2.568. This time though on restart, it shut down and restarted on ita own and told me it was a RAM problem (thanks microsof error report). Si then i booted into UBCD and ran memtest. 10 passes and not one issue so its not bad ram. Bah. anyone have any other ideas?

Do you have by chance anything set to auto? I'm not very good at OC'ing, ask my beast, didn't like my last stab at 500Mhz FSB and had to reset his CMOS PITA removing that big aths X1900XT!

 

[cmdrdredd]

Not every CPU will need as much voltage as I gave mine, but it's a very very safe volatage to use through the bios (1.4v) so here's what i suggest after you download and flash to the newest BIOS available from ASUS's site.

under jumper free configuration set the following
FSB 400Mhz
DRAM 800Mhz
PCIE 100
PCI 33.3
Spread Spectrum off
DRAM voltage 2.1v
CPU Vcore 1.4v
fsb termination voltage 1.3
chipset voltage 1.45
everything else can be at auto

under CPU Configuration turn everything to disabled except Vanderpool Technology (allows intel virtuliztion apps to use this feature on your cpu)

Under NB chipset features turn the following options
memory remap disabled
configure DRAM timing by speed disabled
CAS latency 5
RAS to CAS delay 5
Precharge 5
RAS Activate to Precache 12

Leave everything else alone

Under USB configuration turn off the Wi/Fi adapter if you're not using it.

 

[clawlan]

thx. ill try that.