Help overclocking i7 3930k

[IH_72]

Hi all,

I'm wondering if someone can tell me the settings to change for a simple overclock of 4.2-4.3ghz please.
I'm using the Asus optimal mode atm,which makes my vcore about 1.303 avg at idle for just under 4.2ghz,the voltage seems to be lower at load,it drops to 1.288 then.

I've read using offset you can have it drop at idle,I've uploaded the Bios optimised default settings.
I tried to do a manual overclock with manual voltage at first and then was going to try offset mode.
So I set all cores to 43 and changed vcore voltage to 1.28v.
When the pc booted it got to desktop was ok for a minute then froze,so I panicked thought I'd done something wrong and went into the Bios and changed to optimal mode.

Can someone advise me what to change in my Bios and maybe use offset mode to get lower idle vcore ?
Should I have set speedstep to enabled instead of auto,if I've read up on things correctly speedstep and other power savings need to be on for a good overclock.

If

any other Bios screenshots are needed I'll gladly post them,many thanks in advance.

 

[IH_72]

Can anyone help ? Not sure if this was the right thing to do but to start with I thought I'd put voltages on auto and see what it was hoping someone could help in the meantime.

For some reason I couldn't choose auto vcore, only manual or offset.So I set all cores to 42 vcore to 1.28 and vtt and vccsa to 1.0 each (I also couldn't select auto).
I put speedstep to enabled and made sure the c states were turned on,memory I set to 1333mhz but couldn't set the speed settings as it was greyed out set to auto but it was correct apart from it said command rate 1 instead of 2.

I ran Aida64 extreme stability test with Fpu,Cpu and cache and the pc crashed after 50m mins with bluescreen Clock_watchdog_timeout,highest temp was 64c with no throttling. The average vcore at load was 1.234

What did I do wrong ?

I'm back on Asus optimal atm so at idle the vcore is 1.304 and it drops to 1.288 at load.

 

[Toothless]

Your crash was from lack of voltage. Just use the ASUS settings and leave it alone.

 

[IH_72]

But the average vcore at load was 1.234,surely if it needed more it would have gone up to the max I set of 1.28 ? Yes I can leave it like this but I was hoping for a lower voltage or to ahve offset to drop at idle.
Did I make the correct changes ? And have you got any idea why I couldn't select auto voltage ?

 

[BadFrog]

Can anyone help ? Not sure if this was the right thing to do but to start with I thought I'd put voltages on auto and see what it was hoping someone could help in the meantime.

For some reason I couldn't choose auto vcore, only manual or offset.So I set all cores to 42 vcore to 1.28 and vtt and vccsa to 1.0 each (I also couldn't select auto).
I put speedstep to enabled and made sure the c states were turned on,memory I set to 1333mhz but couldn't set the speed settings as it was greyed out set to auto but it was correct apart from it said command rate 1 instead of 2.

I ran Aida64 extreme stability test with Fpu,Cpu and cache and the pc crashed after 50m mins with bluescreen Clock_watchdog_timeout,highest temp was 64c with no throttling. The average vcore at load was 1.234

What did I do wrong ?

I'm back on Asus optimal atm so at idle the vcore is 1.304 and it drops to 1.288 at load.

I think you can go up to about 1.35 vcore for the 3930k. A drop in Vcore during full load isn't ideal and will cause a crash . Sounds like you need to increase LLC(Load line calibration) to counter the vdroop. Disable speedstep when you OC. Speedstep downclocks the CPU on idle. Also disable C states as well.

Check this article explaining alittle on LLC and vdroop. Hope it helps

http://www.masterslair.com/vdroop-and-load-line-calibration-is-vdroop-really-bad

 

[Thimblewad]

Try and find a setting called Load Line Calibration or maybe LLC and set it to the lowest setting that is not "disabled". So maybe "Normal", "Low" or "Auto", just don't use any "Extreme" settings. It will prevent a phenomenon called vdroop.

As explained by Anandtech for Intel (same goes for AMD)
TL;DR
[adz]
vDroop - the difference between the idle and load voltage.. Generally, you get a higher voltage when idling than when at full load. That's because it works as a self-protection mechanism to prevent too much voltage surging into the chip and frying it, or not giving it enough power.

For example, if your chip needs can take a voltage range of 1.35v - 1.55v, you might find that your idle voltage is around 1.50v. When you put it under full load, it'd drop to 1.47v. That's vDroop.
The board gives it extra voltage at idle so that when the chip goes into full load it can handle the negative voltage drop without going below the minimum 1.35v.
Likewise, the voltage upshoot from from full load to idle is protected by vOffset. That's the difference between your idle voltage and the maximum the chip can handle. You might find that when switching from full load to idle the voltage goes over the 1.50v and then comes back down to settle at 1.50v. That's to give it some room up top away from the 1.55v maximum.

Without vOffset:

 

[Vario]

As an addendum to @Thimblewad
In offset mode,
Actual Voltage = (VID +/- Offset) +LLC

Actual Voltage = the actual voltage that the processor is receiving. Voltage observed by your hardware monitoring.
VID = Voltage the processor is assigned by Intel to request for any given Clock Speed. VID varies based on chip quality. It is what the CPU asks the Motherboard for.
Offset = the value that you input to correct the VID to be either higher or lower.

Load Line Calibration = additional voltage that the motherboard applies to stabilize overclock by offsetting vdroop.
Vdroop = intentional voltage drop when the processor hits load, designed by Intel to prevent overvoltage of processor

It is controversial to use LLC to offset vdroop but most people do it.
The alternative to using LLC is running a lower clock or running a higher offset value or disable power saving options and running a constant voltage, which will use more power.

Using LLC will stabilize an overclock that experiences instability whenever the CPU hits load.

The parameter you need to change in the OP is the CPU VCore Offset Voltage, probably needs to be slightly higher such as +.010V, as a starting point. But for now, set it to +0V. In your screenshot it is set to auto. Change it to a manual value of 0V. Then boot into windows, load the processor with Intel Burn Test or Prime95 and see what your voltage is. If it is under 1.35V you are perfectly safe. See if it is stable, see what the actual voltage is, and if safely under 1.35V but not stable then try +.010V. Then try again and if not stable try +.015V. If it was stable at +0V, then try a negative offset like -.005V. Test again.

As far as LLC, you want to find the Load Line Calibration and turn it on, usually it is labeled something like Disabled,Normal, High, Extreme. So you would do Normal (which is sometimes disabled, if so then high) or High and see what your voltage is under load just like you did with Offset using Intel Burn Test or Prime 95.

 

[Thimblewad]

@Vario, great explanation!

 

[FreedomEclipse]

When i first got my 3930k and started overclocking. I used this guide quite heavily -- It explains ALL you need to know. Just keep the voltage under 1.40v unless you have really good cooling.

 

[jaggerwild]

Nobody has even asked for his hardware list, IF he has a GOOD Asus board he can do 45 with out touching any voltage. I cant see his photos my net is slow. @IH_72 what CPU cooler are you using?

 

[jaggerwild]

V drop is so C2D, again his board will auto volt up to 45. I would suggest checjing the viltage it gives, as Ive seen high auto over voltage and it will probably need lowering.

First we need to see your full systems spec's, dont want you over clocking on a stock cooler.

 

[Aquinus]

That looks like a P9X79 BIOS. My 3930k wouldn't likely push 4.2 stable at 1.3v but, the 3820 probably would but, that's 2 fewer cores. I would try 1.35v, up to 1.4v on the core (depending the CPU, aka. silicon lottery you might need up to 1.4v.)

 

[eidairaman1]

I seriously doubt he has been back, look at the post dates.