Should I overclock this 3.2ghz E5200 further?

I get the feeling it's your memory/settings holding you back.

Did you bump up the MCH? If not you may want to try this and then upping the vCore to 1.36V (don't worry about the restarts - it's normal with a failed clock attempt. Sounds worse than it is.)

But TBH, i think we need to bring your memory speed down to ~800MHz (i think 2.66 is next in the multiplier) while we test the CPU’s limits and the voltages it needs.We need to be sure that any instability you encounter isn't due to your memroy). Once we have found a stable platform we could then look at getting the memory above 800Mhz.

If we brought the memory speed down you should be able to post 3.5GHz, hopefully, with 1.35V or less. Fine tuning the memory over speeds of 800MHz with an 800FSB chip is always the fiddly bit. You can sometimes get it to run at its designated 1066 - but it's a long methodical process.

So to summarise - either try 1.36V with an MCH of 1.2V with th epresent settings and see what happens - quite often a mixture of voltage fractions can solve everything. Or lower the memory to 800MHz or under using the divider and leave the other settings as is.

Again, this is a quick fix approach - and if it fails you perhaps need to either stick at 3.2GHz or do this the traditional way - i.e. resetting the system back to stock and upping the FSB incrementally until it buckles (revert back to last known stable FSB), then upping the vCore, repeat process etc then fine tune other settings as required...


Additional:
  • Have you ever memtest your memory at the 3.2GHz settings?
  • What is the memory speed/setup in the 3.2GHz profile?
 
Last edited:
When it kept rebooting the other night I was extremely worried, I would have had no warranty or anything. I just don't think it is worth it at this point for only a tiny bit of extra fps.
 
I guess I wasn't expecting it to freeze up like that, then fail to boot, I couldn't even acess the Bios... I was kinda thinking the worst case scenario was just a BSOD then a reboot.
What exactly happened there?
 
Plec,

Could you tell me the VID of your CPU at all?

Only reason I ask is that to get my E5200 stable at 3.4GHz I have to set it at 1.375v in the bios which results in 1.360v at idle.

I suspect my M0 stepping E5200 has a pretty high VID at 1.2250v

I'd like to get it to 3.5GHz but so far even setting the vCore to 1.400v in the bios (approx 1.375 at idle) results in Orthos failure. I'm not sure the extra vCore is worth the extra 0.1Ghz

Any comments appreciated
Steve
 
I wont be at my desktop until this evening - i'll have look for you then.

It's unusual for an e5200 to require so much vCore for a relatively mild clock - but, unfortunately, there are some chips which are poor clockers.

What's your system spec?

Also, are you remembering to alter the memory divider as you up the FSB - ideally keeping the memory as close to 800MHz to begin with?
 
Plec,

Could you tell me the VID of your CPU at all?

Only reason I ask is that to get my E5200 stable at 3.4GHz I have to set it at 1.375v in the bios which results in 1.360v at idle.

I suspect my M0 stepping E5200 has a pretty high VID at 1.2250v

I'd like to get it to 3.5GHz but so far even setting the vCore to 1.400v in the bios (approx 1.375 at idle) results in Orthos failure. I'm not sure the extra vCore is worth the extra 0.1Ghz

Any comments appreciated
Steve

Try it without speedstep turned on, i noticed i required far less volts with it turned off, allways worth a test.
 
I wont be at my desktop until this evening - i'll have look for you then.

It's unusual for an e5200 to require so much vCore for a relatively mild clock - but, unfortunately, there are some chips which are poor clockers.

What's your system spec?

Also, are you remembering to alter the memory divider as you up the FSB - ideally keeping the memory as close to 800MHz to begin with?

Yeah I think mine is a poor clocker but I would love to get it to 3.5GHz as long as I can find a way to keep the vCore down.

Yep, Memory set at about 750MHz

Temps by the way are 35deg (Idle) and 50deg (load) so plenty of headroom there.

Spec is as follows:

E5200 (Obviously) - M0 Stepping
Freezer 7 Pro
Asus P5Q-E
Antec 300
Corsair 4GB (2x2GB) DDR2 800MHz/PC2-6400 XMS2 Memory Non-ECC Unbuffered CL5
Windows 7 Home Premium 64bit

Try it without speedstep turned on, i noticed i required far less volts with it turned off, allways worth a test.

Cheers, will give it a go and report back.

Steve
 
@ Gizmo

Sorry for the thread hijack BTW, just thought it would be more useful if I post in this thread seeing as we're having similar issues.

Steve
 
Sorry Steve still not home...

How have you reached 3.4GHz - i.e. 383*12, 275*12.5, 340*10?

If it's via a high multi (e.g. ~12.5*275) try dropping the 0.5 as i found this limited higher clocks on my MB. Also, if you haven't tried higher FSB clocks you could have a play with lower multipliers and see how it fares? (Thats is if you haven't tried this already.)
 
At the moment I'm at 12.5x272.

I did try 12x284 but the results were identical.

I've also tried finding my FSB wall by using a 6x multi and it's roughly around 320-330 before it fails to boot so I'm pretty much stuck with 11, 12 or 12.5 as 10x350 is out of the question.
 
OK just tried 11x318 with current voltage (1.3825v in bios for a Windows idle of 1.3600v) and it fails pretty much straight away.

I've also got speedstep disabled but it makes no difference.

Think I've got a poor chip.
 
Back
Top Bottom