Quick overclock question for those in the know

Associate
Joined
26 Jan 2005
Posts
221
Location
Dorset
I am new to overclocking and have a simple question if anybody can help.

I am using a Quad core 6600 CPU and wish to clock it to 3 GHz.
I am air-cooled but it is a decent Zalman jobby.
I also want to get the most out of my RAM.
I am using PC8500 (1066MHz) RAM.
I am using an ABit IX-38 Quad GT Motherboard.

In the BIOS the DEFAULTS are:
External Clock 272MHz
Multiplier X9
Estimated new CPU Clock 2448MHz
DRAM Speed (CPU : DRAM) DDR2-816

If I increase the External Clock to 334MHz this gives me an Estimated new CPU Clock of 3006MHz and a DRAM Speed (CPU : DRAM) of DDR2-1002.

Does this achieve what I am trying to do?

Do I need to make any changes in the "Voltages Control" part of my BIOS?

Thanks
 
They are funny readings

At STOCK the CPU is a 1066mhz FSB so 266mhz x 4 (Quad Pumped), Memory only needs be 533mhz DDR to be In Sync 1:1

For 3GHZ you need a 333mhz FSB x 4 =1333mhz FSB (Quad Pumped), Memory only needs be 667mhz DDR to be in Sync 1:1

You do not need Memory running over 1000mhz.
 
Last edited:
I am new to overclocking and have a simple question if anybody can help.

I am using a Quad core 6600 CPU and wish to clock it to 3 GHz.
I am air-cooled but it is a decent Zalman jobby.
I also want to get the most out of my RAM.
I am using PC8500 (1066MHz) RAM.
I am using an ABit IX-38 Quad GT Motherboard.

In the BIOS the DEFAULTS are:
External Clock 272MHz
Multiplier X9
Estimated new CPU Clock 2448MHz
DRAM Speed (CPU : DRAM) DDR2-816

If I increase the External Clock to 334MHz this gives me an Estimated new CPU Clock of 3006MHz and a DRAM Speed (CPU : DRAM) of DDR2-1002.

Does this achieve what I am trying to do?

Do I need to make any changes in the "Voltages Control" part of my BIOS?

Thanks


Hi mate the above is what i ahve done to mine. Upped the FSB to 333 x9

Runs sweet the mem is also running nicely at a 1:1 i would do as you stated above. up the fsb to 333.
 
Hi JackCarver.

Need I worry about anything else?
Voltages?

EDIT: Whoops I upped the FSB to 334 (and changed nothing else) and I got a BSOD!

Surely I shouldn't give up?
 
Last edited:
For 3.0 Ghz on the CPU and stock speeds (ish) for your RAM you'd need:

333 FSB
x9 Mulitplier
1.5x FSB:DRAM ratio

This makes 3 Ghz, for RAM you want x1.5 ratio (same as you have at stock, ie. 272 x 1.5 = 408, x2 due to DDR2 then that makes 816) which'll give you 1000 Mhz (333 x 1.5 x 2) DDR2 and that's close enough. If you wanted the RAM at stock you'd need the FSB at 350... which of course at x1.5 would make 333 x 1.5 x 2 = 1065 Mhz, although that brings the CPU at 3.2 Ghz. You may need voltage changes in this.

Open up Core Temp in Windows with Speedstep disabled in the BIOS, run Prime95 to get the CPU at full load and then check Core Temp's "VID" and that'll give you the basic and default vcore for the CPU. Then go back into the BIOS, change the vcore from "Auto" to whatever the Core Temp's "VID" was and start increasing the FSB in jumps of about 5 - 20 FSB at a time (note that 1 FSB = 9 Mhz due to the multiplier, so 20 FSB is 180 Mhz). When you reach what you want (3.0 Ghz or 3.2 Ghz) then I would stress test the CPU overnight in Prime95 for 8hrs+ to make sure that it is totally stable. If you start getting BSOD's before you reach your target, or Prime95 isn't stable and you get errors at 3.0/3.2 Ghz then you may need a vcore increase (very small one though) to make it stable.

