Mobile and Desktop Processors
Intel® Core™ processors, Intel Atom® processors, tools, and utilities
16582 Discussions

Intel Core 13th and 14th Gen Desktop Instability Root Cause Update

Thomas_Hannaford
Employee
29,532 Views

Following extensive investigation of the Intel® Core™ 13th and 14th Gen desktop processor Vmin Shift Instability issue, Intel can now confirm the root cause diagnosis for the issue. This post will cover Intel’s understanding of the root cause, as well as additional mitigations and next steps for Intel® Core™ 13th and 14th Gen desktop users.

Vmin Shift Instability Root Cause 

Intel® has localized the Vmin Shift Instability issue to a clock tree circuit within the IA core which is particularly vulnerable to reliability aging under elevated voltage and temperature. Intel has observed these conditions can lead to a duty cycle shift of the clocks and observed system instability.  

Intel® has identified four (4) operating scenarios that can lead to Vmin shift in affected processors: 

  1. Motherboard power delivery settings exceeding Intel power guidance. 
    a.  Mitigation: Intel® Default Settings recommendations for Intel® Core™ 13th and 14th Gen desktop processors.  
  2. eTVB Microcode algorithm which was allowing Intel® Core™ 13th and 14th Gen i9 desktop processors to operate at higher performance states even at high temperatures. 
    a.  Mitigation: microcode 0x125 (June 2024) addresses eTVB algorithm issue.  
  3. Microcode SVID algorithm requesting high voltages at a frequency and duration which can cause Vmin shift. 
    a.  Mitigation: microcode 0x129 (August 2024) addresses high voltages requested by the processor.  
  4. Microcode and BIOS code requesting elevated core voltages which can cause Vmin shift especially during periods of idle and/or light activity. 
    a.  Mitigation: Intel® is releasing microcode 0x12B, which encompasses 0x125 and 0x129 microcode updates, and addresses elevated voltage requests by the processor during idle and/or light activity periods.  

Regarding the 0x12B update, Intel® is working with its partners to roll out the relevant BIOS update to the public.

Intel’s internal testing comparing 0x12B microcode to 0x125 microcode – on Intel® Core™ i9-14900K with DDR5 5200MT/s memory1  - indicates performance impact is within run-to-run variation (ie. Cinebench* R23, Speedometer*, WebXPRT4*, Crossmark*). For gaming workloads on Intel® Core™ i9-14900K with DDR5 5600MT/s memory2, performance is also within run-to-run variation (ie. Shadow of the Tomb Raider*, Cyberpunk* 2077, Hitman 3: Dartmoor*, Total War: Warhammer III – Mirrors of Madness*). However, system performance is dependent on configuration and several other factors.

Intel® reaffirms that both Intel® Core™ 13th and 14th Gen mobile processors and future client product families – including the codename Lunar Lake and Arrow Lake families - are unaffected by the Vmin Shift Instability issue. We appreciate our customers’ patience throughout the investigation, as well as our partners’ support in the analysis and relevant mitigations. 

Next Steps 

For all Intel® Core™ 13th/14th Gen desktop processor users: the 0x12B microcode update must be loaded via BIOS update and has been distributed to system and motherboard manufacturers to incorporate into their BIOS. Intel is working with its partners to encourage timely validation and rollout of the BIOS update for systems currently in service.  This process may take several weeks. 

Users can check their system/motherboard manufacturer’s website and/or the Intel® Product Compatibility Tool to see the latest BIOS versions for their Intel® Core™ 13th and/or 14th Gen-powered desktop systems: https://compatibleproducts.intel.com/.  

  1. Processor: Intel® Core™ i9-14900K, Motherboard: Intel Raptor Lake Reference Board (M40919), Memory: 64GB DDR5 at  5200MT/s, Storage: ADATA* SU360, Graphics: Intel® UHD Graphics 770, Graphics Driver Version: 32.0.101.5768, Display Resolution: 1280x800, Operating System: Windows 11 Pro (version 26100.712).
  2. Processor: Intel® Core™ i9-14900K, Motherboard: Intel Raptor Lake Reference Board (RVP SR19), Memory: 32GB DDR5 at  5600MT/s, Storage: Samsung* 990 Pro 1TB, Graphics: MSI* RTX 4090 Suprim X, Graphics Driver Version: NVIDIA* v555.99, Resolution: 1920x1080, Operating System: Windows 11 (version 22631.4169)
