test ur Proc? wow...i am in for sure . I could prolly get it to 4.5ghz with extreme cooling.

N680i need GTL reference mod to enable better OC on C2Q. Frankly speaking 15s is very slow. Do the mod and with better cooling i bet you can hit 12s.

not just water cooling...better water cooling. Chipset cooling also important coz it'll get a lil hot. I can help you with mod but it's not really worth the effort if you don't have good cooling.

Ambient is important, but also depends on what cooling you use. I always run my rig in 35c - 38c ambient just to test it out. So basically i am half naked when i bench. My cascade can still hold the cpu at -70c. Chipset is around 30c. I also found out that cooling the chipset can give you around 20-30Mhz FSB. I might phase cool the chipset soon. But at the mean time i'll use super high CFM fan to cool the chipset.

What pics are you refering to? Let me just put it in words....without active chipset cooling, max FSB i can hit is 520FSB as the NB is rather hot. But with sufficient cooling, i can hit 540FSB and still counting. Phase cooling the chipset wont give a big margin...but perhaps another 10C to 15C.

As for ambient, i prefer to have the room warm...around 38C and yes, its very sweaty so that I can test the stability of my rig. There is no point using an ambient of 16C to test the rig as you cant really stress test the rig fully. But thats only for me....air cooling with high OC is a no no at at 38C ambient. You don't want a smokey rig eh.

If i turn on the aircon, room ambient at 17c....my cpu temps will go as low as -80C. Chipset temps will be at 28c. But to achieve these temps i have to turn on the air con everytime i use my rig. Its a lil bit unrealistic, don't ya think.

This post has been edited by extremeocer: Aug 22 2007, 03:34 PM

Bro, intune....how to add you when you never show your final 1M PI result. Need the final result.

Simple....those apps actually detect the multi as 9 but still show as 8. Since you use 400FSB....effective realtime clock is 400X8 = 3.2Ghz. But those apps somehow think it is 400X9 = 3.6Ghz. So you do the math, 450X8 = 3.6ghz. Weird eh, but thats the way it is.

71C...that's their thermal specification. That refers to the core. Just forget about the CPU temp and focus more on the core temp.

ok, here's my Q6600 initial results after being absent for a long time.

C2Q Q6600 @ 4.28Ghz
Asus Commando bios 1302 (old skool )
TeamGroup Xtreem PC8500 2X1GB
Silverstone Zeus ST75ZF

My commando doesn't read the temps right. But according to my temp probe ( placed near the suction line instead of evap base ) it's at -61C load and -56C on full load. Temps are great with just a r410a cascade.

Haha bro....read carefully, remysix bro said minus the minus...means not negative la....hehe

This post has been edited by extremeocer: Feb 20 2008, 10:57 PM

Here is a better result from my previous OC

C2Q Q6600 2.4Ghz @ 4.356Ghz
Abit IP35-E unmodded ( budget but strong overclocking mobo )

Vdroop depends on vcore...my IP35-E has got quite bad vdroop with 1.68v....on load it drops to around 1.64v. 0.04v is critical on High OC. Will do the droop and Vpll mod....see if these mods can yield higher clocks.

Really difficult to pin point the exact issue......sometimes it may be driver issue / PCI-e frequency too high, etc etc. For my case, at 4.4Ghz, i cant do 8 hrs of prime...but gaming is rock solid, tested on UT3, crysis for 5 hours straight continuous gaming without a single hiccup.