Some people also say that you should do one at a time, which is logical as it's easier to do CPU by itself than CPU and RAM together. So for this, you just need to reduce the x1.5 ratio to something lower, like say x1.25 and even if you had 350 FSB (for 3.2 Ghz on the CPU) then RAM would only be 350 x 1.25 x 2 = 875 Mhz, and well under stock. Then once the CPU is stable, you can start playing with the RAM by adjusting the ratio's / timings and volts to get that where you want it, and when that is done - stess both with a "Blend" in Prime95 to achieve stability.

Also - make SURE you lock the PCI-E lane(s) to 100 Mhz, if you leave them on auto you will corrupt your sata drives and you may need to format them, which is a right nightmare.
 
Quoted " If I increase the External Clock to 334MHz this gives me an Estimated new CPU Clock of 3006MHz and a DRAM Speed (CPU : DRAM) of DDR2-1002. "

Your Memory should not be 1000mhz, on a Asus thats 1:1 not In Sync (Asus name it weird), the Memory normally is 1/2 your Quad Pumped FSB so 1333/2= 667.

Now as it aint trying to make your Memory 1333mhz, I think you have a DIVIDER SET.
 
FAO flibby or anybody else who can help......

What does flibby mean above when he talks about disabling Speedstep?

He also talks about making a very small increase in the vcore value to make it stable. What should this increase be typically?

Should I attempt to use ABit's uGuru application to do my overclocking or is it better done in the BIOS?

Many thanks for your help guys.
 
What does flibby mean above when he talks about disabling Speedstep?
SpeedStep, or it's full name: Enhanced Intel Speedstep Technology (EIST) is technology built into processors that allow them to run at a lower speed by reducing the multiplier so that you use less power and create less heat, however only when the CPU is idle. Because of this it also lowers the processors voltage to a point that makes it stable at the lower speed. I would generally leave this on, however for the point of getting your actual VID from the "Core Temp" program I would disable it for the moment whilst you find out. Once you have the VID then turn it back on and it's very handy.

To disable this you will need to go into your advanced bios features, then into the "CPU Features" part and disable: C1E Function / EIST Function. To enable, just turn C1E back to Auto and EIST to Enabled.

He also talks about making a very small increase in the vcore value to make it stable. What should this increase be typically?
About 0.01v should be enough of an increment. This only really matters if the computer is not stable when you reach your desired Mhz target. If the computer is completely stable when you don't need to adjust the voltage, however if it's not stable when increase it about 0.01v and see if it becomes stable. If not add another 0.01v and you should reach a point where it becomes stable. If it's not becoming stable after you've added about 10 lots (ie. 0.1v) of this then it's probably another reason why your system is not stable, and not the vcore itself. This is only in respect of your overclock however, since you are not aiming for that high of an overclock.

Should I attempt to use ABit's uGuru application to do my overclocking or is it better done in the BIOS?
Always do it from the BIOS, a lot of overclock failures happen during POST / OS loading so it matters a lot to do it from there
 
Hi flibby.

I had read about C1E/EIST in the interim but I still have many questions.

Would there be a chance to communicate via email with you?
Do you use SKYPE?

Anyway I have just written a piece and thought it might help others if I post it here.........

My hardware:

Abit iX38 Quad-GT
Intel Core 2 Quad-Core Q6600 G0
2GB (2x1GB) Corsair TwinX DDR2 XMS2 Dominator, PC2-8500 (1066)
Zalman CNPS9700-LED Super Aero Flower Cooler

I would like to Overclock my CPU to run at 3GHz and although it is air cooled I believe my cooler should get me there.
I would also like to run my RAM at 1066 but I am happy to play with that after I have a stable CPU at 3GHz.

There are several things which have been confusing me.

1) Speedfan and CoreTemp are giving me differing readings for the temps of the 4 cores. Why could this be?

