Overclocking c2d e6400 question about safe temperature range

dgood · Post by **dgood** » Fri Apr 20, 2007 4:00 pm

Ok so my friends machine we finally have been able to deam fully stable after changing some stuff around and playing with some settings.
It now has his 8800gts and core 2 duo e6400 on an asus p5b sli board. what is a safe target temperature to not go over when overclocking it. Keeping in mind we are overclocking it with a zalman cnps 9700. I want to start tonight or tommarow doing it for him as it was the goal of the operation to start. Any and all input is gladly accepted. Thanks.

Post by **dicecca112** » Fri Apr 20, 2007 4:09 pm

keep it below 55-60

kenc51 · Post by **kenc51** » Fri Apr 20, 2007 4:40 pm

Mine craps out when I hit about 68C with high clocks (measured with coretemp)

As Dicecca said, keep under 60C and you'll be ok!

dgood · Post by **dgood** » Fri Apr 20, 2007 8:19 pm

So when I do this should I change the FSB:Ram Ratio to 1:1 so it's running like ddr instead of ddr2 so I can find the max on the cpu then change the divider to ramp it back to 800mhz? I'm new to the overclocking of intels and ddr2 machines in general.

Post by **dicecca112** » Sat Apr 21, 2007 8:25 am

well the goal is 1:1 but that can have diminishing returns. I say go for max clock at 1:1, and then loosen the timings and go for real max clock. Personally I go as far the chip can go on 1:1.

Ocing is no different on Intel than it is on AMD

dgood · Post by **dgood** » Sat Apr 21, 2007 1:55 pm

So I just started, I have it running orthos at 2.2 ghz, I am pretty sure all will be fine but I always like to take really small steps. I don't' like how intel boards say fsb is 1066 when in reality it is 266. since the fsb/4 x the multi is where you get your clock speed. whatever though. I also found this motherboard to be really handy since you can auto set the ram to unlinked and set it at 800mhz and it will auto change the dividers to keep the ram at 800mhz. which is perfect. Makes my life easier. so off I go, I'll post some pics in a bit of my progress. The guy isn't even home, he just told me to come up and play around.

dgood · Post by **dgood** » Sat Apr 21, 2007 2:16 pm

So I have it at 2.4, made a jump, it seems fine. running orthos. I noticed that core temp and everest show very different numbers for cpu temperature. I think everest doesn't work on core 2 duos or at least not the versions I'm using. It doesn't show the core temps at all like it does on my fx-60. Guess I'm glad I decided to check out core temp. Everest is registering 25C for cpu temp and CoreTemp shows 42C for the core temperature readings.

Updated: Heres where I'm at currently.

dgood · Post by **dgood** » Sat Apr 21, 2007 4:09 pm

where I end the day for now, still room to go. 3.0ghz core 2 duo from 2.13ghz. I think its a god start.

Post by **dicecca112** » Sat Apr 21, 2007 4:18 pm

Not sure how L2s are but I know B2s do at least 3.2 on air. What Vcore are you at?

dgood · Post by **dgood** » Sat Apr 21, 2007 4:32 pm

well it hasn't been changed by me so still stock. coretemp says 1.325 which is the stock voltgage, but cpuz says 1.264 so I'm guessing its still at 1.325 v.

Post by **dicecca112** » Sat Apr 21, 2007 4:35 pm

What board is it? If its an Intel Chipset most likely its set to Auto, and its way higher than stock usually 1.4 or higher

dgood · Post by **dgood** » Sat Apr 21, 2007 4:44 pm

Asus P5E-Sli
Corsair Hx 520 psu
2GB GSKILL DDR800
I just set the ram to keep itself at 800mhz like I said earlier and made it real easy.

Post by **dicecca112** » Sat Apr 21, 2007 4:46 pm

well then that is the extent of my knowledge on that board. But seeing its an Asus, check to see if the Vcore is set to Auto. I don't believe so because your temps seem fine. Usually you get high temps at low clocks because the Vcore is so high

dgood · Post by **dgood** » Sun Apr 22, 2007 4:46 pm

It was set to auto, but it was at 1.325 V or actually more liek 1.3 was what it was showing up as in the bios even. but I tried 3.1ghz today. No luck, hung up on posting, had to reset cmos cuz holding insert wasn't working. then I tried raising the voltage, still no luck but at least the auto reset to last good setting hopped on for the board adn it put me back at 3.0 and posting so I tried 1.35v maybe I should have gone higher. no luck at 3.1 or 3.2, we thought we'd skip to 3.2 to keep the memory at 800mhz even. Divider doesn't like odd decimals for ghz. We decided to call it good for now. I'm curious what you have as your 3.2ghz on air as your voltage?

Post by **dicecca112** » Sun Apr 22, 2007 4:52 pm

1.3875 for Vcore, 2.0 for Vdimm. I had to up the chipset voltage to.

I used this guide
http://forumz.tomshardware.com/hardware ... 97995.html

dgood · Post by **dgood** » Sun Apr 22, 2007 4:57 pm

well maybe the next couple days I will go back up there and try some more. I was mad that it was hanging in the bios though and wouldnt' auto reset or let me use the insert key. the jumper is a pain to do.

kenc51 · Post by **kenc51** » Sun Apr 22, 2007 5:43 pm

dgood wrote:well maybe the next couple days I will go back up there and try some more. I was mad that it was hanging in the bios though and wouldnt' auto reset or let me use the insert key. the jumper is a pain to do.

Another way to reset ASUS boards quickly is to power on until just before the bios screen loads then off again quickly via the switch on your psu. The bios will reset and load with a message "overclocking failed".
I find the "Insert key" method doesn't always work.

Kougar · Post by **Kougar** » Wed Apr 25, 2007 11:03 pm

CoreTemp "VID" is not your CPU core voltage! Also remember not all programs read the internal cpu diodes for CPU temperatures... SiSoft is probably reading the diode in the CPU socket itself, which is always a good deal lower in temps.

For the 3.5ghz OC in my sig I was using 1.475v to keep stable and that was on air. I only needed about 1.365v for a stable 3.2ghz.

KnightRid · Post by **KnightRid** » Thu Apr 26, 2007 5:18 am

Kougar wrote:CoreTemp "VID" is not your CPU core voltage! Also remember not all programs read the internal cpu diodes for CPU temperatures... SiSoft is probably reading the diode in the CPU socket itself, which is always a good deal lower in temps.

For the 3.5ghz OC in my sig I was using 1.475v to keep stable and that was on air. I only needed about 1.365v for a stable 3.2ghz.

man - I still need 1.425 for stable 3.2 on the DS3 board and E6400

Temps hover between 50 and 55, so I guess it is all good.

Mike

Kougar · Post by **Kougar** » Fri Apr 27, 2007 10:12 am

I use the DS3 myself, currently I almost have a fully stable 100% overclock on it, I just need a new PSU first...

If you can get your temps down it may require less voltage. Also remember that your memory might be going out of spec, to do a 3.5ghz OC I had to run my 800mhz kit at 1,000ghz. I needed 1,067mhz capable RAM before I could even boot to 3.74ghz and work on getting it stable.