Client
Interact with Intel® product support specialists on client concerns and recommendations
27 Discussions

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

Thomas_Hannaford
Employee
4 18 91.2K

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)
18 Comments
reupen
Beginner

Will Intel be releasing a tool to help customers identify if their processors are affected (have degraded)?

loofitheboss
Beginner
SpeedToaster
Beginner

I wonder if the 95C-100C temperature is safe for 24/7 load at lower voltages as long as the vcore is low enough.

However, the instability was caused by high vcore when the chip was idle. Usually chip at idle has a low temperature.

I worry that by stress testing the chip, I may degrade it fast even with safe voltage.

SuperDirty
Beginner

Intel created this issue by allowing eTVB to be overly aggressive and giving free reign to board partners like ASUS who contributed to rapid degradation of the cpus in question. My 13900K failed within a year and I'm sure there's millions more out there that will never figure out why their PC is failing when the blame lies squarely on Intel. There's also the loss of time and productivity when people have to troubleshoot their failing PCs. 

I won't be surprised to see a class action suit over this. 

Chankoro
Beginner

No fixes for C-states bug? Idle voltage of the 14900k would go from 1.35v to 1.48v if C-states is being turned off…

SK123456
Beginner

Is the i5-14500 affected? 
Previous microcode updates did not affect the i5-14500. But this one says for all 13th and 14th gen.

Makito2
Beginner

Yeah, same here. I'm running an i5-13400F and I have a fully up to date BIOS and my microcode update is 0x35.

Rails
Beginner

I've read the update about the Vmin Shift Instability issue for Intel Core 13th and 14th Gen Desktop processors. I have a few concerns and questions:

  1. I'm using an ASUS motherboard with my Intel processor 14900KS.
  2. The 0x12B microcode update, which is supposed to fully address the issue, hasn't been released by ASUS yet for my board.
  3. I have applied the 0x129 microcode update, which partially addresses the problem.

Given this situation, I'm wondering: Is it safe to continue using my system for regular tasks while waiting for ASUS to release the 0x12B update? I'm concerned about potential degradation during this interim period.

OcGen
Beginner

Dear Intel Team,

thanks for providing us with constant updates. I have recently received my replacement for my 13900kf because of instability issues. I bought this Processor to OC and undervolt. After all the microcode adaptations you have implemented, are the previous settings you suggested for stable operations still up to date?

In your post, you mentioned that you found the root cause of the stability issues and mitigated with 0x12B. Do I understand correctly that the stability issues are fully mitigated with my next BIOS update or can stability issues still occur when using the recommended settings?

Thanks the clarification!

 

Cheers

ChoGGi
Beginner

@Thomas_Hannaford wrote:
  1. Motherboard power delivery settings exceeding Intel power guidance. 
    a.  Mitigation: Intel® Default Settings recommendations for Intel® Core™ 13th and 14th Gen desktop processors.

These Intel® Default Settings recommendations?

https://community.intel.com/t5/Processors/June-2024-Guidance-regarding-Intel-Core-13th-and-14th-Gen-K-KF/m-p/1607807

 

I see baseline, performance, and extreme. Which settings should be applied?

asdfadsf234asdf

So the root cause IS a hardware issue. Why hasn't a recall been done? Stop selling faulty hardware with mitigations. 

Ashok12
Beginner

I read your whole article thanks for this update. I am glad that intel has found the root cause.

Could you please confirm if this new code 0x12B is mitigation or permanent patch? This is very important for us.

Because mitigation is totally different than the patch. Mitigation looks intel has reduced the negative effect of high voltage. But still there are chances.

Because other generation processors are not vulnerable. There must be a final patch not mitigation. Otherwise RMA or replaced processors future is uncertain.

murphyba
Beginner

Are the processors safe to use with the 0x125 and 0x129 updates but without the 0x12b update? What defines " ...periods of idle and/or light activity." And what specific conditions cause this?

It is not entirely clear from the post if further damage to the processor is possible without the 0x12b update.

It's also a little confusing, because 0x129 states "microcode 0x129 (August 2024) addresses high voltages requested by the processor." which reads to encompass all high voltage requests. Yet 0x12b states the same at specific conditions. 

DerekPeng
Beginner

I am super curious what this new microcode 0x12b will do.

I am on 0x129 and still getting high temps playing games for 15 mins. I even undervolted my 14700K by 0.01v and still getting 95 deg c. Is 0x12b really going to help or just another show? I am getting sick of this.

 

DerekPeng_1-1727769964996.png

 

Di7
Beginner

I am so frustrated and unhappy with the issue with my i7 14th gen. Had my computer upgraded December last year and have had it back to repairer at least 8 times (or more). I use Lightroom and Photoshop and it is absolutely useless. Shuts down whenever, goes so slow it is useless. Intel should be helping their customers after all this time.  It has now been sent back to Intel to await further investagation. Without a computer yet again....... 

vlec
Beginner

Are we sure this issue doesn't affect 13 and 14th gen laptop processors (e.g. i9-13900h) ?

My sister-in-law reported that her computer is unstable when it's running in performance mode + the CPU reaches extremely high temperatures in this mode.

CommonRustyMullet

Earlier this month my game crashes were getting so bad I couldn't even load into the game menus, at least on certain AAA games such as Red Dead Redemption II. Errors received where random in nature but usually memory access related. Even the Nvidia drivers wouldn't update. This all happening even with the power limits set to Intel specs in BIOS for i9-14900k and installed the 0x125 and 0x129 microcode updates.


It wasn't until I disabled Intel Turbo Boost and Intel Turbo Boost V3 that I was able to play the games again. It was like magic, as they all of a sudden started working again. I didn't have any crashes, was able to update graphic drivers etc etc. Ran like that for two weeks without any issues.

 

I heard about the latest microcode update so I installed it, set BIOS to default values (Gigabyte Z790 UD AX). I ran a few benchmarks which seemed to limit the CPU temperature a bit better -- didn't hit the report limit, 100c, and stay there -- with it bouncing between 95c and 97c which is still ridiculous. Was able to load games and play so I played for a few minutes, went to exit the game and CRASH!. After that, game was unable to load into menu. It seems this latest microcode update has not solved anything.

 

Long story short, Intel should recall this entire line of processors. I have been a dedicated fan of Intel for decades as I had one bad experience with AMD in the past and this situation is so much worse. These processors are expensive and I went all out for the power/performance which I can not have because it relies on Turbo Boost. They market these processors with the highest numbers achievable at a supposedly stable performance, but this time, it is just not happening. Therefore, they are defective and not suited for purpose and deserve to be recalled/refunded.

A true indication of a company's ethics is how they respond when something goes wrong with their product!

CommonRustyMullet

@loofitheboss 

I'm not too sure about this tool achieving what you think it will. In my experience it did not highlight any issues.

With my first i9-14900k (RMA'd), I had extensive BSOD, App crashes, crash on running Intel Extreme Tuning Utility's benchmark feature, the Intel Processor Diagnostic tool did not pinpoint any issues.

I had narrowed the processor issue down to two bad cores by disabling them in BIOS. Once the trouble cores where disabled, I was able to run the benchmark in Intel Extreme Tuning Utility.

 

If this application can't detect a bad core, how would it be able to determine a degraded processor? Unfortunate for me, my replacement process suffers from the issues everyone else is having with high temperatures/app crashes/random misbehaving but I haven't found a reliable test case to troubleshoot. The closest I have come was described in my other post with a completely unusable game until I disabled Intel Turbo Boost.