2) I upped the clock to 333, leaving the multiplier at x9 to get my 3GHz without changing anything else. It wouldn't boot. Is this because I need to up some voltages?

3) You say it is better to make changes in the BIOS rather than using an Overclocking applications such as uGuru but due to some indifferences with the iX38 Quad-GT it is sometimes necessary to clear the CMOS after a crash has occured due to an overclock failing. Would it be possible to "try" thing in uGuru and if they work then make them permanent in the BIOS?

4) Am I correct in thinking that uGuru (which starts at bootup) "temporarily" applies the selected settings to the hardware? i.e. it applies any modifications to the standard BIOS settings each and every time it starts up?

5) If I select "Turbo mode" in uGuru it makes the following changes (from and to). Please can you explain them?......

ExtClk: 272 > 293
Target Voltage: 1.3 > 1.45 (CPU VID remains at 1.3_Auto)
CPU Offset: 0.000 > 0.150
CPU VTT: 1.00 > 1.27
MCH 1.25: 1.25 > 1.37
ICH 1.05: 1.05 > 1.12
ICHIO 1.5: 1.50 > 1.60

6) There appear to be so many modifications when selecting "Turbo mode". Would I be correct in thinking that all of these would need modifying in an attempt to get to 3GHz?

7) Which applications should I use to monitor my core temps and load my CPU to check it under load?

8) Once I am happy with my CPU at 3GHz would it be a simple task to get my RAM performing at 1066? How would this be achieved?

Many thanks for any help.
 
Last edited:
Hi flibby.

I had read about C1E/EIST in the interim but I still have many questions.

Would there be a chance to communicate via email with you?
Do you use SKYPE?
Unfortunately I do not use Skype, and only browse this forum and sometimes on IRC.

1) Speedfan and CoreTemp are giving me differing readings for the temps of the 4 cores. Why could this be?
Not sure which you mean by this, so I'll explain both.

If you mean that CoreTemp and SpeedFan are reporting difference temperatures it's normally because SpeedFan doesn't report them correctly and sometimes reports them up to 15c below what they should be. Wherever possible, I would advise using CoreTemp instead of SpeedFan because CoreTemp normally always reports to the temperatures of the cores correctly. If you mean that the core temperatures themselves are different, it's always normally down the IHS (Integrated Heat Spreader) on the CPU which is never perfectly flat - therefore some cores get more contact with the heatsink that others do. This is a very common issue however and nothing to worry about so long as the cores are not more than 10c difference, over that then it would probably indiciate that the IHS is very uneven. Whilst it wouldn't cause issues with the running of the machine, it would limit the overclock unless you lapped the top of the processor to make it more flat.

2) I upped the clock to 333, leaving the multiplier at x9 to get my 3GHz without changing anything else. It wouldn't boot. Is this because I need to up some voltages?
Will answer this one last, so see the bottom of the post for a more detailed response.

3) You say it is better to make changes in the BIOS rather than using an Overclocking applications such as uGuru but due to some indifferences with the iX38 Quad-GT it is sometimes necessary to clear the CMOS after a crash has occured due to an overclock failing. Would it be possible to "try" thing in uGuru and if they work then make them permanent in the BIOS?
I'm not 100% sure how uGuru from Windows works to be honest. Whilst I have looked at it, I'm not sure if the settings it makes are applied directly to the BIOS so the next time you reboot they are in effect, or whether it just changes them when you enter Windows. I would still however use the BIOS for changing stuff. You could try the overclock from the uGuru, but really it won't help much because you could get an overclock seemingly stable in Windows but when you reboot it might not boot properly and you'd have to reset the CMOS anyway.

4) Am I correct in thinking that uGuru (which starts at bootup) "temporarily" applies the selected settings to the hardware? i.e. it applies any modifications to the standard BIOS settings each and every time it starts up?
As mentioned I'm not sure if it loads the settings when the computer starts or if it directly adjusts the BIOS from the Windows program.

5) If I select "Turbo mode" in uGuru it makes the following changes (from and to). Please can you explain them?......

