-
Notice regarding image hosts and attachments. See here.
Q6600 help clocking over 3ghz
- Thread starter Guest2
- Start date
That looks like your bios is undervolting by 0.04 (the max on HW Monitor), then on top of that your board is getting vdroop of 0.05 (the min on HW Monitor).
So in other words, whatever you set in the bios is actually 0.09v lower during load!
That explains a lot. Try raising vcore to 1.54 with 9x 378 and see what happens. That should be a voltage of 1.45 under load.
1.45 or even a little more should be fine as you're under water. I am running 1.43 at load on air.
You can enable Speedstep etc once we find your max settings, and this will keep volts and temps lower until needed.
Remember to keep HW Monitor open and watch your vcore during load. Your temps are spot on too, well within spec.
So in other words, whatever you set in the bios is actually 0.09v lower during load!
That explains a lot. Try raising vcore to 1.54 with 9x 378 and see what happens. That should be a voltage of 1.45 under load.
1.45 or even a little more should be fine as you're under water. I am running 1.43 at load on air.
You can enable Speedstep etc once we find your max settings, and this will keep volts and temps lower until needed.
Remember to keep HW Monitor open and watch your vcore during load. Your temps are spot on too, well within spec.
Last edited:
thanks for the quick replies. At 1.55v bios (1.45 right) one of the workers stopped after about 10 - 15 seconds
1.56250v bios (1.47 proper) lasted a couple of minutes before crashing. Temperatures then hit 68c. Is it ok to run as many volts as is necessary without the temps getting too high?
edit - i had it at 1.57500V, 1.3 termination, 1.6pll, 1.4mch and it lasted about 6 minutes before straight out blue screening
1.56250v bios (1.47 proper) lasted a couple of minutes before crashing. Temperatures then hit 68c. Is it ok to run as many volts as is necessary without the temps getting too high?
edit - i had it at 1.57500V, 1.3 termination, 1.6pll, 1.4mch and it lasted about 6 minutes before straight out blue screening
Last edited:
Hey mate, sorry for the delayed response.
I wouldn't go much higher than around 4.5 - 4.8 for day to day usage. You could try a little higher for benchmarks, but I certainly wouldn't suggest you go over 1.5 (real under load).
I would say you might have to settle for 3.2 - 8x 400. It's a very decent overclock anyway
You can if you like try something else. Drop back down to the 8x multi and see if you can raise the FSB a little more to get the higher clockspeed.
So try this...
8x 413 (3.3ghz)
and/or
8x 425 (3.4ghz)
CPU Vcore - 1.525
CPU Termination - 1.29 (this might need raised a little more due to the higher FSB)
CPU PLL - 1.55
CPU Reference - Auto
CPU Reference 2 - Auto
MCH Core - 1.3
MCH Reference - Auto
MCH/DRAM Reference - Auto
ICH I/O - Auto
ICH Core - Auto
DRAM Voltage - 2.0
Check when you set this that your memory is not being pushed over DDR2-800. If it is, then change the memory divider so that it is either 800 or less.
Give this a go and report back with results.
I wouldn't go much higher than around 4.5 - 4.8 for day to day usage. You could try a little higher for benchmarks, but I certainly wouldn't suggest you go over 1.5 (real under load).
I would say you might have to settle for 3.2 - 8x 400. It's a very decent overclock anyway
You can if you like try something else. Drop back down to the 8x multi and see if you can raise the FSB a little more to get the higher clockspeed.
So try this...
8x 413 (3.3ghz)
and/or
8x 425 (3.4ghz)
CPU Vcore - 1.525
CPU Termination - 1.29 (this might need raised a little more due to the higher FSB)
CPU PLL - 1.55
CPU Reference - Auto
CPU Reference 2 - Auto
MCH Core - 1.3
MCH Reference - Auto
MCH/DRAM Reference - Auto
ICH I/O - Auto
ICH Core - Auto
DRAM Voltage - 2.0
Check when you set this that your memory is not being pushed over DDR2-800. If it is, then change the memory divider so that it is either 800 or less.
Give this a go and report back with results.
I tried 8 x 425 and errored in prime. We'll see how i get on when 2x2gb arrive, hopefully tomorrow. C64, i suppose you are right but when i spend £50 on a cpu cooler i expect it to be able to overclock at least 200mhz higher, being that load temps are down 25c from before on a scythe heatsink
Last edited:
I think you might have found your CPUs ceiling. Yes you can probably get a little bit higher, but its starting to look like a silly amount of volts are going to be needed to get there.
Will be watching with interest to see if the new memory helps, but I am not certain. Although what it will allow is more flexibility, and even if you can't get higher than 3.2 (which don't forget is already 200mhz up on your previous efforts
) you will have the possibility of using a lower multi and higher FSB to get there.Nice ninja edit
but the original came into my inbox 
And tbh I didn't think 70c topping out in Prime was all that bad at 3.6 running 1.43v through the CPU. That was recorded with my tjmax at 100c too, so the actual temp was probably some 5-10c lower.
Last edited:
No worries nothing bad meant in what I had said, it's because I have just bought the same case as you and was a little surprised/concerned temps weren't lower is all.I expected 60-65c maximum which sounds about right reading the above.
Last edited:
Yeah, no probs. I wasn't getting at you, just thought I would explain the temps.
Its a great case by the way, just don't forget to remove as many of the HDD bays as possible to allow good airflow towards your GFX card/s from the big intake fan
Associate
- Joined
- 23 Mar 2009
- Posts
- 2,014
- Location
- Peterborough
Heya Guest2 how's the clocking going? i've been following your thread with interest as i've been meaning to push my Q6600 a little further. I play RTS games and it would seem my bottleneck is now my CPU. I have a similar setup to you (see sig) and was wondering if you have any tips? I'm actually running a stability test at 3.2ghz now (IBT)
Hi Skippy. I tried some Corsair Dominator and it doesnt like my board for some reason, I left it at 400 x 8 for 3.2ghz and upped the memory divider so it gives 1066 on memory and it resets to 1600mhz (5-7-5-24 instea dof 5-5-5-15) I then tried 533 x 6 and this did the same. I'm selling it on because cant be bothered sorting out what the problem is.
At the moment im 100% stable on 3.2ghz with decent enough temps so ill stick with the memory i have for now
Yesterday I bought a lapped Q6600 on here for £65 that is apparently capable of 3.6ghz @ 1.45v (load) with tuniq 120, max temps 65c. I'll chuck this into my pc on monday night and see how I get on. If it is a better clocker then i'll sell mine on, if its not then i'll sell it on.
No big loss, nothing to lose really
At the moment im 100% stable on 3.2ghz with decent enough temps so ill stick with the memory i have for now
Yesterday I bought a lapped Q6600 on here for £65 that is apparently capable of 3.6ghz @ 1.45v (load) with tuniq 120, max temps 65c. I'll chuck this into my pc on monday night and see how I get on. If it is a better clocker then i'll sell mine on, if its not then i'll sell it on.
No big loss, nothing to lose really
I now have my new (cheaper) lapped Q6600 installed. Bumped it straight up to 3600mhz from 3200. Cpuz is reporting 1.440 under load. Bios about 1.53 So far its done a few minutes of prime without crashing
I tried it at 3700 with higher volts 1.6 something and it was ok for a minute then got an error.
Good stuff, going to sell my Q6600 for same as i paid for it, which i should easily get - £85 and keep this one. I suppose 3.2ghz is still a good clock, just not as good as 3.6 or 3.7!
edit - Just noticed the vid of the one before is 1.3250v, This one is 1.3125
I tried it at 3700 with higher volts 1.6 something and it was ok for a minute then got an error.
Good stuff, going to sell my Q6600 for same as i paid for it, which i should easily get - £85 and keep this one. I suppose 3.2ghz is still a good clock, just not as good as 3.6 or 3.7!
edit - Just noticed the vid of the one before is 1.3250v, This one is 1.3125