Claude AI rewrites BIOS—because Intel’s CPU support won’t

Claude AI rewrites BIOS—because Intel’s CPU support won’t📷 Source: Web
- ★Claude AI automates BIOS modding for unsupported CPUs
- ★12 P-core Bartlett Lake boots on Z790—without Intel’s blessing
- ★DIY hack exposes chipmaker’s artificial segmentation strategy
A single modder just did what Intel’s engineering teams won’t: make a Bartlett Lake-S CPU—12 P-cores, zero official support—boot on an Asus Z790 motherboard. The tool? Claude AI, repurposed to rewrite BIOS microcode where Intel’s own updates refuse to tread. This isn’t some synthetic benchmark victory; it’s a real-world end-run around Intel’s deliberate CPU-motherboard segmentation, where newer chips get locked out of older boards to force upgrades.
The hack itself is surgically precise. The modder, posting under the handle @platomav on GitHub, fed Claude the BIOS binary and a set of Bartlett Lake’s unreleased microcode—then let the AI handle the hex-editing. No soldering, no voltage tweaks, just a scripted rewrite that tricked the Z790 into recognizing a CPU it was never meant to support. The result? A stable Windows boot, complete with all 12 P-cores active, on a board Intel’s drivers explicitly reject.
This isn’t about raw performance—it’s about exposure. The mod proves Bartlett Lake’s compatibility was always a software decision, not a hardware limitation. And when your $400 CPU gets bricked by a BIOS update because Intel says so, that’s less ‘innovation’ and more ‘planned obsolescence with extra steps.’

The real story isn’t the boot—it’s the BIOS as a battleground📷 Source: Web
The real story isn’t the boot—it’s the BIOS as a battleground
The HWiNFO logs from the boot reveal the ugly truth: Bartlett Lake’s microcode was already compatible with Z790’s power delivery. Intel’s block was purely artificial, enforced through BIOS whitelists and microcode version checks. Claude didn’t ‘invent’ compatibility—it just removed the arbitrary roadblocks. For modders, this is a template; for Intel, it’s a PR nightmare waiting to scale.
The developer community’s reaction has been predictably split. Over on r/overclocking, the thread is half celebration, half warnings about stability risks—though no one’s reported a bricked board yet. Meanwhile, Asus’s forums are radio silent, because officially acknowledging this would mean admitting their BIOS updates are policy, not physics. The real signal isn’t the hack’s success; it’s the silence from Intel’s usual ‘unsupported config’ warnings. When even the chipmaker won’t deny it’s possible, the jig is up.
For all the noise about AI ‘democratizing’ tech, this is what it actually looks like: a $20/month chatbot outmaneuvering a $200B company’s update strategy. The modder’s GitHub repo already has forks targeting other ‘unsupported’ CPUs—AMD’s Ryzen 8000G on AM4 might be next. Intel’s segmentation just became a TODO list for LLMs.
In other words, the ‘AI revolution’ just got real—because nothing terrifies a hardware oligopoly like a script kiddie with a Claude subscription and a grudge. The hype cycle usually sells vaporware; this time, it’s selling actual vaporized roadblocks.