The encyclopedia · Product & Design · Product decision · 2024
Intel's 13th- and 14th-gen CPUs crashed worldwide because of a voltage microcode bug
A flawed microcode algorithm pushed desktop processors past safe voltages, causing crashes and forcing Intel to extend warranties.
Intel · 2024-07-22
What happened
Intel's 13th- and 14th-generation Core desktop processors, sold under the Raptor Lake family, were marketed as the company's highest-performance consumer chips. Starting in late 2022, users began reporting crashes, blue screens and instability, especially on unlocked K-series models.
In July 2024, Intel confirmed that the root cause was a microcode algorithm that sent incorrect, excessive voltage requests to the processor. The elevated voltage caused progressive degradation in some chips; once a CPU had crashed repeatedly, the damage could be permanent even after a patch.
Intel issued a microcode update and extended warranties by two years, but the incident damaged the company's standing in the enthusiast and gaming PC market and coincided with a period of intense competition from AMD.
Why it happened
- The microcode was not validated across the full range of real-world motherboards and power-delivery settings before release.
- Intel and its motherboard partners marketed aggressive power and frequency profiles that pushed silicon past its reliable operating window.
- The company treated early crash reports as isolated incidents rather than a systemic design problem for more than a year.
- The warranty extension came only after public pressure and competitor gains, not at the first sign of widespread failure.
The lesson
When performance marketing pushes silicon to the edge, validation must catch the chips that degrade before the customer does.
Aftermath
Intel released microcode patches and extended warranties, but some damage to degraded chips was irreversible.
Sources
- There is no fix for Intel's crashing 13th and 14th Gen CPUs — The Verge
- Intel details fixes for crashing 13th- and 14th-gen CPUs as BIOS updates roll out — Ars Technica
spotted an error? The club wants to know.
More like this
Twitter rejected the hashtag — users invented it anyway
Steve Jobs didn't want third-party apps on the iPhone — the App Store saved it
Android was designed for a keyboard phone — then iPhone forced a complete redesign
Somewhere, someone solved the problem this company failed at. 2nd Opinion →
Comments · 0
Sign in to join the comments.