Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseInsight · On RadarHabr AI→ original

AI Finds SkyOC Code in ASRock BIOS That Overclocked Non-K Intel CPUs

Hardware 360º enthusiasts gave an AI model two versions of an ASRock BIOS (the motherboard firmware), one with SkyOC and one without. The model found the code that overclocked Intel CPUs without a K suffix, whose multiplier is locked. SkyOC raised the BCLK frequency without touching memory or PCIe, until Intel forced ASRock to remove the feature. The team is now trying to bring the code back for new boards, but there are no hardware tests yet. The takeaway: AI speeds up firmware analysis, but only a real board can verify the result. Normally BCLK is 100 MHz, and Intel's protection shuts the system down above 103 MHz. Raising BCLK to 105 MHz yields a 5% overclock but breaks stability. Flashing a modified BIOS can completely kill the board.

AI-processed from Habr AI; edited by Hamidun News
AI Finds SkyOC Code in ASRock BIOS That Overclocked Non-K Intel CPUs
Source: Habr AI. Collage: Hamidun News.
Listen to article

Imagine you have an Intel processor without a K in its name. The manufacturer locked the multiplier, so you cannot overclock the chip the usual way. There used to be a workaround: ASRock motherboards supported a feature called SkyOC, which raised the processor frequency through the base clock, BCLK. Intel then pushed ASRock to remove the feature from the BIOS (the program that starts the motherboard). Now Hardware 360º has asked an AI model to find this code in old firmware, and it did. For anyone who works with firmware, security, and hardware, this is a clear example: AI turns weeks of manual reverse engineering into a comparison of two files.

What exactly was done

The experiment's authors took two BIOS versions from ASRock. One had the SkyOC feature enabled, the other had it disabled. Both firmware images were decompiled, meaning the machine code was converted into a more readable form. The files were then given to a model that the source calls ChatGPT Astra.

The task was simple: find the difference and work out which code handles overclocking. It resembles a routine diff of two program versions in a version control system. The difference is that there is no source code, only binaries that are hard for humans to read. The model isolated the differing blocks, identified the SkyOC code, and helped modify it to build a firmware image for a compatible motherboard.

Why SkyOC matters

Intel allows changing the multiplier only on K-series processors, such as the Core i9-14900K or newer models like the Core Ultra 270K Plus. Everything else has a locked multiplier. You can still raise the frequency of such a chip through BCLK. BCLK is normally 100 MHz, and the working processor frequency is BCLK multiplied by the multiplier. If BCLK goes up to 105 MHz, the processor overclocks by 5%.

But this method has a cost. BCLK affects not only the processor but also the RAM and devices on the PCIe bus, such as graphics cards and SSDs. As a result, the system often becomes unstable.

In 2016, ASRock introduced SkyOC for Intel Skylake processors. Some boards had independent clock generators. These let you change the processor frequency without touching other components. Intel objected. ASRock removed SkyOC through BIOS updates, and Intel changed the processor microcode to close off this path.

According to Hardware 360º, Intel's protection shuts the system down if BCLK exceeds 103 MHz. The original SkyOC got around this limit: the processor saw an incorrect BCLK value and did not trigger. That is the code the team was looking for in the firmware.

What remains unclear

Finding the code does not mean the overclock works. Full testing has not been done, and it is unknown whether the modified BIOS will run on modern Intel platforms. New processors use different microcode versions, different microcode, and different frequency control mechanisms, so porting a decade-old solution may prove very difficult.

There is also a practical risk. Flashing a modified BIOS can completely brick the board. Anyone who wants to repeat the experiment should first check whether the board has hardware recovery, such as a dual BIOS or an external programmer.

What follows from this

For the industry, there are two takeaways. First, AI lowers the barrier to reverse engineering firmware. Comparing two BIOS versions and finding the differing code can now be done not only by a narrow specialist but by an enthusiast with a good model. Vendors who assume a closed binary will hide features should take note.

Second, a neural network speeds up the search but does not replace hardware verification. Until there are tests on real processors and boards, it is too early to talk about a restored overclock. If the experiment holds up, it will be a rare case of AI giving users back a feature that vendors removed under pressure from the chipmaker.

Story

Key Questions Answered

What exactly was done?

The experiment's authors took two BIOS versions from ASRock. One had the SkyOC feature enabled, the other had it disabled. Both firmware images were decompiled, meaning the machine code was converted into a more readable form. The files were then given to a model that the source calls ChatGPT Astra. The task was simple: find the difference and work out which code handles overclocking. It resembles a routine diff of two program versions in a version control system.

Why SkyOC matters?

Intel allows changing the multiplier only on K-series processors, such as the Core i9-14900K or newer models like the Core Ultra 270K Plus. Everything else has a locked multiplier. You can still raise the frequency of such a chip through BCLK. BCLK is normally 100 MHz, and the working processor frequency is BCLK multiplied by the multiplier. If BCLK goes up to 105 MHz, the processor overclocks by 5%. But this method has a cost.

What remains unclear?

Finding the code does not mean the overclock works. Full testing has not been done, and it is unknown whether the modified BIOS will run on modern Intel platforms. New processors use different microcode versions, different microcode, and different frequency control mechanisms, so porting a decade-old solution may prove very difficult. There is also a practical risk. Flashing a modified BIOS can completely brick the board.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…