ExtClk: 272 > 293
Target Voltage: 1.3 > 1.45 (CPU VID remains at 1.3_Auto)
CPU Offset: 0.000 > 0.150
CPU VTT: 1.00 > 1.27
MCH 1.25: 1.25 > 1.37
ICH 1.05: 1.05 > 1.12
ICHIO 1.5: 1.50 > 1.60
Turbo mode is just like a built in overclock setting that the manufacturer has made, although normally they are well over the settings they should be at. Those settings mean:

Target Voltage: This is the CPU voltage
CPU Offset: I'm told this to help combat vdroop
CPU VTT: This is the voltage for the CPU FSB from the CPU to the Northbridge
MCH 1.25: This is the Northbridge voltage
ICH 1.05: This is the Southbridge voltage
ICHIO 1.5: This is the Intel IO Hub Controller voltage

6) There appear to be so many modifications when selecting "Turbo mode". Would I be correct in thinking that all of these would need modifying in an attempt to get to 3GHz?
Lots of the settings that it changes don't need to be changed, BIOS turbo modes and "auto" settings tend to go a bit mad with the voltages and changing settings.

7) Which applications should I use to monitor my core temps and load my CPU to check it under load?
Use CoreTemp to monitor the temperatures for the cores, it's the best program. If you want to properly load the cores to test stability then use the Quad version of Prime95 which is the best program for that type.

8) Once I am happy with my CPU at 3GHz would it be a simple task to get my RAM performing at 1066? How would this be achieved?
Yes this would be the best idea. I would underclock the RAM and just work on the CPU to 3Ghz, then once you have the CPU stable, work on getting the RAM back to stock. This eliminates any problem with the RAM causing issues with your overclock. See below on how the best way to do this is.


Okay in response to No. 2 and a little of No. 8....

Try the following:

1. Go into "Advanced BIOS Features", then into "CPU Feature" and disable: "C1E Function" and "EIST Function" --- This turns off Speedstep, we are doing this so you eliminate any problems with instability caused by Speedstep reducing the vcore when the CPU is idle.

2. Go into the "uGuru Utility" and change the following:

CPU Operating Speed: User Defined
External Clock: 266 Mhz *** Note: This is 266 Mhz on purpose ***
Multiplying Factor: X 9
DRAM Speed (CPU : DRAM) -> 1:1.20
PCI Express Clock: 100 Mhz

3. Then go back to the main BIOS selection pages and go into "Advanced Chipset Features" and set the timings of the RAM (it's the first option) to "By SPD" if you have them on manual.

4. Go back into the uGuru Utility and then go into the Voltage Control and set these options:

CPU Core Voltage: 1.3500v
DDR2 Voltage: 2.1v
CPU VTT Voltage: 1.2v
MCH 1.25v Voltage: 1.33v
ICH 1.05v Voltage: 1.15v
ICHIO 1.50v Voltage: 1.55v

When you have changed all those options, save and exit the BIOS and if the machine restarts, boot into Windows and make sure you don't get any restarts. When you are in Windows, just restart the machine and go back into the BIOS. When you are back into the BIOS, go into the "uGuru Utility" and change the "External Clock" to 334 Mhz (note: 334, not 333). Then save and exit and hopefully the machine should restart normally and you should get into Windows. What you want to do from here is immediately check the temperatures of the CPU using Core Temp. Then if all looks swell, run Prime95 for 8hrs+ to ensure stability and after that it's just a case of getting the RAM back to what you want it at (i.e 1000 - 1066 Mhz).

Let me know how you get on!
 
Last edited:
It's very generous of you to spend all that time helping me (and others) flibby - cheers.

I shall do all you ask (and report back) straight after dinner which I am about to have :D

Give me an hour ;)

In the mean time can I just ask whether there IS a quad version of Prime95 or are we just talking about the latest version here?
 
