Tuesday, July 23rd 2024
Intel Statement on 13th and 14th Gen Core Instability: Faulty Microcode Causes Excessive Voltages, Fix Out Soon
Long-term reliability issues continue to plague Intel's 13th Gen and 14th Gen Core desktop processors based on the "Raptor Lake" microarchitecture, with users complaining that their processors have become unstable with heavy processing workloads, such as games. This includes the chips that have minor levels of performance tuning or overclocking. Intel had earlier isolated many of these stability issues to faulty CPU core frequency boosting algorithms, which it addressed through updates to the processor microcode that it got motherboard- and prebuilt manufacturers to distribute as UEFI firmware updates. The company has now come out with new findings of what could be causing these issues.
In a statement Intel posted on its website on Monday (22/07), the company said that it has been investigating the processors returned to it by users under warranty claims (which it has been replacing under the terms of its warranty). It has found that faulty processor microcode has been causing the processors to operate under excessive core voltages, leading to their structural degradation over time. "We have determined that elevated operating voltage is causing instability issues in some 13th/14th Gen desktop processors. Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor."Modern processor power management runs on an intricate clockwork of collaboration between software, firmware, and hardware, with the software constantly telling the hardware what levels of performance it wants, and the hardware managing its power- and thermal budgets by rapidly altering the power and clock speeds of the various components, such as CPU cores, caches, fabric, and other on-die components. A faulty collaboration between any of the three key components could break this clockwork, as has happened in this case.
Intel is releasing yet another microcode update to its 13th- and 14th Gen Core processors, which will address not just the faulty boosting algorithm issue the company unearthed in June, but also the faulty voltage management the company discovered now. This new microcode should be released some time around mid-August to partners (motherboard manufacturers and PC OEMs), who will then need to validate it on their machines, before passing it along to end-users as UEFI firmware updates.
Meanwhile, an interesting issue has come to light, which that some of Intel's processors built on the Intel 7 node are experiencing chemical oxidation of the die as they age. Intel responded to this, stating that it had discovered the oxidation manufacturing issues in 2023, and addressed it. The company also stated that die oxidation is not related to the stability issues it is embattled with.
Sources:
Intel Community, Intel (Reddit)
In a statement Intel posted on its website on Monday (22/07), the company said that it has been investigating the processors returned to it by users under warranty claims (which it has been replacing under the terms of its warranty). It has found that faulty processor microcode has been causing the processors to operate under excessive core voltages, leading to their structural degradation over time. "We have determined that elevated operating voltage is causing instability issues in some 13th/14th Gen desktop processors. Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor."Modern processor power management runs on an intricate clockwork of collaboration between software, firmware, and hardware, with the software constantly telling the hardware what levels of performance it wants, and the hardware managing its power- and thermal budgets by rapidly altering the power and clock speeds of the various components, such as CPU cores, caches, fabric, and other on-die components. A faulty collaboration between any of the three key components could break this clockwork, as has happened in this case.
Intel is releasing yet another microcode update to its 13th- and 14th Gen Core processors, which will address not just the faulty boosting algorithm issue the company unearthed in June, but also the faulty voltage management the company discovered now. This new microcode should be released some time around mid-August to partners (motherboard manufacturers and PC OEMs), who will then need to validate it on their machines, before passing it along to end-users as UEFI firmware updates.
Intel is delivering a microcode patch which addresses the root cause of exposure to elevated voltages. We are continuing validation to ensure that scenarios of instability reported to Intel regarding its Core 13th/14th Gen desktop processors are addressed. Intel is currently targeting mid-August for patch release to partners following full validation. Intel is committed to making this right with our customers, and we continue asking any customers currently experiencing instability issues on their Intel Core 13th/14th Gen desktop processors reach out to Intel Customer Support for further assistance, the company stated.It's important to note here, that the microcode update won't fix the issues on processors already experiencing instability, but prevent it on chips that aren't. The instability is caused by irreversible physical degradation of the chip. These chips will, of course, be covered under warranty.
Meanwhile, an interesting issue has come to light, which that some of Intel's processors built on the Intel 7 node are experiencing chemical oxidation of the die as they age. Intel responded to this, stating that it had discovered the oxidation manufacturing issues in 2023, and addressed it. The company also stated that die oxidation is not related to the stability issues it is embattled with.
We can confirm that the via Oxidation manufacturing issue affected some early Intel Core 13th Gen desktop processors. However, the issue was root caused and addressed with manufacturing improvements and screens in 2023. We have also looked at it from the instability reports on Intel Core 13th Gen desktop processors and the analysis to-date has determined that only a small number of instability reports can be connected to the manufacturing issue, the company stated.If you feel your chip might be affected, you can file for an RMA.

