Home / Component / CPU / ASRock BIOS update disables Non-K Skylake overclocking

ASRock BIOS update disables Non-K Skylake overclocking

Earlier this week, rumours began circulating suggesting that Intel is due to release a BIOS update in order to block BCLK overclocking on locked (non-K) Skylake processors. Now, it seems like that is what is happening as ASRock is the first motherboard maker to come out with a new BIOS update, which does disable the function.

This BIOS update was released for a range of ASRock motherboards. In the description, we can see that two key changes were made, the first being an update to CPU microcode to 0x76 and the second update is the removal of SKY OC, a feature used to overclock non-K series Skylake processors.

BIOS updates

We will likely see other motherboard makers follow suit with updates to disable BCLK overclocking on locked Skylake chips. Most of ASRock's boards have the update available now but there might still be a few left over, as we can see, the Fatal1ty FM2A88x+ Killer board only got the update today.

KitGuru Says: When we originally reported that Intel might be blocking BCLK overclocking on non-K Skylake processors, a lot of our readers seemed disappointed in the decision. Did any of you actually try out this overclocking method? Did it cause any issues at all? 

 

Become a Patron!

Check Also

Leo Says 77 – Intel ‘fesses up about Arrow Lake Core Ultra 200S

The launch of the new Intel Core Ultra 200S family of CPUs along with Z890 motherboards was a thorny process. KitGuru suffered along with pretty much every other review site on the planet and you may have noticed we held off from reviewing of the Core Ultra 9 285K, Core Ultra 7 265K and Core Ultra 5 245K as it is clear to us that Intel has some work to do before this platform is ready for action.

9 comments

  1. I’ve got a Gigabyte mobo and I believe they never even bothered to release a non K OC BIOS update so I never got to try. However BIOS updates are optional so can ppl who want to keep using the non k overclocking just not bother to update? or is there some background update that does it anyway regardless..

  2. Overclocking BCLK by any sort of large amount was a very bad idea in the first place as most of the CPU besides the core was never meant to run over the normal clock speed. This could easily lead to corrupt data in the cache and getting fed back to your SSD or hard drive. It could even fry parts of the CPU as only the cores are monitored for excessive heat and are automatically throttled. Intel was wise to stop this unintentional exploit by the mobo makers.

  3. Frankly, not worth the risk.

  4. ❝my .friend’s mate Is getting 98$. HOURLY. on the internet❞….A few days ago new McLaren. F1 bought after earning 18,512$,,,this was my previous month’s paycheck ,and-a little over, 17k$ Last month ..3-5 h/r of work a day ..with extra open doors & weekly. paychecks.. it’s realy the easiest work I have ever Do.. I Joined This 7 months ago and now making over 87$, p/h.Learn. More right Here;;76➤➤➤➤➤ http://GlobalSuperEmploymentVacanciesReportsJobs/GetPaid/98$hourly…. .❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2:❦2::::;;76..

  5. If you try run any Skylake (k chips included) chip with the Fatal1ty FM2A88x+ overclocking is going to be a non-issue 😛

  6. seekingabc.blogspot.com

  7. The last platform I recall BCLK overclocking being remotely viable on was AM3+ and its predecessors. You could up the value by a significant margin without any ill-effects so long as you lowered other values proportionally (such as DRAM timings and clock settings and Northbridge and so on.) The FM1 socket could squeeze out a few extra mhz but going beyond 115mhz or so (from the stock 100) could cause loss of functionality.

    I know on the FM2(+) platform you lose AHCI functionality when you hit 105, and beyond 110 you get wonky PCIe bus issues and a few other dilemmas spring up if you go beyond that. Just not a good idea overall these days.

  8. fuck intel

  9. I don’t updated my bios. Because I’m using SkyOC function for 4.2Ghz O.C. on i5 6500 CPU