Newbie overclocking E6400 with P5B-E, Micro PC2 6400, Tuniq Tower 120

ckica

Junior Member
Mar 18, 2007
3
0
0
Hi,
I am a newbie in overclocking, and before I burn my machine, I wanted to know if someone could help me a little bit.
Here is what I have done so far:
1- Using the automated setting on the P5B-E, I overclocked my E6400 to 3.5 Ghz. Under load, the temperature was close to 60-62 degres (using Core Temp), which I thought was too high.
2- So I went down to 3.2 Ghz by setting the multiplier to x8 (400x8.0), left every other settings on auto except the CPU voltage, and chose 1.415V. The CPU temp at idle is around 34degres C and goes up to 54 when loaded (using ORTHOS)

I have three questions:
1- Do you think 54deg is too high ? If not, do you think I can safely go to 3.4Ghz ?
2- What else can I do to lower the temp besides tweaking the CPU voltage ?

Thanks
 

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
Even the 60-62 is not to high IMO. Controlling the voltage is about all you can do to get lower temps. I have the same board and I can tell you that it overvolts like crazy on the auto setting once you overclock. I would try going back up while manually setting the vcore.

Your e6400 seems to be better than mine, I have to pump it up to 1.475 to get orthos stable at 3.2ghz:(, but I'm running the stock HSF so that may have something to do with your increased success.
 

ckica

Junior Member
Mar 18, 2007
3
0
0
I was a little bit optimistic. It seems that I had to increase to 1.43 which is still not too bad based on your reply. This time I was able to run ORTHOS with Small FFT for 1 hour. Under load, temp reported by SpeedFan or Core temp is 55C on each core and CPU temp is 70C. I am not sure which one is the most important.
I have also changed the FSB to 401 after reading several posts on this site.

Based on these numbers, do you think I can try 433 FBS ?
 

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
You may be able to, but it will almost certainly take more vcore. This board also has a significant vdroop, which means the amount of voltage that you get to the chip under load conditions is significantly less than you set in bios. I can run my E6400 in the 430-440 range but it takes 1.6v set in bios which gives me like 1.46v under load in windows and with my stock HSF temps get way out of hand near 80c. I've booted up that way a couple of times for some SuperPI runs, but no way would keep it that way very long. With better cooling I might be comfortable with like 1.55v set in bios, but no way would I ever use 1.6v for 24/7 usage.
 

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
And I should add that I'm a pretty hardcore overclocker and I tend to upgrade my rig every 18mos or so, therefore I'm pretty accustomed to voltages and temps that many, more conservative folks would deem unsafe.

But I will say I've been doing this for many many years and have never had a single CPU die on me. Maybe I'm lucky, but I really believe CPU's are much tougher than most will believe.
 

PCTC2

Diamond Member
Feb 18, 2007
3,892
33
91
yeah. nice OC. i have a Thermalright Ultra 120 on my E6400 and i'm currently running 3.6 (450*8) on my rig (in sig) about 6-12 hours a day. I would not suggest trying my OC if you're gonna run 24/7. I have to pump 1.55v and keep about 35 idle (17C ambient) and 56 Orthos load. I have run at 466.67*8 (3.733Ghz... see MAX OC in sig) for short periods of time at 1.58v if i have some intensive work i don't want to waste more time than i have to or if i need to benchmark, but i don't use that OC too much.
I would suggest maybe 425-440 FSB at 1.45 or 1.5v. 1.55v should really be the MAX for any OC and anything up to 65C should be fine. Nice job!
Don't forget to disable C1E, EIST, Virtualization Technology, set the voltages manually, and you try setting the memory timings too (read forums). Auto settings generally don't work so manual is the way to go.
 

ckica

Junior Member
Mar 18, 2007
3
0
0
Thanks a lot. I have tried 433 but the OS did not boot. I guess, I need to start tweaking the memory ratio or increase the voltage again. Will let you know.