Intel issues statement on microcode update that addresses CPU instability and crashing errors — claims patch has negligible performance impacts, future processors not impacted
You need to install a BIOS update to ensure that your Raptor Lake CPU is not frying itself.
For the first time, Intel has detailed its new patch, which recently started distributing via the 0x129 microcode patch released by its OEM/ODM partners. This update will address the issue of incorrect voltage requests made by the processor, which causes it to ask for elevated voltage. Intel says this results in long-term damage to the affected chips, manifesting as instability and crashing errors.
The patch reins in voltage, instituting a hard 1.55V limit as the company investigates potential mitigations for a related issue — a minimum voltage shift condition that can occur on already-impacted processors. The company will provide an update on the minimum voltage issue before the end of the month. We've asked for more details. Intel also says that all future processors will not be impacted.
However, Intel said in a statement to Tom's Hardware that this microcode patch will only be available through BIOS updates and not through Windows Update. This means users who aren't knowledgeable of the issue would likely not install the patch on their system, increasing the likelihood that their Raptor Lake processor would fail in the long run.
Thankfully, Intel has extended the warranty coverage of several affected 13th- and 14th-gen chips, including Core i5, i7, and i9 processors. The warranty extension covers 22 SKUs, allowing you to file for an RMA directly with Intel if you bought a Boxed Processor. But if you bought a pre-built PC with an affected Intel chip or a Tray Processor, you must go through your retailer. However, your mileage may vary as different manufacturers and retailers have their own policies regarding Intel's warranty extension.
According to Intel, the source of the issue is a "significant increase to the minimum operating voltage (Vmin) across multiple cores on affected processors due to elevated voltages. Elevated voltage events can accumulate over time and contribute to the increase in Vmin for the processor."
The 0x129 update will limit voltage requests above 1.55 volts to prevent chips that are still unaffected by the instability from getting damaged. Intel also said, "…based on extensive validation, all future products will not be affected by this issue." However, chips that are experiencing instability or have already failed will have to go through the RMA process, as there is no fix.
Intel says that those who are concerned about whether the microcode update will affect performance also need not worry anymore, saying that the performance impact of 0x129 is still within run-to-run variation for most benchmarks, including 3DMark: Timespy, Cinebench R24, and others. Gaming performance is also still within the expected parameters, including Cyberpunk 2077 and Shadow of the Tomb Raider. A few tests have shown some impact, though, including PugetBench GPU Effects Score and Hitman 3: Dartmoor, but Intel says, "…system performance is dependent on configuration and several other factors."
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
Of course, Tom's Hardware is already testing the microcode patch to validate Intel's claims, so be sure to check back here frequently for updates. But, in the meantime, it's best to install the BIOS update as soon as possible to reduce the chance of your processor succumbing to overvoltage issues and the resulting chip degradation.
Several motherboard vendors have already released updated BIOSes with the new code, while others have signaled an imminent release.
Here's Intel's full statement:
Intel statement on microcode patch
Intel is currently distributing to its OEM/ODM partners a new microcode patch (0x129) for its Intel Core 13th/14th Gen desktop processors which will address incorrect voltage requests to the processor that are causing elevated operating voltage.
For all Intel Core 13th/14th Gen desktop processor users: This patch is being distributed via BIOS update and will not be available through operating system updates. Intel is working with its partners to ensure timely validation and rollout of the BIOS update for systems currently in service.
Instability Analysis Update – Microcode Background and Performance Implications
In addition to extended warranty coverage, Intel has released three mitigations related to the instability issue – commonly experienced as consistent application crashes and repeated hangs – to help stabilize customer systems with Intel Core 13th and 14th gen desktop processors:
- 1. Intel default settings to avoid elevated power delivery impact to the processor (May 2024)
- 2. Microcode 0x125 to fix the eTVB issue in i9 processors (June 2024)
- 3. Microcode 0x129 to address elevated voltages (August 2024)
Intel’s current analysis finds there is a significant increase to the minimum operating voltage (Vmin) across multiple cores on affected processors due to elevated voltages. Elevated voltage events can accumulate over time and contribute to the increase in Vmin for the processor.
The latest microcode update (0x129) will limit voltage requests above 1.55V as a preventative mitigation for processors not experiencing instability symptoms. This latest microcode update will primarily improve operating conditions for K/KF/KS processors. Intel is also confirming, based on extensive validation, all future products will not be affected by this issue.
Intel is continuing to investigate mitigations for scenarios that can result in Vmin shift on potentially impacted Intel Core 13th and 14th Gen desktop processors. Intel will provide updates by end of August.
Intel’s internal testing – utilizing Intel Default Settings - indicates performance impact is within run-to-run variation (eg. 3DMark: Timespy, WebXPRT 4, Cinebench R24, Blender 4.2.0) with a few sub-tests showing moderate impacts (WebXPRT Online Homework; PugetBench GPU Effects Score). For gaming workloads tested, performance has also been within run-to-run variation (eg. Cyberpunk 2077, Shadow of the Tomb Raider, Total War: Warhammer III – Mirrors of Madness) with one exception showing slightly more impact (Hitman 3: Dartmoor). However, system performance is dependent on configuration and several other factors.
For unlocked Intel Core 13th and 14th Gen desktop processors, this latest microcode update (0x129) will not prevent users from overclocking if they so choose. Users can disable the eTVB setting in their BIOS if they wish to push above the 1.55V threshold. As always, Intel recommends users proceed with caution when overclocking their desktop processors, as overclocking may void their warranty and/or affect system health. As a general best practice, Intel recommends customers with Intel Core 13th and 14th Gen desktop processors utilize the Intel Default Settings.
In light of the recently announced extended warranty program, Intel is reaffirming its confidence in its products and is committed to making sure all customers who have or are currently experiencing instability symptoms on their 13th and/or 14th Gen desktop processors are supported in the exchange process. Users experiencing consistent instability symptoms should reach out to their system manufacturer (OEM/System Integrator purchase), Intel Customer Support (boxed processor), or place of purchase (tray processor) further assistance.
FURTHER READING:
Jowi Morales is a tech enthusiast with years of experience working in the industry. He’s been writing with several tech publications since 2021, where he’s been interested in tech hardware and consumer electronics.
-
DS426 What does Intel mean by saying that aren't releasing the BIOS update via Windows Update? Isn't it purely up to OEM/ODM's, e.g. HP and others to release their own BIOS updates? Intel is making yet another mistake and continuing to crush confidence if they are purposely limiting distribution of the fix; surely, after a month or two of testing, it'd be safe to release to WU.Reply
Also, so they're saying that new chips are modified such that they don't exhibit this defect, regardless of microcode? Would this simply be part of CPU stepping?
And what about the tool to help identify the problem children? -
Gururu Reply
I think the message is that the problem isn't as wide as the enthusiast says it is and like Puget, major pc sellers (Dell, HP) are not sending a wide and clear message to Intel that there is a problem. Custom builders will likely be those for which the fix is most applicable.DS426 said:What does Intel mean by saying that aren't releasing the BIOS update via Windows Update? Isn't it purely up to OEM/ODM's, e.g. HP and others to release their own BIOS updates? Intel is making yet another mistake and continuing to crush confidence if they are purposely limiting distribution of the fix; surely, after a month or two of testing, it'd be safe to release to WU.
Also, so they're saying that new chips are modified such that they don't exhibit this defect, regardless of microcode? Would this simply be part of CPU stepping?
And what about the tool to help identify the problem children? -
evdjj3j "However, Intel said in a statement to Tom's Hardware that this microcode patch will only be available through BIOS updates and not through Windows Update."Reply
Why, reporter? -
Mattzun Really disappointing that the microcode won't be delivered via Windows update.Reply
I'd love to see how high the voltage spikes on a normally configured OEM machine without the patch. -
ThomasKinsley "microcode update"Reply
"negligible performance impacts"
"A few tests have shown some impact"
"a few sub-tests showing moderate impacts"
"system performance is dependent on configuration and several other factors."
Toms' upcoming benchmarks will be much appreciated. -
Loadedaxe Windows (MS) does not do bios updates through WU, its up to board manufacturers and OEMsReply -
CelicaGT Reply
They absolutely do, for larger OEMs like Dell and HP. My Dell G15 did one last month when I first received it. I was quite surprised to learn firsthand this was a thing. In this case however, I think what intel is referring to is the typical microcode soft updates that are loaded on boot on pretty much every system, not an actual BIOS update.Loadedaxe said:Windows (MS) does not do bios updates through WU, its up to board manufacturers and OEMs -
thestryker JayzTwoCents did some initial testing with the new microcode and the performance differences seem random. None of the differences appeared to be big and the highest voltage they saw with the new microcode was 1.51V.Reply
The way I interpret the statement is that they won't be issuing the microcode update by itself through Windows Update (they've done this in the past). That shouldn't have any impact on OEMs who may deploy BIOS updates through Windows Update.DS426 said:What does Intel mean by saying that aren't releasing the BIOS update via Windows Update? Isn't it purely up to OEM/ODM's, e.g. HP and others to release their own BIOS updates? Intel is making yet another mistake and continuing to crush confidence if they are purposely limiting distribution of the fix; surely, after a month or two of testing, it'd be safe to release to WU. -
Guardians Bane Reply
OEMs (most that is) seem to have custom mobos. So maaaaby they can offer the updated microcode through customer accounts or something like that? Everyone is saying the mobo partners are pushing the updates, so maybe the OEMs will do the same as well somehow?DS426 said:What does Intel mean by saying that aren't releasing the BIOS update via Windows Update? Isn't it purely up to OEM/ODM's, e.g. HP and others to release their own BIOS updates? Intel is making yet another mistake and continuing to crush confidence if they are purposely limiting distribution of the fix; surely, after a month or two of testing, it'd be safe to release to WU.
Also, so they're saying that new chips are modified such that they don't exhibit this defect, regardless of microcode? Would this simply be part of CPU stepping?
And what about the tool to help identify the problem children?
I haven't bought a DT pre-built in a long time, so I really don't know how they would do it. I'm just throwing an idea out there to somehow make sense of all this. Lol -
wingfinger So intel has a policy that it won't provide microcode updates or ME firmware updates directly to computer owners.Reply
Is it that the OEMs complained about returns caused by bad flashes?
Are the BIOSs so entangled and fragile, they cannot accept CPU fixes without validation?
Is it better to suffer exploited vulnerabilities or actual damage, than to allow a fix that could fail.
Are we, the end consumers, now and now+, less important than your business partners? We both need your products, or a similar products.