GIGABYTE and Biostar Now Also Non-K Skylake Overclockable on Z170 Motherboards

The non-K overclocking for Skylake processors saga has been going on for almost a month now. In the beginning of December, Dhenzjhen started the non-K OC movement by showing a retail 4.6GHz Core i3 6320 on a Supermicro H170 motherboard. A couple of days later JagatOC confirmed the overclocking results and first hinted at the power management and AVX issues. Two weeks after Dhenzjhen's results, ASUS and ASRock showed off their non-K overclocking capabilities too with Elmor hitting a solid 5.8 GHz with a Core i3 processor.

Today GIGABYTE and Biostar join the list of motherboard vendors that have non-K OC enabled BIOSes available. The former, GIGABYTE, unofficially supports it through beta BIOSes. The latter, Biostar, released it as an official overclocking feature called HyperOC. Thanks to Stasio, a dedicated forum member who shared the beta BIOSes in our Z170 BIOS thread, you can test the GIGABYTE non-K OC on 7 Z170 motherboards. The list includes: Z170X-SOC Force (F6c), Z170X-Gaming G1 (F7a), Z170X-Gaming GT (F6a), Z170X-Gaming 7 (F6), Z170X-Gaming 7 (F7a), Z170X-Gaming 3 (F5g) and Z170-HD3P (F5g).

It remains to be seen how Intel responds to the non-K overclocking BIOSes. It's significant that three motherboard vendors (ASUS, GIGABYTE and MSI) only support it on beta BIOSes and have made no official statements on this topic. ASRock and Biostar are a bit bolder in their approach going full out and turned the capabilities into features called respectively Sky OC and Hyper OC. We have not seen the end of this story, that is certain.


10

South Africa Vivi says:

Maybe intel leaked it?

Belgium Massman says:

I don't think so ...

Ukraine johnwaynr says:

1.Could intel make a microcode update and via windows 10 update and close non-k OC? 2. And once you might have it, if you will roll back to win 8.1, that update will be gone? 3. Or once you caught it you are done, it will affect bios etc? 4. Or it just in hdd/ssd and wipe whole thing down and you good for OC?

Sweden saftig says:

johnwaynr said: 1.Could intel make a microcode update and via windows 10 update and close non-k OC?
2. And once you might have it, if you will roll back to win 8.1, that update will be gone?
3. Or once you caught it you are done, it will affect bios etc?
4. Or it just in hdd/ssd and wipe whole thing down and you good for OC?


No I don't think Intel can do anything about this as the BIOS files have already been released. Any amount of software tinkering in Windows is not going to affect BIOS. If Intel really sees this as a problem they will probably take legal action or threaten the motherboard manufacturers with repercussions if they don't remove the overclocking features.

Ukraine johnwaynr says:

saftig said: No I don't think Intel can do anything about this as the BIOS files have already been released. Any amount of software tinkering in Windows is not going to affect BIOS. If Intel really sees this as a problem they will probably take legal action or threaten the motherboard manufacturers with repercussions if they don't remove the overclocking features.

I mean, when last time intel was a d**k and close OC haswell+ non-z boards, do people could just turn off windows update and still use OC?

United Kingdom TheMadDutchDude says:

I don't think it'll be able to update via Windows unless a BIOS update was forced somehow, maybe...?

Either way, there's not much Intel can do about it without requesting that the files are removed from the vendors website(s).

If you weren't already aware, Roman (der8auer) has uploaded a fair chunk of them to his personal (I think) site, and I have downloaded every BIOS I can find as well, as I will be uploading them to the review site that I work for.

[MENTION=47]Massman[/MENTION], I'll message you later on to see if we can do something with it for all HWBOT users. I'm not sure how extensive Roman's uploads list is, but I am sure he isn't slacking behind. Perhaps we can put the two together and make them available to the masses who aren't aware of our forums. :)

Ukraine johnwaynr says:

TheMadDutchDude said: I don't think it'll be able to update via Windows unless a BIOS update was forced somehow, maybe...?

Either way, there's not much Intel can do about it without requesting that the files are removed from the vendors website(s).

If you weren't already aware, Roman (der8auer) has uploaded a fair chunk of them to his personal (I think) site, and I have downloaded every BIOS I can find as well, as I will be uploading them to the review site that I work for.

[MENTION=47]Massman[/MENTION], I'll message you later on to see if we can do something with it for all HWBOT users. I'm not sure how extensive Roman's uploads list is, but I am sure he isn't slacking behind. Perhaps we can put the two together and make them available to the masses who aren't aware of our forums. :)

Well, story with win10 and OC pentium g3258 proves they can close OC via new win10 builds and future win10 build 11899 (for example) can contain pre installed intel microcode update, but for now if you have all the files, and you won't change your bios, and you turn win update off = does your OC safe?

United States Schmuckley says:

..but it won't get you a better xtu score..

Belgium Massman says:

TheMadDutchDude said: [MENTION=47]Massman[/MENTION], I'll message you later on to see if we can do something with it for all HWBOT users. I'm not sure how extensive Roman's uploads list is, but I am sure he isn't slacking behind. Perhaps we can put the two together and make them available to the masses who aren't aware of our forums. :)


I can upload them to the Cloud with the other Z170 BIOSes. Actually that was the plan, but haven't been able to get to do it with everything else that's been going on.

Let me know how I can be most useful :celebration:

Germany der8auer says:

Trying my best to keep it up to date :D http://overclocking.guide/intel-skylake-non-k-overclocking-bios-list/

Please log in or register to comment.

Leave a Reply: (BBCODE allowed: [B], [QUOTE], [I], [URL], [IMG],...)