Z170's Motherboard non-K OC Beta Bios |
Post Reply | Page 12> |
Author | |
peroni
Newbie Joined: 27 Dec 2015 Status: Offline Points: 65 |
Post Options
Thanks(0)
Posted: 11 Feb 2016 at 7:18pm |
We might be putting too much hope on AMD, let's hope it does deliver
|
|
Z170 PRO4
i5 6600 2x8GB Corsair DDR3000 SSD 950 Pro (OS) 850 Evo (data) GTX 960 4GB 2x LCD |
|
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 25073 |
Post Options
Thanks(0)
|
Zen
|
|
|
|
peroni
Newbie Joined: 27 Dec 2015 Status: Offline Points: 65 |
Post Options
Thanks(0)
|
Non-k cpu's have an interesting history of mild overclocking
I remember these steps: 1. Turbo mode hack on sandy bridge to allow 4 extra bin (i.e a max turbo value of 3.6GHz with one core active would become 4.0GHz, 2 cores active at 3.9GHz insted of 3.5GHz etc.) 2. The above was disabled on Haswell but a new functionality called Multicore enhancement could lock all the 4 cores at max turbo value 3. SkyOc on skylake which allowed unlimited BCLK overclocking but disabled speedstep, turbo, c1 states and core temp reporting What will be next? |
|
Z170 PRO4
i5 6600 2x8GB Corsair DDR3000 SSD 950 Pro (OS) 850 Evo (data) GTX 960 4GB 2x LCD |
|
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 25073 |
Post Options
Thanks(0)
|
The sad fact is that Sky OC was a gamble as to whether intel would allow it. It was a gamble that lost. No matter what intel's official response may be (nothing as yet), it is quite clear they were behind the abolition of the feature. Users have to understand that Sky OC was essentially a hardware and firmware level hack to implement a feature not officially supported by intel. In any scenario where the term "hack" can be applied it must always be assumed that the functionality will not be perfect.
Sky OC allows for a quick and dirty OC on Z170 boards when paired with a non-K CPU, much like the implementation of non-Z overclocking on previous generation Haswell boards. With B/H series Haswell boards the user had to be willing to accept the fact that the OCing utility was very limited in so far as the number of tweaks that were available, no LLC, no RAM overclocking, no BCLK settings as well as fixed voltage even if you selected "adaptive". This is now and will always be the case when a manufacturer provides and unsupported feature. Does that mean the feature is bad or should not have been included? Obviously not, there are always those to whom the weaknesses of said features will be offset by the benefits. ASRock consistently pushes the boundaries with it's products, especially where it comes to adding extra value for it's users. Not all of these features will take off and not all will remain in play but the fact that they keep trying and are willing to risk the ire of chipset and CPU providers is truly a testament to their commitment to us as end users. It is sad that Sky OC is being phased out but for those who already have capable boards with the few BIOS versions that support it, you still get to use it
|
|
|
|
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
First, Sky OC is officially dead, if you haven't noticed all the UEFI updates flooding in for Z170 boards.
For example, the description for UEFI 2.60 for my Z170 board: 1.Update microcode to 0x76. 2.Remove Sky OC function. This is a news item at PC enthusiast websites, so you can find stories about it all over the Internet. If you like Sky OC, don't drink the poison UEFI update. The poison is actually microcode 0x76. The rest is any UEFI options related to Sky OC. The latter are worthless anyway, once you have the former. Given this development, there of course will NOT be any fixes for bugs related to Sky OC. But doesn't anyone remember the limitations that were part of Sky OC? There used to be a list of them posted on ASRock's website, which is probably gone now for obvious reasons. Regarding the VID and offset voltage UEFI setting, that behavior may be normal for a non-K processor. That is, the ability to override the VID with an offset. For a non-K processor at stock clock, what is the use of that? Sky OC worked, but it was far from perfect. All the limitations that did NOT exist in the golden days of over clocking (before Sandy Bridge) that have been added since then were not washed away by Sky OC. Sky OC tried to use a difference in Skylake processors that exists for the first time since Sandy Bridge. That is, the CPU BCLK is not shared with the PCIe lanes, DMI3 lanes, etc. So the CPU BCLK can be changed without affecting (and crashing) the other things that depend on a stable clock value. To bad it is not that simple. Other changes along the way since Sandy Bridge, and some new to Skylake, have weird side affects when the CPU BCLK is changed. Like the integrated graphics no longer working, C States no longer functional, and... was it no CPU temperature or no VCore reading, I think the former. For me personally, some of those shortcomings made Sky OC much less attractive. Another thing, VID and VCore are not the same thing. With Adaptive voltage, the actual VCore can be lower and higher than the VID. Actually, I want someone to tell me what voltage option(s) are available besides Manual, with Skylake processors. For example, what is the Auto setting equivalent to? Is Adaptive still an option with Skylake? We think we know these things, but do we? |
|
ProperT
Newbie Joined: 11 Feb 2016 Status: Offline Points: 1 |
Post Options
Thanks(0)
|
I just spent a few hours figuring out that I could only increase voltage offset effectively if I leave BCLK at 100. wish I would have saved my time and read your posts. I'll add to the inquiries to ASrock of this and hopefully that can fix it for us, but with all the intel trying to close the door on the non-k oc, maybe Its safer to just get a different board that allows Vcore adjustments. any suggestions?
|
|
sprudel
Newbie Joined: 30 Jan 2016 Status: Offline Points: 2 |
Post Options
Thanks(0)
|
I still hope ASRock will fix that with the next Bios even if this is a low budget board
|
|
Mcflurry
Newbie Joined: 31 Jan 2016 Status: Offline Points: 1 |
Post Options
Thanks(0)
|
I am having exactly the same problem with my Z170M Pro4S, on both L2.23 and L2.40, firstly there is no voltage control, only voltage offset options, secondly, if I change my BCLK to anything, the voltage will always be stick at auto (1.088v). Should I refund this board and go for a Gigabyte or Asus which have similar price?
|
|
sprudel
Newbie Joined: 30 Jan 2016 Status: Offline Points: 2 |
Post Options
Thanks(0)
|
at least on the Z170M Pro4S, SKYOC does not work really good with the beta bios, nor the 2.40.
you can set a vid offset to a non k cpu which will only work if you leave bclk @ auto. when you increase bclk you are able to set any voltage you want but it will not affect the vid, so you are very limited to the oc by the default vid..Yes, you can leave offset @auto -> 1.05v, or +400 -> 1.05v. i already mailed to the support weeks ago but no answer. |
|
oemspain
Newbie Joined: 29 Jan 2016 Location: SPAIN Status: Offline Points: 5 |
Post Options
Thanks(0)
|
Thanks, Xaltar. Nice notice ;-)
|
|
Post Reply | Page 12> |
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 |