Intel 6700k Overclocking

[stwisper]

I'm trying to OC my CPU I managed to push it to 4.6gh with 1.365v tho when I stress test it it get to about 1.392v. Temps are spiking a lot from 60 to about 80 ( not using water using Be Quite Dark Rock 3 ) but once they hit 80 they got back to about 65-70 asap so I'm not sure if I should worry about it or not. So my main question is how to handle the voltage on normal state when I'm not doing anything. What happens is the CPU declocks to 800 mhz but the vcore is at 1.36v. , temps is at about 29-30. LLC is on auto C-state is on SVID is disabled. Tried working with either adaptive and off set volt but I didn't even manage to boot my PC.
CPU - 6700k
MB - Asus ranger VIII
Cooler- Be Quite Dark Rock 3
PSU - CM Thunder 600w

Before that I tried with 4.5 ghz with 1.325v gets to about 1.36v LLC on auto again temps were about 60-80 again when stresstesting
But still I would like to know how to decrease the voltage when the CPU goes idel.

 

[Faktion]

1.392v is a little high for my comfort on an every day rig as is. I found out a little while back that with these 6700k 1.35 is a pretty good soft limit in most cases (unless you have an amazing cooling solution.)

The CPU might be thermal throttling due to the heat. Or you have a program that is controlling your CPU cooler fan on a curve and that is a threshold.

I would steer clear of auto\adaptive\offset voltages and stick to manually setting your voltage. Even at stock speeds. If you manually set your voltage it should also still use far less in its low power state.

 

[stwisper]

On 1.35 4.6ghz will crash with blue scree watch dog error which to my understanding is due to lack of power. I also have my CPU fan running at 100% when the CPU hits 60% temp which is about 2000 rpm. On default BIOS it's even worse. Vcore gets to about 1.44, heat is about the same. Also on default it does use a lot less power on low state but that's because SVID is enabled which basically kills the purpose of manually setting the voltage

 

[Faktion]

Yeah a lot of motherboards supply far too much power when voltage is set to auto even at stock speeds 1.44@ stock is insane!

Disabling SVID just disables the CPUs integrated voltage regulator and hands the voltage settings over to the motherboard.

"SVID Support controls whether or not the CPU’s FIVR (Fully Integrated Voltage Regulator) should communicate with the external voltage regulator (Extreme Engine DIGI+ III) for the delivery of the CPU Input Voltage. Configuration this option to Enabled essentially establishes this communication while setting it to Disable forbids such communication, which yields better O.C. margin as compared with having it enabled. Considering this is outside the Intel CPU integrated Voltage Regulator, disabling SVID Support will “Not” affect the Intel integrated power saving functionalities such as EIST and the various C-States."

The motherboard voltage regulator should still have very similar low power states.

 

[stwisper]

I see and what exactly is causing the increased voltage when I'm stress testing and basically when the CPU is under load ? For example I set the vcore to 1.35 but it actually goes higher is it because of the LLC . For one thing messing with the LLC increases the heat and I'm noticing that the lower the lever I set it the less voltage increase I get while the CPU is under load which also makes it less stable

 

[Faktion]

Chapter 2: Different levels of LLC

Since each motherboards' power design is different this makes it difficult to create 1 setting which would flatten the drop to match it with the vCore set. As you can imagine, a perfect implementation to less powerful motherboards might still not be sufficient for more high-end gaming & dedicated overclocking models (which use different brand power phases and higher quality components). On the other hand, LLC on a high-end motherboard can lead to unwanted behaviour such as overvolting on less heavy models. Also, since each motherboard and CPU configuration might react differently to LLC it's hard to design 1 setting of LLC which is spot on, covering all configurations. This the reason why you'll see multiple settings in the BIOS when looking at LLC for some motherboards (0%, 25%, 50%, 75%, 100%). To show how easy it is to tackle Vdroop nowaydays we take the same setup, a MSI Z170A GAMING M7 motherboard coupled with an Intel i7-6700K CPU and set 'CPU Loadline Calibration Control' in the BIOS to 'Mode 1'. We set 1.3v vCore and overclock the CPU to 4.5GHz. Again we test with Prime95. "

TL: DR LLC only combats voltage drops when the CPU is going from a low load to a high load. The higher you set it the higher the extra voltage will be added when your CPU begins the transition to a high load.

V-droop isn't as much of a problem especially on higher end motherboards these days. It used to be a huge problem though and could cause locks\freezes\BSOD\restarts and the like.

LLC could be the reason you are seeing higher voltages under load than you had manually set. You could use a small offset for this or manually set the voltage slightly higher to combat V-droop like we used to.

 

[stwisper]

Right this helps a lot now. I did some testing again and it all comes down to working with LLC and Voltage. I don't know about other MB brands but in my case LLC has 7 levels with 15% increase per level. I started with 1.3v on 4.5 ghz from level 1 up to level 7 testing. What happened is that between level 1 and 4 the voltage was actually lower while testing from what I've set in the BIOS, so it was set to 1.3v but while stress testing it was around 1.28v to 1.29v depending on the level of LLC. From level 5 up to level 7 the voltage was higher from what I've inserted in the BIOS so on level 5 it was about 1.31v and on level 7 it was around 1.34v. Finally I end up with 1.3v set in bios LLC level 5 on 4.5 ghz. While testing voltage was at 1.31v , max temp I hit was 72, average temp 57-58 as I mentioned temp is spiking all the time. When the CPU get into low state basically 800mhz voltage is 1.296 I don't know what's normal voltage while CPU is idle but 1.296 looks rather good to me.
Right now I only did 40 mins of AIDA testing and there is a high chance of crashing with 24h testing but we will see.