First time overclocker, paid help needed :D (ASUS)

maxamillion

Limp Gawd
Joined
Oct 27, 2005
Messages
162
So I recently switched back from mac to pc and was wondering if anyone could help me overclock to a stable 3.2 from a 2.66.

$25 paypal goes to the first person that pm's me with assistance (please include your aim contact). And yes I know I could just research and overclock myself but my time is usually quite precious endeavoring into other ventures.

I just want to hit a stable 3.2 ghz with the following setup:

ASUS P6X58D Premium
Intel Core i7-920 Bloomfield 2.66GHz
Corsair Dominator 6GB TR3X6G1600C8D
Seasonic X650
Thermalright Venomous X

Graphic card is a EVGA GTX 260 if it matters but will switch to a ATI 5850 soon.
 
just raise the BLK clock.. cant remember what the exact number is for 3.2ghz.. but you shouldn't need to increase the cpu voltage at all to do it either.. it should do 3.8ghz @ 1.35v i think.. do some searching through this section of the forum.. you will find a ton of numbers for overclocking..
 
Download Real Temp, CPU-Z, and LinX (stability testing).

In your BIOS, go into the AI Tweaker menu, set it to Manual, and at the bottom, disable Load Line Calibration (make sure it is explicitly set to disabled) as it can damage 45nm chips, and disable CPU and PCIe spread spectrum.

Go into CPU Configuration and disable C1E Support.

In AI Tweaker, set the CPU ratio to 21. The 21x multiplier is far easier to work with than the default 20x multiplier. Raise the BCLK to 153 MHz. This will give you a 3.21 GHz OC. Set your DRAM speed to the highest option that is under 2000 MHz. Set your VCore to 1.35V (this is just for testing; you'll decrease it later). Set your DRAM bus voltage to 1.66V. You'll see a warning that it's outside of Intel specification - ignore that. (The guideline is actually .5V from the DRAM controller voltage which is minimum, and by default, 1.2V, so theoretically you could go as high as 1.7V but I prefer 1.66 just to stay safe.) Save and try to reboot. If there's no POST turn it off and back on again (which resets it to default settings temporarily) and go back into the BIOS and set the DRAM speed one notch lower. (Some i7s can boot at ~2000MHz; some can't. You've got good RAM so the RAM itself shouldn't be the problem.)

From there, if you can boot into Windows, set the VCore down to ~1.28V and run LinX for 5 passes at a 25,000 problem size. If that passes, take VCore down a notch or two, and run again. Once you've reached a VCore where it does not pass, or takes a very long time to pass (my 3.4 GHz 920 with DDR3 1600 runs a single pass in around ~230-240 seconds), raise VCore again and run for 20 passes. Keep raising from there if it's unstable.

Once it passes 20 passes you're pretty good off but I tend to run another 100 or so passes overnight just to be 100% sure. It's probably unnecessary - I've never had an OC that passes 20 passes NOT pass 100 passes. It's more of a paranoia thing.
 
Download Real Temp, CPU-Z, and LinX (stability testing).

In your BIOS, go into the AI Tweaker menu, set it to Manual, and at the bottom, disable Load Line Calibration (make sure it is explicitly set to disabled) as it can damage 45nm chips, and disable CPU and PCIe spread spectrum.

Go into CPU Configuration and disable C1E Support.

In AI Tweaker, set the CPU ratio to 21. The 21x multiplier is far easier to work with than the default 20x multiplier. Raise the BCLK to 153 MHz. This will give you a 3.21 GHz OC. Set your DRAM speed to the highest option that is under 2000 MHz. Set your VCore to 1.35V (this is just for testing; you'll decrease it later). Set your DRAM bus voltage to 1.66V. You'll see a warning that it's outside of Intel specification - ignore that. (The guideline is actually .5V from the DRAM controller voltage which is minimum, and by default, 1.2V, so theoretically you could go as high as 1.7V but I prefer 1.66 just to stay safe.) Save and try to reboot. If there's no POST turn it off and back on again (which resets it to default settings temporarily) and go back into the BIOS and set the DRAM speed one notch lower. (Some i7s can boot at ~2000MHz; some can't. You've got good RAM so the RAM itself shouldn't be the problem.)

From there, if you can boot into Windows, set the VCore down to ~1.28V and run LinX for 5 passes at a 25,000 problem size. If that passes, take VCore down a notch or two, and run again. Once you've reached a VCore where it does not pass, or takes a very long time to pass (my 3.4 GHz 920 with DDR3 1600 runs a single pass in around ~230-240 seconds), raise VCore again and run for 20 passes. Keep raising from there if it's unstable.

Once it passes 20 passes you're pretty good off but I tend to run another 100 or so passes overnight just to be 100% sure. It's probably unnecessary - I've never had an OC that passes 20 passes NOT pass 100 passes. It's more of a paranoia thing.

I just did 20 passes in linX with 1.32 vcore at 3.2 ghz. The average pass around is about 259 seconds. Should I keep these settings or is that vcore suitable?
 
I just did 20 passes in linX with 1.32 vcore at 3.2 ghz. The average pass around is about 259 seconds. Should I keep these settings or is that vcore suitable?

That Vcore is unnecessarily high--I run mine at 1.25V at 3.9Ghz stable.
 
I noticed all overclocks on forums have Load-Line Calibration enabled. Does what eddieck said about it damaging 45nm chips have truth behind it?
 
I decided to get hit 3 ghz only without having to max out my fans and making it sound like a jet engine.

Settings so far:
21 x 145
DDR: 1744 MHZ
CPU vcore: 1.20
QRI/DRam: 1.60000

I will keep on lowering the vcore until it blue screens again and then stabilize near the previous setting.

Here is a screen:
eyFt8.png
 
Back
Top