Ready to over clock my 17-2700k - but how?

Abz Hussain · 22 Apr 2012 at 12:24

I have my CPU above ready for over clocking. I know with the Sandy Bridges that you have to use the multiplier and vcore to get the over clock you want or can get. However what i would like to know is that what other settings should i touch or not touch. Having read around the forums I'm suffering from information paralysis so i will ask here where i first started off my new pc.

Which settings, other than multiplier and vcore do i need to touch and by how much.

My aim is to achieve the highest over clock i can for 24/7 use whilst taking advantage of the power saving features. By that i mean that i want the CPU to idle @ 1.6Ghz when its not under load.

I have as above a i7-2700k, Gigabyte Z68XP-UD4 and Kingston hyperX 8GB 1600mhz.

Thank you guys

My build is water-cooled and i have my fans running at the noise level that i am happy to put up with - so i will be over clocking to that level where the temps are no higher than 70-75 degrees.

Rooster212 · 22 Apr 2012 at 12:38

Start upping the multiplier, possibly to 40x, you should be able to reach that without changing anything from auto, past that you might have to raise vcore, and when you get to higher multipliers you might have to change PLL or some other voltages.

Good luck and have fun!!

***OVERCLOCKING GUIDELINES***

- Do not exceed 1.425v core voltage, doing so could limit lifespan of the CPU
- Aim to keep temperatures below 70c underload if at all possible
- Do not overclock with BCLK, again doing so could limit lifespan of the CPU
- Recommended memory voltage is 1.50v, so make sure to run your memory at 1.50v, higher than 1.60v could limit lifespan of the CPU
- These recommendations come from OcUK and Intel, your warranty is un-affected but we highly recommend you adhere to the above to make sure your CPU lifespan is un-affected
- All Sandybridge CPU's worldwide should be run at the above or lower voltages, no higher!

Rooster212 · 22 Apr 2012 at 12:44

Also, if you leave Intel Speedstep on then it will go back to 1.6ghz when not under load.

Abz Hussain · 22 Apr 2012 at 13:33

Rooster212 said:
Also, if you leave Intel Speedstep on then it will go back to 1.6ghz when not under load.

Is speed step also known as turbo? I cant see speedstep in my bios.

Rooster212 · 23 Apr 2012 at 13:50

Turbo is the mode that comes on by default if the CPU uses it, on your board it may be that you modify the turbo multipliers so that the board defaults to 3.4ghz when not under strain, if there isn't a seperate setting for multiplier then I think you can use the turbo multis!

nickeverett · 23 Apr 2012 at 21:20

Here are some useful links to get you started:

- Sandy Stable Club

- Munaim1's Overclocking Guide for SandyBridge

- Raja@Asus's Z68 BIOS Guide - BASIC~Intermediate Overclocking

Abz Hussain · 24 Apr 2012 at 08:56

Cheers mate. I think i need to sort out my watercooling loop first. Im getting crappy temps at the moment.

Abz Hussain · 24 Apr 2012 at 09:01

Also, intel burn test or prime 95 or both. How should i use them?

nickeverett · 24 Apr 2012 at 10:19

Abz Hussain said:
Also, intel burn test or prime 95 or both. How should i use them?

Ibt on max will give very high temps, so good for testing cooler when OCing. 12-17 hrs of custom prime blend with 90% memory for stabity testing.

Abz Hussain · 28 Apr 2012 at 18:52

nickeverett said:
Ibt on max will give very high temps, so good for testing cooler when OCing. 12-17 hrs of custom prime blend with 90% memory for stabity testing.

Ok so im passing 15 loops of the very highest setting on IBT, however prime 95 keeps failing after about 2 mins. If im passing ibt with ease it seems and failing prime after 2 mins what could be the cause?

nickeverett · 29 Apr 2012 at 11:46

vCore too low.

As soon as one prime thread fails you know that the OC is unstable. So raise the vCore very slightly and try again.

If you get a BSOD, then record the error number and use this guide to work out whats wrong:

The OverClockers BSOD code list
BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

IBT is better for testing max temps for an OC. Prime is better for stability. If you can do 12 hours on a custom prime blend with 90% ram usage, you know you've got a stable oc.

What multiplyer and vcore are you on a the mo?

Abz Hussain · 29 Apr 2012 at 12:18

nickeverett said:
vCore too low.

As soon as one prime thread fails you know that the OC is unstable. So raise the vCore very slightly and try again.

If you get a BSOD, then record the error number and use this guide to work out whats wrong:

IBT is better for testing max temps for an OC. Prime is better for stability. If you can do 12 hours on a custom prime blend with 90% ram usage, you know you've got a stable oc.

What multiplyer and vcore are you on a the mo?

Thanks for the reply Nick. Out of sheer frustration i went back to stock settings last night and thought i would give it another go today. I think i was on 47 multi @ 1.38 in the bios. However i was getting different readings from CPUZ and then CORE temp also had a VID reading which was different o both the BIOS and CPUZ voltage - so all in all it was confusing this newbie overclocker.
Also confusing is what setting exactly does one touch. Some say just touch the multi and vcore. some touch other stuff like LLC PLL and other si i just called it quits. Going to start afresh today - how would you like to mentor me through my overclock lol?

nickeverett · 1 May 2012 at 09:07

Abz Hussain said:
Thanks for the reply Nick. Out of sheer frustration i went back to stock settings last night and thought i would give it another go today. I think i was on 47 multi @ 1.38 in the bios. However i was getting different readings from CPUZ and then CORE temp also had a VID reading which was different o both the BIOS and CPUZ voltage - so all in all it was confusing this newbie overclocker.
Also confusing is what setting exactly does one touch. Some say just touch the multi and vcore. some touch other stuff like LLC PLL and other si i just called it quits. Going to start afresh today - how would you like to mentor me through my overclock lol?

vCore and VID are different.
vCore is set in the bios, it is the voltage supplied to the cpu. vCore will read lower in bios than in cpu-z on load because system is idle in bios so less vcore needed.
VID is the voltage requested by the CPU. This can be helpful to work out offset voltages later.

If you just use multiplier and vCore you won't get very far. LLC controls vdroop from set vcore and actual delivered vcore. Usually set to Ultra High.

Don't use the PLL overvoltage until you have trouble booting into windows with an overclock.

In terms of tweaking PPL and VCCIO, I'm not clear on either of those myself, so I would suggest asking someone else if you want to use them.

For your Gigabyte mobo, I would use this guide: http://www.overclock.net/t/910467/the-ultimate-sandy-bridge-oc-guide-p67a-ud7-performance-review