Need help with 6700k and Gigabyte G1 Z170-X Gaming 7 [F7] Bios [Auto vs Fixed Voltage ]

acedl

Reputable
Mar 22, 2015
87
0
4,640
Hello!

Build Specs:
Gigabyte G1 Z170-X Gaming 7 [F7] Bios
6700k
DDR4 3400 G.Skill
x61 Kraken

Anyone here have a Gigabyte G1 Z170-X Gaming 7 [F7] Bios and 6700k? I feel that my temps/voltage are out of line. Super familiar with my 2500k, but not the skylake / 6700k platform.

I was running my 6700k at stock/auto and it was over volting to a max on 1.32v from 1.296v in the bios.

With XMP set my DDR4 3400 G.Skill ram pushes my BLCK to 102mhz - not familiar with Skylake OC's yet. BLCK OC bad?

Temps hit max 70C in gaming/firestirke.. not bad. In overwatch, I never went over 60c at stock/auto on avg maxed out with a 980Ti FTW,

I did force the voltage down to 1.23v and turned off auto and it stayed around max 55-60c. With the voltage drop, should I gained about 8-10c.

I guess what I am most worried about is the BLCK and temps. I was able to keep it at 100mhz but had to underclock the memory. My memory is pushing the CPU past its normal turbo though clock to 4.2ghz on all cores but just the CPU0. So technically, its overclocking all cores, not just in single threaded cases.

Moving forward - is there cause for concern? Should I just clear CMOS and run stock/auto with puts me at 4.2ghz?

Maybe I need to re-do my thermal paste hmm. Now I can't get the voltage back to auto to test, I need to clear my cmos ugh.

Build is a few hours old.

Thanks for the advice/help in advance.
 
Solution
First of all, the I7-6700K is a great performer at stock.

If you want to overclock, try simple methods first. Leave voltage on auto and simply raise the max multiplier.
How high will be determined by the quality of your chip.
Skylake manages voltage better than haswell. 1.4v vcore is about as high as you want to go.
As of 5/2016
What percent can get an overclock at a somewhat sane 1.40v Vcore.

I7-6700K
4.9 2%
4.8 17%
4.7 59%
4.6 93%
4.5 100%
Do not fool with BCLK. leave it at default.

I recommend running ram at 1.2v stock. That will probably be 2400 speed. Higher speed needs higher ram voltage which I think has an impact on your multiplier overclock.
Ram speed has little real impact on performance.
Read this...

snurp85

Distinguished
May 6, 2009
641
0
19,160
For Skylake, it is generally recommended to keep the BCLK at 100 Mhz and to adjust the multiplier. To get the RAM to work, make sure you manually set the RAM voltage to 1.36 (for 1.35V ram) and then set the XMP profile/multiplier in the bios.

The overvolting from 1.296 to 1.32 isnt bad. But if you dont want it changing voltage, then yes, manually set it. If you get a stable system at the normal voltage then theres nothing to worry about.

The 70C temp isnt bad if thats the highest you see when the CPU is maxed.
 
First of all, the I7-6700K is a great performer at stock.

If you want to overclock, try simple methods first. Leave voltage on auto and simply raise the max multiplier.
How high will be determined by the quality of your chip.
Skylake manages voltage better than haswell. 1.4v vcore is about as high as you want to go.
As of 5/2016
What percent can get an overclock at a somewhat sane 1.40v Vcore.

I7-6700K
4.9 2%
4.8 17%
4.7 59%
4.6 93%
4.5 100%
Do not fool with BCLK. leave it at default.

I recommend running ram at 1.2v stock. That will probably be 2400 speed. Higher speed needs higher ram voltage which I think has an impact on your multiplier overclock.
Ram speed has little real impact on performance.
Read this:
http://www.silentpcreview.com/article1478-page1.html

implement speedstep which will lower the vcore and the multiplier when the cpu has little to do.
That might require adaptive voltage or whatever it is called on your bios.
 
Solution

snurp85

Distinguished
May 6, 2009
641
0
19,160
Well thats a bit odd.... I would just manually set the BCLK to 100 then. As for the RAM voltage on my Gaming 5 board, for whatever reason I can only set it to even numbers (1.36V). I get Prime95 errors if I set it to only 1.34. Though when the XMP profile is enable it claims to use 1.35 (despite me manually setting it to 1.36).