Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Contribute
Create a page
How to help
Wiki policy
Adapt videos to articles
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Consumer_Action_Taskforce
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Intel CPUs stability issue
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Third statement=== The issues mentioned above have led to some CPUs becoming irreversibly damaged, resulting in the '''Vmin shift'''. High operating temperatures cause the silicon in the processor to degrade, requiring a higher minimum voltage to operate stably. This, in turn, leads to even higher temperatures, creating a vicious cycle that ultimately results in the CPU failing. Intel has identified four key issues contributing to the instability. For the explanation of each issue, refer to the full statement below. ====Official statement (September 25, 2024)<ref>[https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633446#M40 Third statement]</ref>:==== <blockquote>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:''' #Motherboard power delivery settings exceeding Intel power guidance. '''a. Mitigation:''' IntelĀ® Default Settings recommendations for IntelĀ® Coreā¢ 13th and 14th Gen desktop processors. #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. #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. #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: <nowiki>https://compatibleproducts.intel.com/</nowiki>. #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). #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) </blockquote>
Summary:
Please note that all contributions to Consumer_Action_Taskforce are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Action Taskforce:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)