That caveat matters more than the buzzword "vibe-coded". Tom's Hardware, which reported the story, notes it remains to be seen whether the modified firmware can restore SkyOC on modern Intel platforms, because the workaround is yet to be fully tested. The post doesn't report a successful boot, a stable overclock, benchmarks, or even which board and CPU are involved. The source is an X post, not an ASRock or Intel statement.
What the post actually claims
According to the post, the author fed GPT Astra two ASRock BIOS versions: one from before SkyOC was removed and one from after. The AI reportedly located the code that enabled the trick, then edited the author's own board's BIOS to try to reproduce it. Tom's Hardware describes this as decompiling and comparing the two versions.
I can't verify what "GPT Astra" is, what files it analyzed, or what exactly was changed in the firmware. The post gives none of that detail. "Vibe-coded" describes the workflow, not the quality or safety of the output.
The post also makes technical claims about how the original trick worked:
- Independent CPU clock: it says high-end boards often have a separate BCLK for the CPU, so raising it doesn't also overclock RAM, PCIe and other buses.
- A hard limit: it says Intel built in a limit where the processor shuts down if it detects a BCLK above 103 MHz, with 100 MHz as the default.
- A false report: it says ASRock got around this by feeding the processor a false report of the real BCLK value.
These are the poster's claims. I found no official ASRock or Intel documentation confirming the "false report" mechanism or the 103 MHz figure. Treat both as unconfirmed.
A quick refresher on BCLK
A CPU's operating frequency comes from the base clock multiplied by the CPU multiplier. Unlocked K-series chips let you change the multiplier. Non-K chips don't, so the remaining lever is BCLK. Tom's Hardware gives the simple example that moving from 100 MHz to 105 MHz raises the frequency by 5%.
The catch is that on many platforms BCLK also feeds other parts of the system. As Tom's Hardware puts it, BCLK changes can affect memory and PCIe components and cause instability. That is why the separate clock generator mentioned in the post matters. Tom's Hardware reported in 2016 that ASRock's extra clock generator let the CPU cores run on a separate BCLK from the rest of the system.
SkyOC: how it started and ended
SkyOC came through beta UEFI firmware updates, which ASRock promoted under that name. Wikipedia's Skylake entry notes it was feasible partly because, on Skylake, the base clock applied only to the CPU, RAM and integrated graphics.
The feature came with trade-offs. Tom's Hardware reported that on ASRock's later boards, once BCLK went above 100 MHz the system instantly disabled the C-states power-saving feature and Turbo Boost. Those were observations about the Skylake-era implementation. They don't tell us what a modern port would disable, or whether it would work at all.
Then came the removal:
- In February 2016, an ASRock BIOS update listed two changes: a CPU microcode update to 0x76 and the removal of SKY OC.
- Wikipedia says Intel announced on February 9, 2016 that it would no longer allow such overclocking of non-K processors, and had issued a microcode update that removes the function.
- It also says that in April 2016 ASRock began selling motherboards that allow overclocking of unsupported CPUs using an external clock generator.
The post says Intel forced ASRock to remove the feature. Contemporary coverage is more cautious. Digital Trends noted there had been no word from ASRock or Intel, so the motives were speculation. Intel's role in the broader block is better supported, because a microcode change was involved. Whether Intel compelled ASRock is not established by the sources I reviewed.
One detail from forum discussion of the time is also worth knowing. Users reported that rolling back to an older BIOS didn't always restore BCLK overclocking once newer microcode had been loaded. That was anecdotal, but it shows the block wasn't purely a BIOS matter.
Why a modern port is a long shot
Finding the old code is not the same as making it run on a new board. SkyOC was written for one combination: Skylake CPUs, Z170 boards, a specific BIOS and a specific microcode. Tom's Hardware warns that finding the original code does not necessarily mean it can be ported to a modern motherboard BIOS. It adds that newer Intel processors use different firmware, microcode and clock-management mechanisms.
My reading, from general industry knowledge rather than anything in the post:
- Microcode is loaded by the CPU at boot and can enforce limits that a BIOS patch alone can't remove. That is exactly what happened in 2016.
- A patch that works on a decompiled image still needs real hardware validation. Boot, POST, memory training, PCIe stability and thermals all have to hold up.
- There is a discrepancy in the numbers. The post cites a 103 MHz shutdown threshold. I couldn't verify ASRock's own Skylake-era guidance, which reportedly mentioned problems above 102 MHz. The two figures may describe different conditions, and the available sources don't resolve it.
The practical takeaway: don't flash this
This is not a guide, and nothing here suggests readers should try the modified image. No BIOS download, compatible-board list, test method or recovery procedure has been published. Firmware flashing is model-specific, and a faulty image can leave a board unbootable. Tom's Hardware makes the same point, noting that flashing modified firmware carries its own risks, including rendering the board unusable.
If you're curious about non-K overclocking on a working PC, wait for independent testing from experienced firmware modders. Don't treat an X post as a validated tool.
What to watch for
The more interesting question is the gap between code discovery and validated behavior. AI-assisted decompilation and diffing can plausibly speed up the tedious part of reverse engineering. It doesn't replace hardware testing, and it can't tell you whether a limit lives in firmware or silicon. Until the poster reports a boot, a stable overclock, and results from a named board and CPU, this remains an intriguing experiment and nothing more.
References
- Overlocker uses vibecoded BIOS modification to target Intel's non-K overclocking restrictions Tom's Hardware · 2026-11-16T14:54:10+00:00
- Asrock Makes Non-K Skylake CPU Overclocking Official With 'SKY OC' Z170 BIOS Update | Tom's Hardware tomshardware.com
- ASRock BIOS update disables Non-K Skylake overclocking kitguru.net