• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need some OC help!

K

koston88

n00b
Joined
Jun 11, 2008
Messages
19
Recently upgraded my case to get better airflow, so started OC'ing it more.

Mobo: P5Q-E
Proc: e7200
FSB: 360
Temps idle: 25-30
Temps load: 45-50
Vcore: 1.20
NB: 1.14v
Ram voltage: 2.1
LLC - enabled

That's the stable OC previously (ran for some 10-12 hours stable on prime)

Today, I went up a tiny bit to 365 and now when I run OCCT or Prime on blend mode I get blue screens. I'm thinking it's the memory - rated at 1066 but running at 1098 (when 365) - I tried running it lower at 980 ish and still got blue screens. Not sure if it's the NB or other voltages I need to raise. Most of the other settings are set to auto if not listed above.

Anyone got any ideas?

p.s bios is 2001
 
koston88 said:
Recently upgraded my case to get better airflow, so started OC'ing it more.

Mobo: P5Q-E
Proc: e7200
FSB: 360
Temps idle: 25-30
Temps load: 45-50
Vcore: 1.20
NB: 1.14v
Ram voltage: 2.1
LLC - enabled

That's the stable OC previously (ran for some 10-12 hours stable on prime)

Today, I went up a tiny bit to 365 and now when I run OCCT or Prime on blend mode I get blue screens. I'm thinking it's the memory - rated at 1066 but running at 1098 (when 365) - I tried running it lower at 980 ish and still got blue screens. Not sure if it's the NB or other voltages I need to raise. Most of the other settings are set to auto if not listed above.

Anyone got any ideas?

p.s bios is 2001
Click to expand...

first whats the error its showing on the BSOD.. if its a machine exception error then you need to raise the voltage on the cpu.. but you could also try bumping the NB voltage but if its bsod'ing even with the lower clock speeds on the ram then i dont think thats the issue.. but first id start with raising the cpu voltage just a little bit see if it stablizes.. if not then start messing with the other voltages..
 
How did you change from memory speed 1098 to 980, just FSB or a combo of FSB and mem multi? Did you change any voltages? Are any voltages on auto?

Make sure your CPU is still stable by running some small FFT tests.
 
Technophobe said:
How did you change from memory speed 1098 to 980, just FSB or a combo of FSB and mem multi? Did you change any voltages? Are any voltages on auto?

Make sure your CPU is still stable by running some small FFT tests.
Click to expand...

Changed the ram speed by changing the fsb:ram speed ratio. So yeah the mem multi.

CPU PLL Voltage is on auto, so is FSB termination voltage

Changed CPU Margin Enhancement is set to -->Performance (random asus setting)

Changed FSB to 361 and OCCT testing it now - no errors so far.

Previously tested 360 on both prime blend/small FTT and OCCT for 10 hours and no errors.

I'll have to double check but I can't remember what was on the BSOD, might be the vcore messing up like sirmonkey said.

I will raise it back to 365 later and raise the vcore a notch to see if that works.

Thanks for the quick replies!

EDIT: Ok tested it at 362 at vcore 1.21 and no errors on OCCT or any BSODs. Must have been a vcore prob heh.
 
Last edited:
You must log in or register to reply here.
Back
Top