387 Comments on Intel Statement on 13th and 14th Gen Core Instability: Faulty Microcode Causes Excessive Voltages, Fix Out Soon
I think if you've bought a "253W" Intel CPU in the last half-decade, you've known what you're getting yourself into and hopefully you've either bought the 350W+ motherboard and ridiculous cooler needed to accommodate it, or you've gone into your BIOS and enforced your own, strict limits on how much trouble your "253W" processor can actually get itself into by locking PL1 and PL2 to reasonable values for your cooling and preferred noise levels. Sure, you're not going to get the same performance as the published benchmarks show when the CPU can actually guzzle >300W but at just 150W the 12th/13th/14th gen CPUs aren't actually bad at all; They're simply ruined by extremely inefficient overvolt/overclocks right out of the box by Intel.
TechPowerUp have done some power limited benchmarking which to Intel's credit does show that behind the process gap there is some good IPC capability, but as a product I'm amazed so many people have bought these K/KS SKUs...
I feel bad for those who have more normal CPUs... especially those with T series chips which are meant to be lower power... they should really be nowhere near an 'excess voltage' problem.
IIRC 12th gen at 125W power limit wasn't far off the performance of an 88W Zen3 competitor at the time, and considering it was the class-leading TSMC 7FF vs Intel's shaky
10nm"7" process, that's actually a pretty decent result, IMO.It all went wrong when Intel decided that
350W400W+ was an acceptable power draw for a consumer CPU.Edit - apparently I'm out of touch. The 14900KS pulls 410W from the socket. Holy ****, batman - suddenly the 7800X3D's winning performance at around 80W makes this overclocked-to-death fiasco by Intel even sillier!
The problem is that Intel was afraid of getting spanked by AMD on performance, so they let their marketing/sales department overrule their engineers and sold chips that were overclocked to hell and gone. And that makes them look better in benchmarks, but in the long run it causes stupid, expensive, trust-destroying shit like this to happen.
And then AMD went and did the exact same goddamn thing with Zen 4 and it pisses me off so much. Obviously Intel is at fault here because if they hadn't done it AMD wouldn't have, but it pisses me off because two wrongs don't make a right, they just compound stupidity. And the last thing AMD should be doing to succeed, is copying their competitor's most stupid of ideas.
Basically, I hate marketing/sales people, but more than that I hate the dysfunctional "management" at Intel that allowed this to happen at all. They should all be fired into the Sun.
125W is only 0.8% slower than 241W, which means that even 125W is at or already beyond the point of diminishing returns; There's basically nothing left on the table after that except excessive heat and noise but Intel decided 410W was the answer and here we are today in this embarrassing mess for Intel... :\
Hence my previous comment:If it wasn't for the E-cores being present for example, the I5-12600K would have offered little over the plain 12600 or even the 12400.... and this same irony has persisted into Raptor Lake - the 'efficiency' E cores only present on higher TDP wasteful SKUs to eek out some cinebench wins....
Multi-core productivity is a different story.
If shopping at the low-end, people buying a Ryzen 7600X instead of a 7600 (and keeping the change for maybe a bit more RAM, bigger SSD, better GPU, or just plain old beer money) confuses me especially if they plan to upgrade....
The last few Intel generations in the latter stages of Skylake / Coffee Lake showed the K CPUs starting to offer a lot less value and diminishing returns in terms of how much you can push the envelope.... those Sandy Bridge days are looooong gone.
With Alder Lake/Raptor Lake, buying the K/KS parts really just meant buying a CPU with a higher turbo boost clock and power limit, but on a process which meant thermal limits would effectively neuter a lot of that clock speed potential. Sure, you 'can' overclock them but they are so close to the red-line that it's not as practical as it used to be.
It probably isn't even that measurable at the power socket due to the increasing efficiency of PSUs as power load ramps up... even 80plus platinum PSUs are not very good under 10% of their power rating in most cases.
I appreciate my i7's low idle power usage when adjusted and I appreciate my R7 5700X3D's (and 5800X3D) low gaming power usage with no adjustments. That said, the idle difference is barely 10W as you mention and games really seem to like 8C8T as much as X3D as long as CPU usage stays under about 90%.
Oh, middle august, that's not fixed tomorow tho
Just because its software internal to the CPU doesn't change the fact that its largely unavailable to typical programmers. Its effectively part of the CPU.
-------
I've said it before: "Division" (and modulus) are both operations that are almost-always implemented as microcode rather than pure hardware. From the perspective of modern programmers, the "div" and "idiv" instructions are effectively a hardware implementation. Microcode does a lot in modern CPUs because of how hugely complex these modern processors are.
In my case (14700KF) i'm suffering from OS file corruption fixed via sfc /scannow.
-----
While there are many theories in circulation, and many have their suspicions about Intel's explanation, theirs is the most logical explanation to date. But time will tell. I've too have followed the coverage from news sites, Level1techs, GamersNexsus and others, and while I think thorough third-party investigation is more than welcome (perhaps even necessary), they should make sure to have the right (engineering) expertise to assess it properly (possibly even request hardware debugging tools and data about silicon quality?).
It has been suggested that about half of affected CPUs may be fixed with firmware, but let's dismiss that one outright; if there is (for any reason) abnormal wear, no firmware will reverse that. The fixed firmware will (presumably) avoid further abnormal wear.
Also various estimates of rates of completely defective CPUs of 20%, 50% or even ~99%, which I highly doubt.