Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop Processors

[Thomas_Hannaford]

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:

• June 2024 Intel Default Settings Guidance
• August 2024 Warranty Extension Details

[ysk_PLUZ]

RMAによって【ユーザーがしばらくの間PCを使用できない不利益が生じる】事について、何か対策を検討していますか？

仕事に使用している身としては、不具合が生じても使用できない期間を考えるとRMAを申請するのが難しいです。

[NYC_Fanboy]

Crashes still happening with Asus 0x129 Microcode BIOS.

I will RMA my second 14900 then.

[DeF1]

If you had crashes prior to the 0x129 update then the damage will already be done, bummer! Hopefully no more issues with the replacement now.

[AkramOM603]

Where is the fix for mobile CPUs such as the i9 13980HX, I am experiencing stability issues and game crashes because of memory corruption 0xc0000005, I already checked the RAM with MemTest86, and the results say the RAM is okay! So it's clearly from the CPU!

[wh99]

Which brand is that? I'm worried about my MSi GT77 with i9-13980HX. Any chances that MSI replaces my CPU? I don't want to gamble with a $4,000 computer.

[DeF1]

Has the issue been confirmed to affect mobile chips?

[n_scott_pearson]

Intel has stated not.
...S

[DeF1]

That's what I thought. I think issue above it a different issue. Memory issues can exist but still pass tests such as MemTest86. If you can readily reproduce the issue, try removing one of the dims, try to repo, swap dims and try again. Might narrow down whether one of the dims is faulty. I had a memory failure recently and MemTest86 passed initially. It eventually deteriorated further and MemTest86 would fail.

[AkramOM603]

If there were any memory issues they should have appeared since the beginning when I purchased the laptop end of last year not till May 2024! I also tested with HCI Memtest Pro for around 3~4 Hours and surprise 0 Errors!

 

 

   

[wh99]

I don't think you can perform a full memory test when the operating system is running, since some parts are reserved, and the physical addresses can't be explicitly stated. You must use something like MEMTEST86+.

[AkramOM603]

I will do and share results!

[AkramOM603]

Here you go as I said before it's definitely not the RAM! These crappy CPUs are the problem even on mobile ones!

[n_scott_pearson]

You have no warranty from Intel for processors in a laptop. Your warranty comes from the laptop manufacturer. You need to deal with them regarding any replacement.
This is a moot discussion; Intel has already stated that laptop processors are not affected. So far, all the HX speculation is just that.
...S

[wh99]

Yes Intel does not acknowledge any issues with HX cpus, there are reports from some people:

• i9-13980HX Access memory issue/0xc0000005
• Dota 2 crashes all the time error code 0xc0000005
• Memory leak causing Discord, Chrome and Megasync to crash
• Constant EXCEPTION_ACCESS_VIOLATION(0xC0000005)
• Z790 Maximus Hero ACCESS_VIOLATION (c0000005) in multiple apps/games

[AkramOM603]

Bro, we are literally cooked! RIP 4000$ and RIP my 2500$ and if you go to your OEM they will tell you intel said that you aren't affected (But you are, only time will tell I am experiencing memory corruptions already on my i9 13980HX)!

[XeonCJJ]

Have you tried reinstall the OS? 0xc0000005 is not a memory corruption error. It's a ACCESS_VIOLATION error code. It happens when the program do a invalid memory access (such as reading memory at the address of illegal area (such as 0x00), deferencing a null pointer and such), or loading DLLs of incompatible version are all highly likely), which is very common software bug.

I think if it's a 100% fail then it's not a HW issue since current 13th/14th gen desktop CPU are not experiencing 100% crash (that's one of the reason it's hard to reproduce, thus hard to fix.). You should get your some chance of successfully enter the game and some chance of crush if it's the same issue as desktop ones. Do give reinstalling OS a try.

Currently the Intel official claim the BSOD in laptops are common BSOD issue found in laptops (Just like every laptop before 2022 can still BSOD for a lot of reason). I do remember see some reddit post about 3rd party PC retailer running some stress test (that has a higher rate triggerring BSOD on desktop 13th/14th gen faulty CPUs) on claimed RMAed 13/14th gen laptop but found all issues contributing to BSODs/crashes are not CPU related at all. I think some youtuber (GN for example) is running their own test on laptops claimed has faulty CPU. We can wait and see if laptop are affected according to their test.

[gcgc]

To lend credence to this, I had an issue where some software was corrupted due to the Raptor Lake issues. Even after raising the voltage (the only thing I knew to do back in January), crashing persisted. Fortunately, I'm using NixOS, so I was able to roll back easily, clear out the old data, and rerun the update. Naturally, this isn't a function supported by Windows. (On any other Linux Distro, I'd revert to an older Btrfs snapshot.) At that point it worked reasonable well... for about a week. Again, this was earlier in the year when most people were still in denial so there wasn't much else I could do besides increase voltage.

edit: When I say "some software" I mean "some critical part of the OS that I couldn't easily identify".

[Eisbar]

So this treats a symptom and not the problem?

What is causing the Vmin to shift that requires IA VR to be capped? 

[gcgc]

No, it treats the source of the problem (voltage spikes) and leaves the symptom (crashing) unaddressed, because once it starts crashing, it's permanently damaged.

[ChrisKloß]

Hey, what can I do?
I experience infrequent crashing of apps with my 14900K. It is a tray version and the selling point won't organize a replacement with Intel as long as the crashes are not reproduceable within a couple of minutes. They don't care about all the stuff mentioned here and the media.

Even with the new update I still see VID max values of 1.57 using hwmonitor.