Q6600 G0 - A bit of Advice - please

Later :)

No problem with having left CPU Enhanced Halt, CPU Thermal Monitor 2 and CPU IEST Function enabled during testing?.
 
Last edited:
One of them will reduse the cpu multi when not on load, the other will shut it down if to hot.
Seriosly, have a look at other people's clocks, it will save you 'creeping' up to your clock.

Anyway, go to bed, it's late!
 
Monstermunch said:
Turn all of that carp off, if you wanna actually achieve anything!
Click to expand...

Are you saying that leaving them enabled means the testing was worthless because there could be some throttling taking place.
The more I increase the clock the more throttling.

Or are you saying that it's holding the overclocking back and I could achieve a higher speed with them disabled?
 
Marse said:
Are you saying that leaving them enabled means the testing was worthless because there could be some throttling taking place.
The more I increase the clock the more throttling.

Or are you saying that it's holding the overclocking back and I could achieve a higher speed with them disabled?
Click to expand...

It's all that speedstep crap, & yes throttling....

There is no point trying to clock with that stuff on, u may as well not bother
 
15wmd90.png



  1. So this test was meaningless because although it shows 3.4 it could in fact have been throttling back and not achieving anything like the performance you would expect from 3.4?

  2. There is no point in enabling any of those options after testing once you have a stable clock because it may simply throttle again?

  3. What's the point in people posting pics showing how well they've overclocked and comparing results when they could have left these options enabled which could suggest speeds which in practice may be unrealistic or unusable?

  4. Is there a simple way of checking if throttling is taking place?


I thought this was too easy.
 
Last edited:
Dont worry, yours is fine

under 100% load it wont throttle

CPU-Z is about the only thing that you should believe.... If it says 3.4ghz, then thats what you have!

but if you leave all that crap enabled it will hinder general performance in windows, stop you from clocking further than u actually can & just generally be something written by microsoft and do things that it thinks you want it to do, rather than what you tell it to do!
 
You had me worried there for a minute or two.

First build and first overclock – I’m chuffed to bits – I think.

I’m still surprised at 3402 for 9 hours [ someone put the clock back during the test ] with an average temp of 52 C - per Everest.
The temps didn’t seem to increase after about 2.8 GHz but I'm not complaining.

Barring further mishaps I’m giving some thought how to proceed next.

I’m not really after the maximum possible, I just want as much as I comfortably can get without pushing anything too hard.

I went straight to 3.6 from 3.4 and it was ok until stress testing so perhaps start to head up towards 3.5 and see what happens?

The memory is specified at 4.4.4.12.
At default the BIOS sets the System Voltage Control to Manual which gave 1.9v for the Ram and timings 5.5.5.18.
Once on Auto the voltage increased to Corsair’s default of 2.1 and the timings changed to 5.4.4.12.
They’re now on 5.5.5.18

Would sorting them be a better prospect for everyday use than a bit of extra speed?

Edit: I was using small FFT's which I thought was recommended. Is the Blend option a 'better' test?
 
Last edited:
Really, you're better off with pretty much nothing on auto!

Set your ram to the manufacturers recommended voltage manually, then slacken the timings to 6-6-6-18 while colcking (worry about them later)

If you're on air cooling (depending how good it is) you should be safe with a vcore of 1.4 to 1.45 without overheating issues...

Watch the temps with coretemp, anything above 70deg is not good

But to give you an idea, I managed to get mine stable at 3.5ghz on air with a scythe ninja.
 
You must log in or register to reply here.
Back
Top Bottom