Overclocking a q6600 help

can anyone give me the exact figures i need for the ram in the bios i no its 5-5-5-15 or 4-4-4-12 but what about the rest of the figures in the ram timmings theres about 10 to set.

And how much should i push the vcore up from the stock setting to get it stable at 3.2?
 
Update tried the weekend at 3ghz resulting in a a crash to restart after 15 minutes of OCCT testing on *** cpu at 3ghz,, I then dropped it down to 2.6 just to try and the sme thing happened with 15 minutes the computer had restarted..

Anyone help me get this Oc'ed to a decent level and stable ??
 
ok baked that seemed to of worked thxs..

Doesnt the 8x400 push the Rated FSB to 1600mhz thou and isnt the cap 1333 on this mobo

Ive also got it to boot at 333x9 now at 1:1:20 rated fsb 1333mhz
This also gives 800mhz for the ram but at a different ratio.

It was the memory after all. :) so which of those overclocks are the best ?
And now for ram timmming anyone help me getting those perfect now instead of all at auto/SPD

O core temp also sees my cpu at 3.6ghz thou cpu-z says 3.2 and so does the bios. Is this normal?
 
no all thats turned off what im saying is

i can run at 2 different oc's ive found since u posted how to get it to boot.

one 333mhz fsb 9x multiplier with ram at a 1:1:20 ratio =3ghz and a fsb rated at 1600mhz

two 400mhz 8x multiplier with ram at 1:1 ratio = 3.2ghz and a fsb rated at 1600mhz

Now the mobo i use says max of 133mhz for fsb rating, so its the 8x bad for the mobo and which is the best overlock the 9x or 8x cpu speed aside i can see the difference there. im just worried about the fsb rating at 1600mhz
 
Baked said:
at 3.2 your fsb is 400 not 1600

try priming on either, i prefer using the 8x for this memory

FSB rated at 1333 not 133
Click to expand...
that was type error i meant 1333

cpu z- reports it as being at 1600mhz 100% thats the reading being reported using your figures, its beeen running 2 hours stable now thou
 
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
 
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.
 
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