Overclocking 8700K on low end Air Cooler like Cooler Master EVO 4.7-4.8ghz is possible on average silicon this is because max voltage you can use for non avx stress testing is around 1.225v before temps are late 80 degree C using stock TIM. Cache and mems cant really be pushed on this type of cooling as SA IO volts add to heat output. Cache really goes high on 8700K but in my testing only with voltages around 1.35v+ which is not possible on this type of cooler.
Overclocking 8700K on 240mm AIO like Asetek 240mm 4.8-4.9ghz is possible on average silicon this is because max voltage you can use for non avx stress testing is around 1.28v before temps are late 80 degree C using stock TIM. Cache and mems cant really be pushed on this type of cooling as SA IO volts add to heat output. Cache really goes high on 8700K but in my testing only with voltages around 1.35v+ which is not possible on this type of cooler.
Hm, it didn't seem that bad for me, but then again I'm using a board with Vdroop issues... It almost seems pointless even trying to overclock without delidding.
I wouldn't say 1.3 is the limit, its the average. You can go higher depending on temps. Delidding definitely drops temps significantly. VT-d is simply one less item for the board to initalize that 99% of people don't use... Guys like dino (professional overclockers) tend to disable everything they can to eliminate as many variables as possible.
I wouldn't say 1.3 is the limit, its the average. You can go higher depending on temps. Delidding definitely drops temps significantly. VT-d is simply one less item for the board to initalize that 99% of people don't use... Guys like dino (professional overclockers) tend to disable everything they can to eliminate as many variables as possible.
^ This. Leave it on if you are going to use it... Often OC'ers (and by OC I mean LN2 in a lab looking for records) disable audio and LAN as well, which is not a real world usage.
Updating HWinfo solved the issue, as it displays the sensor locations.
I would warn people against installing AppCenter though, it installs the EasyTune service (without prompting) and it overrides BIOS settings, which is rather annoying, I don't want to OC through a Windows app.
Updating HWinfo solved the issue, as it displays the sensor locations.
I would warn people against installing AppCenter though, it installs the EasyTune service (without prompting) and it overrides BIOS settings, which is rather annoying, I don't want to OC through a Windows app.
I got everything up and running, enabled XMP (Profile 1), set all of my memory timings and voltages, but the BIOS insists on leaving my 3600 speed RAM at the 2600 speed setting. Been fighting with it on and off for 2 days and nothing I do in the BIOS seems to make any difference. I wouldn't think it would be so hard to get some GSkill Trident Z 3600 CL16 RAM to run at that speed.
@HKPolice, I don't know about safe, but I have to ask why... most people (and not just with Gigabyte boards) are using 0.95-1.1v for VCCIO and 1-1.15v for SA.
@moustang, with AppCenter my RAM was running at 2133, even though I had XMP enabled in the BIOS, so if you have AppCenter installed, you might want to uninstall it and then check if it's working. For what it's worth, my dimms worked fine just by enabling the XMP profile, even at stock CPU settings, without any further fiddling with timing/voltages. (It's a kit of 2x8GB F4-3600C16D-16GTZR G.Skill TridentZ)
@HKPolice, I don't know about safe, but I have to ask why... most people (and not just with Gigabyte boards) are using 0.95-1.1v for VCCIO and 1-1.15v for SA.
@moustang, with AppCenter my RAM was running at 2133, even though I had XMP enabled in the BIOS, so if you have AppCenter installed, you might want to uninstall it and then check if it's working. For what it's worth, my dimms worked fine just by enabling the XMP profile, even at stock CPU settings, without any further fiddling with timing/voltages. (It's a kit of 2x8GB F4-3600C16D-16GTZR G.Skill TridentZ)
That's exactly the RAM I have. I couldn't figure out if it was stuck on the 2600 speed because of something I missed or because after enabling XMP I immediately tried the CL14 timings from the 3200 RAM to see if they would work. It booted and ran just fine, but I can't get the RAM speed above 2600.
That's exactly the RAM I have. I couldn't figure out if it was stuck on the 2600 speed because of something I missed or because after enabling XMP I immediately tried the CL14 timings from the 3200 RAM to see if they would work. It booted and ran just fine, but I can't get the RAM speed above 2600.
You should start at the beginning... ie load optimized defaults, enable XMP and check how that works, without any other changes. Then start tweaking what you want... It's time consuming but it's pretty hard to troubleshoot if lots of different settings are changed at once, have to do it one step at a time.
If you don't want to do that, a quick (and dirty) tweak is increasing VCCIO and VCCSA voltage to 1.1V and see how that works - I've not done proper reading yet, but I gather those are the two voltage settings (besides the obvious DRAM voltage) that affect memory overclock and every chip is different so maybe yours needs a little bump - I think stock those are at 0.95V and 1.00V respectively.
I was thinking of doing exactly that. I really haven't changed that much, but I started with the CPU and then went to the RAM. Perhaps doing it in reverse and starting with the RAM will yield better results.
Hmm, I see a lot of people with this board using AVX offset, but does it actually work? I have this board and it triggers the AVX offset even when running non-AVX code. Even right after windows startup I'll see it kick in.
Also.. when I use DVID offset, I have to manually change the IA cores AC/DC load line because at default my VID is all over the place when I OC (1.45V and above)
Hmm, I see a lot of people with this board using AVX offset, but does it actually work? I have this board and it triggers the AVX offset even when running non-AVX code. Even right after windows startup I'll see it kick in.
I know the issue you're describing. We've tested it on Z270 as well and it seems to be a bug on Intel's microcode. We've been waiting on a patch atm.
Although, there's a workaround to get this right. Disable all the C-state options (C1E, C3, C6/C7, C8, C10) and it will be stable.
I'm not use to Gigabyte motherboard BIOS.. Does the Z370 Gaming 7 have an offset voltage mode? I can't find the option for it.My 8700k at 5ghz is stable with 1.33v fixed voltage.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Ask a question
Ask a question
Overclock.net
27.8M posts
541.2K members
Since 2004
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!