Saturday, August 10th 2024
Intel Ships 0x129 Microcode Update for 13th and 14th Generation Processors with Stability Issues
Intel has officially started shipping the "0x129" microcode update for its 13th and 14th generation "Raptor Lake" and "Raptor Lake Refresh" processors. This critical update is currently being pushed to all OEM/ODM partners to address the stability issues that Intel's processors have been facing. According to Intel, this microcode update fixes "incorrect voltage requests to the processor that are causing elevated operating voltage." Intel's analysis shows that the root cause of stability problems is caused by too high voltage during operation of the processor. These increases to voltage cause degradation that increases the minimum voltage required for stable operation. Intel calls this "Vmin"—it's a theoretical construct, not an actual voltage, think "speed for an airplane required to fly". The latest 0x129 microcode patch will limit the processor's voltage to no higher than 1.55 V, which should avoid further degradation. Overclocking is still supported, enthusiasts will have to disable the eTVB setting in their BIOS to push the processor beyond the 1.55 V threshold. The company's internal testing shows that the new default settings with limited voltages with standard run-to-run variations show minimal performance impact, with only a single game (Hitman 3: Dartmoor) showing degradation. For a full statement from Intel, see the quote below.
Source:
Intel
Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop ProcessorsIntel 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.
119 Comments on Intel Ships 0x129 Microcode Update for 13th and 14th Generation Processors with Stability Issues
As to the new microcode still pushing 1.475v this is expected in short bursts but 1.5v+ to 1.6v is a problem and on my MSI Z790 Carbon Wifi even at auto, seen nothing hitting 1.5v even on the Intel Extreme profile...Still a bet some motherboard manufacturers are srtuggling to get the new bios fine tuned and right.
We complain about stock settings, but in the same time you would like to maintain stock performance? That does not make any sense.
"Stock performance" is too high and you will kill the chips trying to maintain it.
Instead of doing the right thing, Intel is desperately trying to maintain the frequencies, because if they lowered the frequencies as they should, they would create a different product with lower performance than what the customers expected when they bought the chips.
Intel will need to figure how to deal with this lower performing product, because trying to keep the breakneck frequencies is simply not possible.
But when it comes to the voltages, the recent updates do seem to be trying to reign that stuff in. This cpu has actually been acting all right the last couple days. When I first took the chains off I was a bit worried by a max vcore of 1.44 but since doing the 13700k emulation ( thats when I got 1.35 max btw), then going back, and I don't know why, it hasn't been as bad, it doesn't pass 1.4v 99% of the time and when it does its only 1.41 or something. Most of the time its in the 1.2s and or 1.3s. Like right now I've just been gaming and vcore is at 1.34. But its not like its a heavy load just sandland at 4k60 plus firefox and a couple utilities, but it doesn't seem to get all that much higher under the heavy loads. Plus with this new ucode I know there's not going to be any crazy transients. Maybe it will be okay in the end?
Uh oh, I just jynxed it, didn't I?
But surprisingly, I put in a 1.5v vid limit and I thought okay there's no way this is going to affect performance... but it did. Not alot, but enough to notice in passmark cpu test like 1-2%. I don't think it was run to run variance either because I repeated the test many times making sure nothing else was running in the background etc. There's clearly more going on behind the scenes than our monitoring software is telling us because neither hwmonitor or hwinfo reports vid anywhere near 1.5. Maybe intel does know what they are doing? I'm not sure to keep that limit there or not. Right now I removed it, not for the performance but just cause.... well, I'm just following intel's instructions.
Not saying I trust them all of a sudden but idk what if that limit messes with something I don't understand? There's just so many people out there with so many takes, it gets kinda exhausting you know? And I got my rma too. And even if I don't get cross shipping, I still have my handy dandy 12100 to use in the meantime =D I have a feeling that both its not nearly that simple, but also that there's probably a kernel of truth in there. Just a guess.
I noticed recommended iccmax from intel for 13700k and 14700k was the same but thats just one ecore cluster.... What about 4 ecore clusters disabled and iccmax not changed, is that... dangerous? Again I don't know maybe he changed it earlier or I got it all wrong. Just something I've been wondering for a while.
Anyway... goodnight.
The latest microcode is a mitigation only and they have no idea how to handle the situation without losing a lot of money.
They've said elevated voltages can cause instability.
They've said they're releasing a microcode patch to fix the root cause of said elevated voltage.
But putting these two together != "the root cause of stability problems is caused by too high voltage"
Validator:
valid.x86.fr/qsscee
The CB version is very important, v15.0.3.7 is way better than 15.0.3.8 for stability purposes.