In the mean time can I just ask whether there IS a quad version of Prime95 or are we just talking about the latest version here?
Aye, you can download it direct from here. By default the prority is set to 1, which is very weak, so I'd go into File->Worker Threads and set the CPU priority to around 6.
 
Well I've not had much success :eek:

I modified the settings you suggested and rebooted (at this stage I hadn't upped the Clock to 334).

The machine started to boot but about 5 seconds into booting it rebooted, this time booting up into Windows.
I then rebooted and hit DELETE to go into the BIOS. All settings were back to their original settings.

How could this have happened?
 
That normally happens when something is causing it to be completely unstable, it just resets itself back to factory settings. I'm not sure what it could be other than the RAM.

Okay firstly I think we need to find some stock settings that work but not set to auto, your board seems to be being picky, either that or you RAM doesn't like running that low below stock. I would try again with the following settings:

uGuru Utility - Main Page
External Clock: 266 Mhz
Multiplying Factor: X 9
DRAM Speed (CPU : DRAM) -> 1:1.50 (DDR2-800) *** Make sure this says 800, or close enough, ie. 798/799/801 etc
PCI Express Clock: 100 Mhz

Voltage Control
CPU Core Voltage: 1.2375v
DDR2 Voltage: 1.8v
CPU VTT Voltage: 1.2v
MCH 1.25v Voltage: 1.25v
ICH 1.05v Voltage: 1.05v
ICHIO 1.50v Voltage: 1.50v

Advanced Chipset Features
DRAM Timing Schedule: Manual

After that are a bunch of numbers, the first four are going to be changed starting with the CAS Latency Time and ending with the Precharge delay, so set those in order from top to bottom as:

5
5
5
18

Leave all the other settings on that page

Double check all the settings in case you've missed one or left something on auto by accident. After that, save and exit and try booting and see if you run into any problems. This is basically just forcefully setting everything to stock other than RAM which we are setting at 800 Mhz. I've checked our your RAM and it is, by the SPD, able to run at 800 Mhz with 1.8v using timings of 5-5-5-18 so that is basically stock with 1.8v. I have made one assumption however in that your CPU VID is 1.2375v as most newer ones using the G0 stepping are - but this may be different, if you know what it is then set the CPU Voltage as what the VID is.

See if that works.
 
I have some questions....

What is VDroop?
What is the CPU core voltage offset used for?
The "Target CPU Core Voltage" appears to be a combination of the CPU VID and the offset. What is this used for?

I have heard that the IX38 Quad GT is particularly good in the VDroop department but how do I "enable" this feature?

Thanks again. I am making some tests at present and shall report back.
 
What is VDroop?
Vdroop is a drop in the CPU voltage when the processor is under load. For instance if you have 1.2375 VID, then that is the voltage mainly for idle but when under load you'll probably find it's more like 1.22v. The drop in voltage is called "vdroop".

What is the CPU core voltage offset used for?
See post #20.

The "Target CPU Core Voltage" appears to be a combination of the CPU VID and the offset. What is this used for?
Target CPU Core Voltage will be the actual core voltage, consisting of both the VID and the offset. Offset is apparantly just another way to add additional volts to the CPU when you reach the cap from the VID. See post #20 below for more info.

I have heard that the IX38 Quad GT is particularly good in the VDroop department but how do I "enable" this feature?
You can't enable it, and it's probably a good thing you can't. Vdroop is generally seen as bad, as it hampers overclocks quite a bit and a lot of hardcore overclockers tend to modify their motherboards to help prevent vdroop - such as soldering on a resistor or using the imfamous "pencil mod".
 
Last edited:
CPU Voltage Offset

Okay just had a read around, apparantly the CPU Voltage Offset is just another way to allow more voltage to the CPU. In this instance I would not bother using this setting and just concentrate on the CPU Vcore directly to increase voltage if / when you need too. The Offset setting seems a bit silly really if this is all it does, since they could have just made the actual vcore voltage increase higher instead of creating another new setting to do the same thing but in lesser amounts.
 
Back
Top Bottom