First real overclock =]

~LoKe

Limp Gawd
Joined
Oct 29, 2006
Messages
393
My Gigabyte 965P-S3 board showed up today, so I pulled out the old ASRock and put this one in instead. I was excited because I could finally overclock and see a significant gain.

Specs:
Intel Core 2 Duo, E6300
Gigabyte 965P-S3
1GB (2x512) Dual Channel/DDR2 RAM (PC-5300, 667MHz)

Currently running at 3.43GHz, 490FSB. 500FSB doesn't boot. CPU temp is around 40*C while folding on both cores. Idle is around 30*C.

RAM timings are 5-5-5-15, 2.2V. vCore is 1.37xx.

How does that look so far? I'll take a picture of my BIOS settings the next time I reboot, perhaps there's something I could improve. I'm still using the F6 BIOS.

EDIT: Here's the picture. Everything is still the same exact the FSB is now 490 and the vCore is 1.38xx.
EDIT2: Backed it off to 480 FSB. 490 locked up.

 
boo forbios screen shots! Looks like you have fun today;)

 
Thanks!

Should mention that my CPU and GPU are watercooled. ;)
 
It's a mess right now. Things hanging out all over the place. I was just too excited to piece it all back together. Pics will come soon.
 
You're loading at 40c under water with that huge OC?

Are you measuring with Coretemp..? I find that really hard to believe, especially if you've got a GPU in the loop.

Nice OC, regardless.
 
I'm definitely measuring it wrong. I'm under Linux so the standard apps aren't exactly usable. I'll try to see if I can get the temps to read better.
 
I'm definitely measuring it wrong. I'm under Linux so the standard apps aren't exactly usable. I'll try to see if I can get the temps to read better.

Ahhh, that makes sense now. Still an incredible overclock... ESPECIALLY for that RAM!

That's like, the highest RAM OC I've ever seen...
 
Now I'm happy. Thanks. :)


Yeah... DDR980 from DDR667 is about a DDR313 overclock...

I can't even get more than a DDR200 RAM oc...

Do you have a Windows partition... I think it's CRUCIAL that you Check temps with Coretemp and Stability with Orthos...
 
I think I'll install Windows tonight.

For some reason, I'm skeptical like you are. The BIOS and my thermal monitor seem to read in the mid/low 30's idle, and I'm not entirely sure how to go about getting my load temps. Windows is the only way to do it, I guess.
 
For fun...Super Pi!

------ Started super_pi run : Wed Feb 7 18:23:58 EST 2007
Start of PI calculation up to 1048576 decimal digits
End of initialization. Time= 0.192 Sec.
I= 1 L= 0 Time= 0.608 Sec.
I= 2 L= 0 Time= 0.704 Sec.
I= 3 L= 1 Time= 0.708 Sec.
I= 4 L= 2 Time= 0.708 Sec.
I= 5 L= 5 Time= 0.712 Sec.
I= 6 L= 10 Time= 0.704 Sec.
I= 7 L= 21 Time= 0.700 Sec.
I= 8 L= 43 Time= 0.716 Sec.
I= 9 L= 87 Time= 0.700 Sec.
I=10 L= 174 Time= 0.712 Sec.
I=11 L= 349 Time= 0.704 Sec.
I=12 L= 698 Time= 0.704 Sec.
I=13 L= 1396 Time= 0.700 Sec.
I=14 L= 2794 Time= 0.700 Sec.
I=15 L= 5588 Time= 0.696 Sec.
I=16 L= 11176 Time= 0.704 Sec.
I=17 L= 22353 Time= 0.708 Sec.
I=18 L= 44707 Time= 0.664 Sec.
I=19 L= 89415 Time= 0.628 Sec.
End of main loop
End of calculation. Time= 13.929 Sec.
End of data output. Time= 0.072 Sec.
Total calculation(I/O) time= 14.001( 0.528) Sec.
------ Ended super_pi run : Wed Feb 7 18:24:26 EST 2007
That's with "Stress" already running.
 
"Fatal error: Rounding was 0.4946289062, expected less than 0.4. Hardware failure detected, consult stress.txt file".

After 11:31. Guess I gotta back it off a bit.
 
Question: EasyTune5 that came with the board says my CPU temps are 45 and under, however, CoreTemp Beta 0.94 says 62-63? Which is correct? And why would they be so different?
 
Question: EasyTune5 that came with the board says my CPU temps are 45 and under, however, CoreTemp Beta 0.94 says 62-63? Which is correct? And why would they be so different?

Coretemp.

Easytune is reading from the motherboard, Coretemp reads from... well... the core :p
 
Coretemp.

Easytune is reading from the motherboard, Coretemp reads from... well... the core :p
This makes an incredible amount of sense. Hm...

So...at full load I never surpass 63*C. I know the Tjunction is 85*C, and I don't wanna get anywhere near that. :eek: But...since I'll rarely be at full load; is this anything to worry about?
 
Getting there.

Get up to 8 hrs on Orthos ;)

Temps are about what mine are on water too.
 
Getting there.

Get up to 8 hrs on Orthos ;)

Temps are about what mine are on water too.

I'll settle for 4 hours so I can get myself in the dabatase. I'll run it overnight, though, so I'll probably hit 8 hours unless something goes horribly wrong. ;)

Plus, I don't want to run Windows any longer than I have to.
 
Below say 65-70 degrees in CoreTemp, and you needn't worry. I regularly pushed my Core 2 Duo system to above 65 degrees, with nary a problem.

Of course, the comptuter more or less blew up, but I think it was an unrelated PSU problem. :p
 
^^

Running OCCT to see if my 3.43 is stable. Got a little more daring with the voltage.

If my computer just flat-out reboots during OCCT, what could that mean? Memory timings? vCore?
 
My experience with this chip is low vCore will cause the reboots, but in order to suffice the low vCore, you end up with killer temps by increasing it.. Keep playing & you'll find the sweet spot.
My max stable seemed to be around 3.4GHz, but on a fairly low vCore. I keep it around 3.0 now because I've found the best balance of both. By the way, this CPU has been traded :( .. sending it out early next week because I've got an e6600 arriving.
 
OCCT seems to have passed at 3.43, 1.4 vCore (O_O). Temps aren't horrible (watercooling).
 
Haha. Found a big source of my high temps. My GPU was the first in the loop, the CPU last. :eek:

Switched that around, and cut the tubes so they're much shorter. Temp drop! Now I bounce between 58/63 load!

EDIT: TAT reports an average of 59. Since it's an Intel program, should I trust its results more than CoreTemp?
 
Back
Top