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
I can use vcore moving forward on TPU, not a problem for me, as I agree with what you said.
The problem is you state certain loads. But never say which one.
Oh no 1 core utilized 1.5v to obtain a frequency of 5.6ghz through 6.0ghz depending on the cpu model. This does not mean 250w man.
The issue is from heavy loads like all cores and the wattage. So Volt x Amp = wattage.
1.35v limited while under all core load drooping to 1.288v. That's a big droop. Why not just set 1.288v with a higher LLC and keep a sustained v-core? You'd still be at nearly 250w peak consumption....
People really should look at the amps. Lower that. V-core isn't a big deal. Well it is to those that don't understand it I suppose.
OK - Sorry for double post.
This is TWO cores at 1.682v Cpu-z reading with High LLC so keeping fairly stead 1.68v observed during the benchmark as minimum.
This is only 60w...... Edit: (Only 1 core utilized for the benchmark.)
Degradation?
Looks like there's a whole mess with the settings going on - and looks like my setup is affected too. Video showed me how to improve on the situation. Might have changes coming with newer BIOSes
In the end the mess I think was just his cinebench being detected as a background app and limited to e-cores only by windows I think, he said it at the end.
Turns out, cpu runs fine on my B660-G board with first release ME firmware. Which is sad cause I'd like to get back to overclocking.
The problem Intel has is that once ME updates, you can't roll it back. They fucked themselves with that.
Chip has been running great since release and at this point, and
I've not really owned an Intel cpu since 3570K days, so not really been into this stuff much, but I do watch buildzoid for MB/memory recommendations and have followed his videos since these issues first started popping up.
So I took the shackles off my cpu ( haven't decided if I'm going to keep it that way)
I'm getting a maximum of 1.43 vcore (as per hwinfo) after running the passmark cpu test (includes multi and single core). And... I even turned off turbo 3 off so there'd be no 5.6 cores. Put ac at 90 instead of the 110 it was at originally. And left the 253 limit on, so otherwise still 'intel defaults= high performance' which includes 307 iccmax so its not 100% unbound.
Really goes to show how the 14700k is just an overclocked 13700k, its not better binned or, at least in my case. Guess that was just me fooling myself when I made the purchase.
On one hand its like should I just go back down to 5ghz and turn off some ecores? Turn down the power limits.... Pretend its like a 13600k/13700k and hope it lives a long life? Its not like that extra 10% of performance really matters for daily tasks. On the other its like, because I damn well paid for it whats why, and rma has been extended so if something goes wrong, maybe I'll get a better sample?
I just don't know ='(
Can always go back to 104 and do offsets but that corrupted my os last time I tried so I don't think I have much wiggle room (even though I did in January..... not a comforting thought) then again thats also when I found a couple pieces of something in my socket so that could have been what was causing issues. Also don't want to lose these new ucode protections...
On the bright side, I can confirm the vid limit (1.4) in my bios works as before turning it off all my pcores could not hit 5.5 unless they were basically idle. (Actually for some reason, vid was showing not going higher than 1.37... but thats software reporting for you I guess)
Perhaps setting a vid limit of 1.5 would be enough to allow me to hit 5.5 consistently enough while also offering a bit more protection than what intel is offering. Does intels vid limit vary by sku or is it just 1.55 across the board? I would really like to know.
Too much choices, giving me a headache. Anyway sorry for venting.
I do have my power limits conservative and even lowered my tjmax from 100C to 95C might drop it later to 90C. My power limits are 175w for short and 125w for long. I ran a quick and dirty CPUZ bench yesterday which hit the 175w limit, but still outscored the 12900k reference on it. Yeah similar situation for me.
So, if you haven't updated, does that mean your ac/dc loadline is at 110? (since the default just changed for me, not sure if thats a gigabyte or intel thing) Should be in hwinfo>summary>Motherboard under 'ai ac loadline' and ''ai ad loadline.' As of now my other loadlines are all on auto. Just to get it as close as possible.
How did you get it down to 5ghz then?
I had a look at my notes for AC/DC, so basically I equalised them as intel now recommends, 1.10/1.10 is set in bios, and this bumped my voltages up a bit so thats why my undervolt increased to -75mv. I think it might be ok to reduce them, but they both should be same value.
That's been the case since basically day 1 bios -- they released a bios later where you could turn off the undervolt protection, and that let the chip crash but rip at full performance with an undervolt. I think the undervolt protection just underclocks the chip if the voltage fed is below the vid table and it's just a flat 50% underclock.
Max vcore of 1.35. See that seems more normal to me. If a -75mv offset were stable on here ( don't know, don't want to try, since it involves ucode 104 which I've had bad luck with - twice! That thing is cursed). That would put us roughly around the same, right? If I were to jump to conclusions, it would almost seem like 13700k and 14700k aren't even binned that differently. I guess I assumed that was the whole point of the new gen. No new silicon, but move the bins up a tier.
Anyway yeah thats why I do have to use the ac/dc loadline as other than frequency its pretty much my only tool to affect vcore while staying up to date. But I can only get so far with it. 90 seems to have the same performance as 110 at least as far as I can see. Somebody on reddit suggested 60 but my performance nosedived. I guess some people increase llc to make up for this but w/e. Intel's whole system is just too complicated as far as I'm concerned. I'm just gonna run intel defaults with ac/dc at 90 and turbo 3 off, vid limit of 1.5 and try to forget about it.
.
.
.
.
.
.
.
Off topic but last time I ran this test on my 14700k, the score was 14700, I'm not even kidding... I think I still have the pic.....
lol!
There are plenty of videos online as proof they exceeded the 253W Intel specification.
Everyone has their own way of stress testing, I prefer to not go overboard so for me, its usually a few runs of each cinebench, asusbench 30 minutes, and 5 minute run of each xtu stress test (standard, avx, avx2, memory), and also the xtu bench, as I have in the past had bench cause instability. Also memory testing but no need in your case as you only adjusted the cpu params. Then just using the machine, as transient loads always have the potential to throw something up. Keep an eye on WHEA counter as well, hwinfo does log the counter for conveniance. I think with the loadline you set, I dont see why the chip would be unstable though as you still on the stock v/f curve.
Now intel have confirmed wattage isnt the root cause but its voltage, I may change my pl1/pl2 back to 175/175. Although I dont anticipate any workload I would run that would need that wattage, as I have only ever exceeded 125w in a benchmark or stress application. 175 is about right for my cooler/ambient/case airflow combination.
I seen your post in the other thread as well, and i do agree with the other guys, your chip is 5 year warranty now, and even at stock you are well within Intel's guidelines. But if you are uncomfortable above 1.4v, it looks like this 13700k config might be an acceptable middle ground for you.
Intel have extended the warranty for a further two years for all 13th and 14th gen which is a start and I believe RMA's are going through a bit more smoothly though losing your CPU for a week or two cannot be a nice thing. I use to have a Gigabyte motherboard and all I can say it the bios was a mess and once you start making any voltage changes things can go off very quickly. In fact even wwhen I made changes the old changes were not removed and only a hard bios reset. removing battery would get oit back to normal...I was pulling out my hair...changed to ASUS which was also just another painful experience as the voltage they ware pushing on anything auto or 'multicore enhancment' was a joke. On MSI now which has been better but they too were pushing too much but in terms of fine grained control, it seems a lot better. Only manufacturer I have not tried is AS Rock.