mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Hardware (https://www.mersenneforum.org/forumdisplay.php?f=9)
-   -   Slow overclocking Q6600 (https://www.mersenneforum.org/showthread.php?t=10681)

henryzz 2008-09-20 19:57

Slow overclocking Q6600
 
i tried to overclock my new Q6600 G0 today and found that what ever i did i could not overclock it past 295x9:surprised what i have read over the last few weeks that is a very bad overclock for a Q6600:cry:
here is the benchmark:
[code]
Compare your results to other computers at [URL]http://www.mersenne.org/bench.htm[/URL]
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
CPU speed: 2655.09 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: 15.642 ms.
Best time for 896K FFT length: 18.714 ms.
Best time for 1024K FFT length: 21.239 ms.
Best time for 1280K FFT length: 26.522 ms.
Best time for 1536K FFT length: 32.389 ms.
Best time for 1792K FFT length: 38.514 ms.
Best time for 2048K FFT length: 42.722 ms.
Best time for 2560K FFT length: 56.466 ms.
Best time for 3072K FFT length: 68.907 ms.
Best time for 3584K FFT length: 82.005 ms.
Best time for 4096K FFT length: 91.620 ms.
Best time for 5120K FFT length: 117.310 ms.
Best time for 6144K FFT length: 141.671 ms.
Best time for 7168K FFT length: 172.317 ms.
Best time for 8192K FFT length: 188.863 ms.
Timing FFTs using 2 threads.
Best time for 768K FFT length: 8.319 ms.
Best time for 896K FFT length: 9.877 ms.
Best time for 1024K FFT length: 11.463 ms.
Best time for 1280K FFT length: 13.767 ms.
Best time for 1536K FFT length: 16.841 ms.
Best time for 1792K FFT length: 19.951 ms.
Best time for 2048K FFT length: 22.304 ms.
Best time for 2560K FFT length: 29.284 ms.
Best time for 3072K FFT length: 35.670 ms.
Best time for 3584K FFT length: 42.429 ms.
Best time for 4096K FFT length: 47.601 ms.
Best time for 5120K FFT length: 61.296 ms.
Best time for 6144K FFT length: 75.265 ms.
Best time for 7168K FFT length: 90.905 ms.
Best time for 8192K FFT length: 102.191 ms.
Timing FFTs using 3 threads.
Best time for 768K FFT length: 9.467 ms.
Best time for 896K FFT length: 10.624 ms.
Best time for 1024K FFT length: 15.603 ms.
Best time for 1280K FFT length: 11.352 ms.
Best time for 1536K FFT length: 13.666 ms.
Best time for 1792K FFT length: 16.125 ms.
Best time for 2048K FFT length: 18.123 ms.
Best time for 2560K FFT length: 23.814 ms.
Best time for 3072K FFT length: 29.096 ms.
Best time for 3584K FFT length: 34.356 ms.
Best time for 4096K FFT length: 38.846 ms.
Best time for 5120K FFT length: 48.591 ms.
Best time for 6144K FFT length: 59.210 ms.
Best time for 7168K FFT length: 71.673 ms.
Best time for 8192K FFT length: 80.419 ms.
Timing FFTs using 4 threads.
Best time for 768K FFT length: 8.418 ms.
Best time for 896K FFT length: 9.542 ms.
Best time for 1024K FFT length: 13.747 ms.
Best time for 1280K FFT length: 10.042 ms.
Best time for 1536K FFT length: 11.739 ms.
Best time for 1792K FFT length: 13.552 ms.
Best time for 2048K FFT length: 15.325 ms.
Best time for 2560K FFT length: 19.143 ms.
Best time for 3072K FFT length: 23.392 ms.
Best time for 3584K FFT length: 27.552 ms.
Best time for 4096K FFT length: 31.331 ms.
Best time for 5120K FFT length: 39.276 ms.
Best time for 6144K FFT length: 47.434 ms.
Best time for 7168K FFT length: 57.741 ms.
Best time for 8192K FFT length: 65.644 ms.
Best time for 58 bit trial factors: 4.006 ms.
Best time for 59 bit trial factors: 4.059 ms.
Best time for 60 bit trial factors: 4.038 ms.
Best time for 61 bit trial factors: 4.008 ms.
Best time for 62 bit trial factors: 6.702 ms.
Best time for 63 bit trial factors: 6.726 ms.
Best time for 64 bit trial factors: 6.239 ms.
Best time for 65 bit trial factors: 6.195 ms.
Best time for 66 bit trial factors: 6.197 ms.
Best time for 67 bit trial factors: 6.177 ms.
[/code]
i havent stress tested it for long yet but it seems to be stable
i have tried increasing the vcore voltage up all the way to 1.432v but that didnt get me any further than 1.232v:glare:
lowering the multiplier doesnt increase the fsb i can take it to
i am using a ASUS P5K-VM motherboard
i spent several hours trying virtually every setting to see if it helped me overclock:smile:

can anybody help me?
:help:

Batalov 2008-09-20 20:40

G0 is a good one. You should be able to better than that, but I cannot give you a specific advice with that m/b.

I can only recite some trivialities, like:
1. Mind the memory frequency. Maybe your box rejects a configuration (by rebooting and restoring) because the memory bails out. You have to keep the memory multiplier reasonable, so that it doesn't push memory into cardiac arrest. The FSB goes up, the multiplier goes down.
2. Get a good cooler.
3. I think I wrote up my experiences in a different thread while it was fresh in my mind. One thing to add - the system had been rock stable for 6 months now (under 4 LLs, needless to say :smile:) where's that thread?....
Found it - [URL]http://mersenneforum.org/showpost.php?p=132198&postcount=39[/URL]

Good luck,
--Serge.

henryzz 2008-09-21 07:18

1. my 1066mhz memory is now running at 984mhz so that shouldnt be a problem
2. i already have a Arctic Cooler Freezer Pro
[URL="http://www.aria.co.uk/Products/Components/Fans%2C+Heatsinks%2C+Coolers/Socket+775/Arctic+Cooling+Freezer+7+PRO+?productId=20729"]http://www.aria.co.uk/Products/Components/Fans%2C+Heatsinks%2C+Coolers/Socket+775/Arctic+Cooling+Freezer+7+PRO+?productId=20729[/URL]
and a very cool case my temps with 1.432v were 52c

295*9 failed the stress test
i reduced to 290*9 and that has been running now for 11 hrs

em99010pepe 2008-09-21 10:20

1º - Turn off EIST, C1E and Intel Speedstep on your BIOS settings
2º - Set PCI Express Frequency to 100MHz and PCI Clock Synchronization to 33.33 MHz.
3º - You can flash the BIOS
4º - Read this [url=http://www.tomshardware.co.uk/forum/240001-11-howto-overclock-quads-duals-guide]guide[/url].

henryzz 2008-09-21 12:24

[quote=em99010pepe;143327]1º - Turn off EIST, C1E and Intel Speedstep on your BIOS settings
2º - Set PCI Express Frequency to 100MHz and PCI Clock Synchronization to 33.33 MHz.
3º - You can flash the BIOS
4º - Read this [URL="http://www.tomshardware.co.uk/forum/240001-11-howto-overclock-quads-duals-guide"]guide[/URL].[/quote]
1º already done
2º already done pcie frequency dont have setting for pci clock
3º i am on the second to last version of the bios the web page says the only change is adding more cpus
4º this made me think about other voltages my motherboard only has settings for vcore and memory voltages is there a way of unhiding the rest on this board ctrl F1 does it on some motherboards(when i have finished 24hrs of stress testing with v25.6 i will have a play)?
the crashes i have so far have had are either refusing to boot or just freezing

S485122 2008-09-21 16:25

Asus "-VM" boards are their low range offer. You do not have many tuning options. For instance there is no way you can feed apropriate voltage to fast memory. They are not advertised by Asus as overclocking friendly.

It is a pity but the market for on board graphic motherboards is linked to performance.

As far as I know there are no hidden setup options on Asus bios'es.

Jacob

henryzz 2008-09-21 17:29

there is certainly no way i could overclock my memory much as i am at the top voltage the motherboard supports to get stock speed

lavalamp 2008-09-22 05:09

I have the P5B-VM board, very similar to yours. I tried overclocking my E6600, but it crapped out before I even got to 275*9.

henryzz 2008-09-22 06:22

seems like they are bad boards to overclock with
i supose its what comes with trying to get a cheapish board

290*9 passed 24.5 hrs of stress testing

henryzz 2008-09-30 16:56

throughout last week i wondered why my motherboard specically said it supported 800/1066/1333 system bus speeds and i came to the conclusion that the motherboard wasnt supposed to support my current system bus speed of 1160 but was supposed to support 1333 so i increased the fsb to 333 so the system bus would be 1333 and it worked!!!
:party:
since then i have stress tested the computer for 24 hours and on the second attempt(i had tried to lower the voltage too much and it failed after exactly 13 hours) it now seems to be stable at 333*9=almost 3ghz
it wont go any further than this although i am quite happy at this speed

lavalamp 2008-09-30 21:51

Nice, I might have to try that with this machine then. I don't hold out much hope, but it's worth a try.


All times are UTC. The time now is 06:02.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.