AI-Assisted BIOS Modification Revives Interest in Intel Non-K Overclocking
- Cargo
- Machine Learning
- Shipped
- Shipper
- [email protected] (Kunal Khullar)
- Readers
- 725
An enthusiast used AI to adapt ASRock’s old SkyOC workaround, but the modified BIOS has yet to show it can overclock modern non-K Intel CPUs.

An AI-assisted BIOS modification has brought an old overclocking workaround back into view, but the key question is still open: can code written for an earlier Intel platform work on modern hardware? Enthusiast Hardware 360º says it used ChatGPT Astra to compare ASRock BIOS versions and adapt code associated with SkyOC, a feature once used to overclock Intel processors with locked multipliers. The modified firmware has not yet been fully tested, so its practical value remains uncertain.
The work focuses on a boundary Intel draws between its unlocked K-series processors and non-K models. K-series chips, including the Core i9-14900K and the newer Core Ultra 270K Plus, allow multiplier-based overclocking. Non-K processors have locked multipliers, which limits that familiar route to higher CPU frequencies.
There is another control available on some systems: the base clock, commonly shortened to BCLK. It usually runs at 100 MHz, and the processor’s operating frequency depends on both that clock and its multiplier. Raising BCLK to 105 MHz would, in a simple example, increase clock speed by 5%. But BCLK changes can affect other parts of the system too, including memory and PCIe-connected devices. That wider effect can make a system unstable, even if the processor itself appears to tolerate the new setting.
What SkyOC changed
ASRock introduced SkyOC for Intel Skylake processors in 2016. The feature let users raise the BCLK on certain non-K CPUs, with some compatible motherboards offering independent clock generators. Those generators could allow the CPU clock to change without imposing the same adjustment on the rest of the system.
The feature did not remain available. Intel opposed the workaround, and ASRock later removed SkyOC through BIOS updates. Intel also introduced microcode changes intended to block non-K overclocking. ASRock’s removal of the feature is described in a contemporaneous report on SkyOC’s disappearance from its motherboards.
Hardware 360º says the current experiment began by decompiling and comparing two ASRock BIOS versions: one that included SkyOC and a later version with the feature disabled. The AI-assisted analysis reportedly identified code linked to the workaround, which was then modified for a BIOS intended for a compatible motherboard. That workflow may help narrow down where a feature lives in firmware, but locating code is only an early step in adapting it.
Why a modern port is uncertain
The account describes Intel’s safeguards as including a shutdown mechanism that activates when BCLK exceeds 103 MHz. It says SkyOC worked around the limit by making the processor receive a false report of the actual BCLK value. Those details are claims about how the mechanism operates; the modified BIOS has not yet demonstrated that the same approach works on current platforms.
Modern processors and motherboards differ from the Skylake-era systems for which SkyOC was designed. Firmware structures, microcode and clock-management mechanisms have changed, so code that could be identified in an older BIOS may not transfer cleanly. Even if the relevant logic has been found, it would need to interact correctly with the newer platform’s hardware and firmware.
There is also a practical cost to experimenting with motherboard firmware. A failed flash or incompatible modification can leave a board unusable. That risk matters especially here because the reported BIOS has not been fully tested. Anyone assessing the work should distinguish between a promising reverse-engineering result and a demonstrated overclocking method: the former is reported, while the latter remains to be established.
What the experiment shows
The clearest result so far is that AI assistance was used to compare firmware versions and help identify a past workaround. That could reduce some of the manual effort involved in tracing changes through a BIOS, though the available details do not establish how much of the analysis or modification the model completed on its own.
The next useful evidence would be a successful test on a named compatible motherboard and processor, with results showing whether the CPU clock changes while memory and PCIe devices remain stable. Until such testing is available, the work is best read as an attempt to reopen a path that earlier firmware and microcode changes closed. Its success will depend on whether the old SkyOC logic can be adapted safely to the much newer platform.