Labels (1)
14 Replies
AMR41
Novice
29,419 Views


Very good, Thomas Hannafor.
In the case of Gigabyte and the Z790 AORUS ELITE AX (rev. 1.x) board with the i7-14700K processor, how many weeks are we talking about for a normal 'non-beta' bios update to appear?
Kind regards

johnno124
Novice
27,553 Views

I think that would be a question best aimed at Gigabyte. Intel don't create the Bios they just provide the Microcode update to the Board Partners to include in a new Bios Revision

AMR41
Novice
27,259 Views

Thank you Juanno124
“Did you come up with the idea to ask Gigabyte all by yourself, or did you read it in some kind of manual?”
greetings

0 Kudos
johnno124
Novice
27,247 Views

i Used the thing located behind my eyes and between my ears to utilise Common Sense that Intel does not create Bios. The individual Board Partners each have their own UEFI/BIOS for there specific Model. Intel is only responsible for the CPU and Chipset. The BIOS then coordinates the Firmware/Microcodes to ensure everything can talk and report correctly. The Microcode release is not Beta but the Motherboards BIOS is. Again, Talk to Gigabyte if you are concerned about a Beta Bios. 

AMR41
Novice
27,244 Views

The obvious is not an answer that anyone would be interested in.

johnno124
Novice
27,243 Views

It Seems you are more interested in complaining to Intel rather than getting an actual answer then. Hard to take people like you seriously when you refuse to utilise solutions provided to you.

AMR41
Novice
27,236 Views
0 Kudos
Danny_X85
Beginner
18,621 Views

It is available now. I did the BIOS flash today with the FK version contianing the microcode update. I have the same build, so the COD or Stalker test was okay without crashes 

0 Kudos
AMR41
Novice
18,555 Views

Thanks Danny. It's been days since I updated. I posted the results here https://community.intel.com/t5/Processors/Question-about-Bios-Update-Result-with-0x12B-on-Intel-Core-i7/m-p/1638218 and asked two questions that nobody has answered.

0 Kudos
ysk_PLUZ
New Contributor I
29,190 Views

私は以前のRMAのプロセスで『マイクロコード129で劣化の問題が完全に解決したのなら交換してください、他に問題が残っていれば返金してください』と問いました。

intelは交換を選択しました。

UberProGuy
Beginner
26,830 Views

Will equivalent microcode changes still be rolled out for HX family 13th and 14th gen mobile processors, seeing as they are the closest thing to the desktop processors there is?

For shall we say... reassurance and customer trust re-building if nothing else?

0 Kudos
Keean
Novice
26,228 Views

Are there any changes to the recommended BIOS settings with microcode 0x12B?

In particular I am interested in undervolting with CEP disabled. My understanding is that lowering the voltage would lower the current, and that less current (and lower temperatures) would reduce the risk of electromigration.

I understand that undervolting can cause instability, but I am happy to spend the time stability testing larger under-volts than are possible with CEP enabled.

Logically I can't see why CEP would protect the CPU from electromigration (only prevent crashing due to low voltage). However now Intel understands the root cause of the vMin shift, could Intel comment on whether disabling CEP and undervolting is going to damage the clock tree causing the vMin shift?

0 Kudos
Buba
Beginner
21,630 Views
Hello iam new i have asrock z790 pro rs wifi and i7 14700kf, last time update mikrocode 0x12b and temperatures change to 100celsius before update on mikrocode 0x129 temp max 90. Why new update temp up.
0 Kudos
CorpsusVitale
Beginner
17,687 Views

I updated my BIOS 2 months ago, i5-13600KF and MSI PRO Z690-P DDR4. Problems seemed to be solved and my system has been stable ever since. The problems have returned since a good or so (BSOD, lots of access violations is games and other applications). Is a new BIOS update in the making? How can I know if this instability is again related to this issue?

0 Kudos
Reply