Citizen_Insane's Q6600 Overclocking Thread

C

Citizen _insane

Gawd
Joined
May 2, 2006
Messages
565
Ok, so I just picked up a q6600 @ microcenter today. So far I'm very happy with it. I have a couple questions and such. I haven't played around with maxing this at ALL, I've just quick set it up, so don't think this is my maximum overclock by any means (although I have no clue what the max on this chip is)

System:

Abit IP35-Pro motherboard
Q6600 SLACR G0 Stepping - 384x9 = 3.46Ghz
Scyth Infinity cooler
4x1gb Corsair XMS2 DDR2 800
x1950Pro 256mb
Corsair 620HX
Other stuff that's non-relevant

So my overclock right now is sitting at 3.46Ghz, 384x9, 1.345V, ddr2 = 2.125V. According to CoreTemp my temps are: 67 67 63 63 (*C) at full load. As I understand it, CoreTemp read the actual die temp, so the max for the processor is 100*C correct? I just want to be sure before I ruin anything.

I also noticed when installing the processor that the IHS wasn't completely flat. I may be lapping the processor some time soon after I determine it's in good condition and I won't need the warranty. That should drop temps a bit as well.

Anyway, does this seem pretty good? I'm pretty happy with the results, although temps seem a bit on the high side, the system is perfectly stable. For all my settings, see the attached screenshot.



edit - batch#L737B286 - updated max temps
 
As long as it's stable under load, and you're under Intel's max spec voltage for the architecture (I think it's 1.55v), you're fine.

That's a pretty nice OC for not even trying. Pretty nice voltage on the CPU too, although does your DDR2 volts need to be that high? Unless you have active cooling on the modules, you could be getting into the danger zone with your RAM.
 
If you're running 1:1 ratio, then you're not even running your memory at it's rated speeds. So you should be able to lower the voltage down to atleast 1.9, or even at it's defaultt 1.8. But since you're running all 4 slots, it might be a safer bet to stay at 1.9.
 
Also, I believe tJunction is the *MAXIMUM* your cpu can handle. But generally, you don't want to get anywhere near that. Safe-zone should be below 71c.
 
Ok, well over night, my temps dropped again they're now: 66 66 62 62 (100% CPU all night long, folding@home). I think the paste is setting in. About the memory voltage, the XMS2 Modules I have are rated for 2.1V, that's their rated voltage from what I've heard. I can try dropping it down a little bit, I'll run some blend tests in Orthos to make sure they're still working ok.

edit - I also messed up my report of DDR2 voltage in my original post, it has been corrected.

edi2 - I lowered the DDR2 voltage to 1.9 and the system crashed. Then something weird happened. For some reason, every time I tried booting, my motherboard cleared the CMOS. I would save the settings in the BIOS, but then the computer would just shut off after I saved them. I would have to manually restart and then all my BIOS settings were cleared. It got it back up finally after boosting the DDR2 voltage to 2.1V. I don't know if this issue was due to the ram voltage or not, but hopefully it was.
 
The 'CPU' temperature is the Tcase, and is generally -10C from the hottest core, I believe. That's the one that Intel's 72C spec refers to, which would correspond to the hottest core being at 82C. However, that's obviously a maximum for safe operation, I wouldn't like any of my cores going into the 70s.
 
I noticed on my IP35 Pro that I needed a bit more voltage to the RAM than my EVGA i650 needed for the same stability. The IP35 seems to undervolt the RAM a bit.
 
According to CPUID Hardware Monitor, that is correct. My actual voltages are around 2.08v, almost a full 0.1V under my specified maximum. My idle temps are: 40 40 36 36. These seem a bit high for my room temp (about 70*F). Uguru has also started acting up. I've been getting lock ups when trying to overclock. Any ideas why something would have changed?

Edit - Now I'm having more boot issues. The only way I can get the system to boot is with DDR2 voltage at 2.125. I'm thinking that it's the ram, but I'm not sure. Since I started tweaking the memory settings everything has gone haywire. I'll do more testing tonight.
 
You must log in or register to reply here.
Back
Top