Overclocking a q6600 help

q6600 guys - I'm thinking of getting one soon, gonna be colled under water.

Have any of you guys come across an FSB wall with this chip? EG, my e4300 will not go over 340Mhz...
 
I use Everest to monitor temps, I think Speedfan monitors PWM temps also, but not sure how acurate it is.
 
Roeg1 said:
were do i check that?
Click to expand...

load up the uguru software you got on the install disk, idealy the
pwm temp should be around the 40 degree mark but as mentioned above
it can safely be higher, ive not used speedfan but everest is a good alternative if you have that
 
Last edited:
Tried a prime 95 run last night, blue screened of death after a couple of minutes each time. thou sat stable doing basic task for 2 hours, even let me game for 20 minutes np.

Soons i load prime thou it crashes hard within 5 minutes..

Up the volts on vcore or what ?
rams at 2.1 so that should be ok i guess?


Btw thxs for all the help :D much appreciated
 
I went from 1.225 vcore @ 2.4 ->3.2, then I had to raise it to 1.3750 in BIOS to be stable @ 3.4, just keep an eye on your temps.
 
Last edited:
Roeg1 said:
Tried a prime 95 run last night, blue screened of death after a couple of minutes each time. thou sat stable doing basic task for 2 hours, even let me game for 20 minutes np.

Soons i load prime thou it crashes hard within 5 minutes..

Up the volts on vcore or what ?
rams at 2.1 so that should be ok i guess?


Btw thxs for all the help :D much appreciated
Click to expand...

yeah, just move the vcore, if you look at the pic i posted earlier the droop is pretty bad knocking 1.31 down to 1.28
 
Last edited:
Baked said:
91797079oi3.jpg


i would set your ram down to 1/1 to rule it out, i used the 8x multiplier (8*400) for 3.2 this
also meant the ram was at 800mhz on 1/1
Click to expand...


Not to go too off topic, where did you get this presumably vista sidebar addon?
 
Running prime now and it primes for a minute and then the 3rd core dies..

other 3 run np's for 15 minutes havent tried longer yet as core 3 keeps getting errors ?

vcore at 1.31 now


[Fri Feb 08 02:23:24 2008]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sat Feb 09 19:00:21 2008]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Compare your results to other computers at http://www.mersenne.org/bench.htm
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
CPU speed: 3599.90 MHz, 4 cores
CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2
L1 cache size: 32 KB
L2 cache size: 4096 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 256
Prime95 32-bit version 25.6, RdtscTiming=1
Best time for 768K FFT length: 13.337 ms.
Best time for 896K FFT length: 15.953 ms.
Best time for 1024K FFT length: 18.266 ms.
Best time for 1280K FFT length: 22.710 ms.
Best time for 1536K FFT length: 27.614 ms.
Best time for 1792K FFT length: 32.876 ms.
Best time for 2048K FFT length: 36.505 ms.
Best time for 2560K FFT length: 48.108 ms.
Best time for 3072K FFT length: 58.797 ms.
Best time for 3584K FFT length: 69.841 ms.
Best time for 4096K FFT length: 78.042 ms.
Best time for 5120K FFT length: 100.173 ms.
Best time for 6144K FFT length: 120.816 ms.
Best time for 7168K FFT length: 147.512 ms.
Best time for 8192K FFT length: 162.478 ms.
Timing FFTs using 2 threads.
Best time for 768K FFT length: 7.234 ms.
Best time for 896K FFT length: 8.647 ms.
Best time for 1024K FFT length: 10.176 ms.
Best time for 1280K FFT length: 12.224 ms.
Best time for 1536K FFT length: 14.748 ms.
Best time for 1792K FFT length: 17.520 ms.
Best time for 2048K FFT length: 19.560 ms.
Best time for 2560K FFT length: 25.626 ms.
Best time for 3072K FFT length: 31.291 ms.
Best time for 3584K FFT length: 37.210 ms.
[Sat Feb 09 19:05:51 2008]
FATAL ERROR: Resulting sum was 2.549858937444762e+016, expected: 3.214959828929516e+016
Hardware failure detected, consult stress.txt file.
 
how comes you say 1,2,4 and core 3? lol. Just seems a bit strange tahts all.

I doubt he is crashing because of heat a 3.2ghz unless his heat sink is badly seated. Inwhich case he wouldn't get errors it would just cut out.
 
ok uping it to 1.4 as we speak and will start a prime in about 2 minutes.. temp across cores is a range of 10 degrees as an example it normaly sits at 24-34 degrees depedning on what core u measure.
 
prime fine on 1.4 started to drop the vcore then to see how low i could go before the 3rd core dropped out again.

vcore = 1.3475 before it would prime without the 3rd core dropping out.

Just tested it for half and hour and all seems well apart from the vcore drop..
cpu-z reads it at vcore 1.33 IDLE

When priming this drops as low as 1.28 flutuating around a 1.30 1.31 constant with drops down to 1.28 :confused:
These seems a very bad drop, also temps under load = hotest core on 58-59 this ok ?
 
Anyone willing to give me the remaining info so i can get this stable after work tonight..
just worried about the drop and overall temps seem a little high for the Ocing im doing
 
You must log in or register to reply here.
Back
Top Bottom