![]() |
Looking for Z170 OC Formula Guide & Tips |
Post Reply ![]() |
Author | |||||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() Posted: 17 Aug 2017 at 10:29am |
||||
For some OC, temperature, and VCore examples, check out the thread below. It begins with some SSD benchmarks, but later posts are of i7-6700K over clocks of 4.9 and 5.0GHz. BTW, the maximum normal VID for Skylake and Kaby Lake processors is 1.52V. You can also see the CPU throttling temperature in your board's UEFI, which could be adjusted higher if you dare (don't!):
http://forum.asrock.com/forum_posts.asp?TID=1491&title=two-950s-in-r0 Granted, voltages above 1.4V are not what we like to use for every day use, but up to 1.45V is not insane for these processors, with proper cooling. The VCore value being above the VID is caused by Intel's Adaptive voltage (not used with SB or Ivy Bridge), which I assume you are seeing when NOT using Fixed voltage (??) Otherwise the higher VCore could be caused by the stress test running AVX2 instructions, which are a killer for needing more VCore/power. The latest Intel HEDT processors have a special UEFI/BIOS option, AVX2 Offset, which lowers the core multipliers when AVX2 instructions are being executed. OMG, with your board's 16 phase VRM design, which are not even all enabled by default, with a high (1 or 2) LLC setting, any Vdroop using fixed voltage mode will be Missing In Action! ![]() For some reason, using the XMP profile on some boards can affect the VCore and CPU over clocks. I'm not saying not to use XMP, but if you are at a loss about why something is different, it might be using XMP. If you are coming from Sandy Bridge, like an i7-2600K, don't forget that they are the last Intel non-HEDT processors that have solder between the processor die and IHS. From Ivy Bridge forward, we have TIM between the die and IHS. The i7-2600K temperature spec is Tcase (72C), which is not the same as the current Tdie temperature spec of an i7-7700K: http://ark.intel.com/products/97129/Intel-Core-i7-7700K-Processor-8M-Cache-up-to-4_50-GHz If the max temperature you get stress testing is 85C with air cooling, you are doing fine. |
|||||
![]() |
|||||
ped ![]() Newbie ![]() Joined: 13 Aug 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
||||
Point taken with the temps, I appreciate your assurances. 72C seemed high based on what I saw on other forums running suicide runs like Prime95 which were lower and The Division really shouldn't stress the CPU 100%. I use this game because I know that it pulls the most watts from my system and is one of the more stressful games based on what I saw from HWiNFO.
You're right. I think I just picked 1.38V given that was the median from one of the OC forums on OCN, and I was trying to "split the book" method of narrowing down the voltage. So I considered 1.38V as the "middle page". Ultimately I was trying the shortcut method but seems to create more questions than I answered.
Good idea. I think you are right that a few values changed when you click it. Will record them next run. Here's a run I posted on the OCN which I'll copy here: Round 1: UEFI settings: Mult: 46 Uncore: 41 Vcore 1.34 fixed LLC 1 (highest) RAM: XMP 1 Running LinPACK Vcore at load:1.392V Vcore at idle: 1.312V Max temp: 85C VID: 1.20V Running x264 Vcore at load:1.360V Max temp: 64C VID: 1.20V Round 2: UEFI settings: Mult: 46 Uncore: 41 Vcore 1.34 fixed LLC 2 (second highest) RAM: XMP 1 Running LinPACK Vcore at load:1.312V Vcore at idle: 1.312V Max temp: 79C VID: 1.20V Running x264 Vcore at load:1.312V Max temp: 64C (same as before) VID: 1.20V So I'm a bit wary of the fact that the 1.312V didn't budge, but it seems that perhpas the LLC2 may be the magic bullet here and the LLC1 may be a 120% current push that others talk about on the other forums. I do greatly appreciate your help here parsec and your assurances that the temps and voltages seems solid. Just surprised this chip can take 1.312V when the temps are quite high, even if binned. Just not accustomed to see this delta. I would have expected to see a 1.35V or more when hitting 75C+. Will try your recommendation on the UEFI reset and see what that shows. Edited by ped - 17 Aug 2017 at 3:55am |
|||||
MoBo: ASRock Z170 OC Formula
CPU: 6700K Cooler: Noctua NH D15 |
|||||
![]() |
|||||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
||||
VID is what the processor is requesting for the VCore, from its built in table of VIDs. That does not mean it will actually get/use that voltage, or that it needs that voltage, as you have seen from the VCore reading in HWiNFO. The VID is a worst case situation voltage, not a magic voltage value.
You were unhappy with a CPU temperature of 72C at 4.6GHz. That is really not bad at all, frankly it is very good. The CPU throttling temperature is 100C, so that leaves quite a bit of headroom. Your CPU cooler should be fine, I use a NH-D14 with my Kaby Lake i7-7700K. If the CPU temperature is too high for you, get some more air flow into the PC case, increase the CPU fan speeds, or get some higher speed fans for the CPU cooler. Noctua goes for quiet operation, which is not optimal for the best cooling. The OC preset should set the CPU fan speeds to Full On. If you are reducing the fan speeds, expect higher CPU temperatures. A VCore of 1.4V is not unusual for an OC of an i7-6700K. Users at the 5GHz level run them close to or at 1.5V. Frankly, the Auto VCore for stock speeds of these processors is at least 1.4V. More than necessary for most processors. A fixed VCore voltage is just that, fixed. It might droop with the LLC set to 3 or lower, but with your board, won't with LLC above 3. That is normal. So your game crashed, but are you sure it was a CPU VCore issue? I'm not sure why you are searching for a VCore value of 1.38V. I assume you think it is a perfect value? If setting Fixed voltage to 1.38V does not give you that result for the VCore, then set it to 1.4V, or 1.42V. Going over your description, you said you applied the 4.6GHz OC preset. Later you set the VCore to Fixed, 1.38V, with an LLC of 3. Now you say those settings don't produce the same results? Try this, don't do the Load UEFI defaults. Perform a Clear CMOS/BIOS, either with the jumper on the board, or the Clear CMOS button on the IO panel. That will reset every UEFI/BIOS value to their true defaults. Then go into the UEFI and select the 4.6GHz OC preset. Now go through ALL of the OC Tweaker screens to see what the options are set to. The Voltage Configuration screen cannot be skipped! For example, the CPU SVID Support option may be disabled with that OC preset. Or the Turn on All Phase option is not enabled by default. Or the PWM Switching Frequency is set to a different value. Carefully check ALL the options in this screen, before and after applying the OC preset. I'm sure the OC preset changed at least some of them from their default values. Your board has options the no other ASRock board has for over clocking, and since I don't have your board, I can't tell you from personal experience. Also check the CPU Configuration screen in the Advanced section. Also, if you set the VCore mode to Auto, you should get a high VCore, might be more than you want but at least it will be higher again. |
|||||
![]() |
|||||
ped ![]() Newbie ![]() Joined: 13 Aug 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
||||
First thanks for responding so quickly! Will answer best I can.
Yes, I'll admit the irony. As long as we agree that something that is so sophisticated has an "easy mode" fat button that sets it to 4.4GHz, then we can agree that it's a bit silly there too, no? ![]() I bought it because I did a bit of OC on SB, which obviously evolved a lot. What made me purchase was what I read about the 18 multi-phase / 60A choke and ultimately the 33% less voltage noise to make OC easier. I figured I'd find some help on the forums as I did last time. This time I really wanted the sophistication so there was more room to play with, and perhaps some over-engineering to help too which is after my prior ASRock P4 GEN 3 Extreme felt I could have struggled less. I realized what I got into when I saw the Advanced UEFI options. Originally I meant to do this a year ago, but had a kid, and that made spare time pretty much negligible. So now here I am trying again but really have limited windows where I can play and learn.
Currently ver 2.4, know there is a 7.4, but wasn't looking at given I understood is primarliy for Kaby Lake chips. I've had bad experience with UEFI updates making OC'ing worse, so avoiding this unless I absolutely have to update.
Air: Noctua NH-D15 (as mentioned in my sig, but probably not visible on mobile)
I was using fixed voltage. Then set it to 1.38.
Ok I agree my explanation was sparse at best. I was hoping perhaps there was an obvious option I missed which caused my Fixed Voltage not to appear in HWiNFO. So let me explain everything I did. 1st - went for Lazy mode: I used the preset 4.6GHz to see if it would hold. Worked for Firestrike, but The Division made it crash - meaning everything froze and the machine rebooted itself like every other crash listed here. 2. Then I went into the CPU config, set the mutiplier to 46, left everything else to auto. Went into the voltage settings, changed it to fixed at 1.38V, and LLC to 3, given I wanted to ensure stability before testing further. The Division was good, however my temps were at 72C. HWiNFO showed my Vcore at 1.36 to 1.402. VID I wasn't paying attention at this point. 3. Going back to UEFI, it said my LLC was 1 although I set it to 3? So I set it back to Auto to see what would happen. Changed Uncore fixed to 4.2 I believe at this step. Vcore stayed in the range of 1.12-1.30 volts 4. Went back into UEFI, set LLC to 1. Still the Vcore seemed to stay a 1.2-1.30V. Had no effect to my fixed Vcore option (which was still fixed to 1.38 from step 2 prior) Ran x264 16 thread test as per the OC.net forums skylake group. VID was pegged at 1.20 for all cores, and my Vcore was no more than 1.22V Division also ran fine. Decided to test it with LinX for 5 runs at a 64K problem size. Ran through the first one no problem. Then crashed. 5. Then I decided to use the "reset UEFI to default" option in the exit tab. Went back to set my RAM to XMP 1 (which it was this way the whole time) Again set multiplier to 46, Uncore to 42. Rest default. Set voltage to Fixed at 1.38V Set LLC to 1 Again HWiNFO saying Vcore in the 1.1-1.23V range. VID stating it needed 1.37V? 6. Reset UEFI back to default again. Set RAM to XMP 1. Left it everytihng else as is. So at 4.2GHz, my Vcore ranges from 0.784 to 1.296V with my VID going as high as 1.370. So since that first run where I saw the Vcore going to 1.38V, haven't seen it again since. Perhaps using the preset mode changed some options I wasn't aware of that allowed the fixed voltage to set. However at a loss how to replicate it. Any advice on what I may have done or not done would be appreciated! ![]() Cheers, Edited by ped - 14 Aug 2017 at 4:03am |
|||||
MoBo: ASRock Z170 OC Formula
CPU: 6700K Cooler: Noctua NH D15 |
|||||
![]() |
|||||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
||||
Sorry, no guides for the OC Formula that I am aware of. It is ASRock's most sophisticated over clocking model, so aimed at those with experience in that area. What UEFI/BIOS version do you have installed? What are you using for the CPU cooler? My main question is, what VCore mode are you using? That would be in the OC Tweaker, Voltage Configuration screen. Did you use the same mode before and after the UEFI reset? So you found LLC set to level 1, but then set it to Auto. Did you see what LLC level you had with it set to Auto? You wrote, "I set it to Auto, then did it again", which seems to say you left it on Auto, correct? The LLC level was most likely not 1 with it set to Auto. BTW, LLC level 1 is the highest level (most correction), and level 5 is the lowest. You set VCore manually, apparently to 1.38V, is that right? I tend to doubt that. Afterwards, you had some crashes, and did a UEFI reset to defaults. You were then unable to get the 1.38V VCore back. Using the Auto settings, particularly for voltages, gives you the least amount of options to change manually. Is CPU Vcore Voltage set to Auto? The VCore range you listed, 1.36 to 1.4V, sounds like the Auto values you would get. Auto here would give you Intel's Adaptive voltage, normally producing the highest VCore values. With CPU Vcore Voltage set to Auto, do you get an option to set a specific VCore value? Usually you don't. Your description lacked details, such as after you reset the UEFI to defaults, did you reset your multipliers again? We have no way of knowing exactly what you did except from your description. The only options you listed were the two multipliers, and LLC. What "VCore" are you looking at in HWiNFO64? The VIDs at the top, or VCore value way below that? Don't forget you can save your UEFI option settings in a profile on the OC Tweaker screen. |
|||||
![]() |
|||||
ped ![]() Newbie ![]() Joined: 13 Aug 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
||||
Hi everyone,
I'm looking around several other forums and not really found a good guide on navigating all the features on the OC Formula. Anyone have any guides or experience they can share? I'm in a situation were I bought a binned 6700K @ 4.8GHz so I can ensure that I can run it at 4.6/4.7GHz 24/7, and while trying to change the multiplier / Uncore / Vcore, I'm getting odd results in HWiNFO. For example, I did a test where I changed the multiplier to 46, uncore to 42, Vcore to 1.38, LLC to 3 (instead of 5) and it seemed to work once where I saw the Vcore range from 1.36 to 1.4 with a temp at 72C. So clearly I was stable, but wanted to lower the temps, so I went back into the BIOS (ver 2.4), and found that the LLC seemed to be at 1 for some reason. I set it to Auto, then did it again. Then my Vcore was 1.22V. After a crash or two and a UEFI default restore, I cannot for the life of me get the 1.38 or 1.3x Vcore to come back. Are their other options I need to look at? Perhaps something set to auto? My last OC experience was SB, so been awhile. Thanks.
|
|||||
MoBo: ASRock Z170 OC Formula
CPU: 6700K Cooler: Noctua NH D15 |
|||||
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |