link
More at the link
Basically TL;DR is that intel's highest tier CPUs are drawing so much power and wattage that they're becoming unstable and experiencing silicon degradation within days, weeks, or months of purchase.
If you have an intel CPU I highly recommend undervolting and power-limiting the CPU to preserve its lifespan.
_____________________________________________
UPDATE: Intel issues statement
tom's hardware: intel issues statement
Intel issues microcode patch
Bios updates rolling out via mobo vendors
UP: 9/25/24
root cause confirmed found
The problem is reportedly especially problematic on games that were created in Unreal Engine.
What you need to know
It seems that PC gamers using both 13th and 14th Gen Intel Core i9 CPUs (both Raptor Lake and Raptor Lake Refresh) have reported stability issues when playing video games (thanks TechRadar). This reportedly, is especially an issue for games that run on Unreal Engine where crashing isn't out of the question. Some players are also getting an error that claims their system is "out of video memory" even though their system has plenty of memory to use.
- Intel's 13th and 14th Gen Core i9 CPUs are reportedly causing problems when it comes to PC gaming.
- People are claiming these CPUs are unstable and can cause crashing, especially with games that were created in Unreal Engine.
- These CPUs also reportedly create "out of video memory" errors when a system clearly has plenty of memory.
- This has led to PC gamers in South Korea returning the Intel CPUs and seeking out alternatives like with AMD Ryzen.
- Intel is now looking into the matter.
According to Wccftech, this has led PC gamers in South Korea to return the Intel Core i9 processors and seek out alternatives like AMD Ryzen. Intel is reportedly looking into the matter.
More at the link
Basically TL;DR is that intel's highest tier CPUs are drawing so much power and wattage that they're becoming unstable and experiencing silicon degradation within days, weeks, or months of purchase.
If you have an intel CPU I highly recommend undervolting and power-limiting the CPU to preserve its lifespan.
_____________________________________________
UPDATE: Intel issues statement
tom's hardware: intel issues statement
Intel issues statement about CPU crashes, blames motherboard makers — BIOSes disable thermal and power protection, causing issues
Igor's Lab seems to have obtained a message originally destined for motherboard manufacturers concerning a prolonged stability issue on the company's 13th Generation Raptor Lake and 14th Generation Raptor Lake Refresh chips, which rank among the best CPUs. It made sense for the company to clarify the issue where many blamed the motherboard manufacturers in a race to become 'the fastest' performer by having over-aggressive voltages for allowing higher clock speeds.
The company specifically points out the issue with 600/ 700 series motherboard manufacturers that disable thermal and power protection to achieve the highest possible overclocks, even at the cost of instability. The chipmaker said in the message:
UP:Intel has observed that this issue may be related to out of specification operating conditions resulting in sustained high voltage and frequency during periods of elevated heat.
Analysis of affected processors shows some parts experience shifts in minimum operating voltages which may be related to operation outside of Intel® specified operating conditions.
While the root cause has not yet been identified, Intel® has observed the majority of reports of this issue are from users with unlocked/overclock capable motherboards.
Intel has observed 600/700 Series chipset boards often set BIOS defaults to disable thermal and power delivery safeguards designed to limit processor exposure to sustained periods of high voltage and frequency, for example:
– Disabling Current Excursion Protection (CEP)
– Enabling the IccMax Unlimited bit
– Disabling Thermal Velocity Boost (TVB) and/or Enhanced Thermal Velocity Boost (eTVB)
– Additional settings which may increase the risk of system instability:
– Disabling C-states
– Using Windows Ultimate Performance mode
– Increasing PL1 and PL2 beyond Intel® recommended limits
Intel requests system and motherboard manufacturers to provide end users with a default BIOS profile that matches Intel recommended settings.
Intel strongly recommends customer’s default BIOS settings should ensure operation within Intel’s recommended settings.
In addition, Intel strongly recommends motherboard manufacturers to implement warnings for end users alerting them to any unlocked or overclocking feature usage.
Intel is continuing to actively investigate this issue to determine the root cause and will provide additional updates as relevant information becomes available.
Intel will be publishing a public statement regarding issue status and Intel recommended BIOS setting recommendations targeted for May 2024.
Intel issues microcode patch
Bios updates rolling out via mobo vendors
UP: 9/25/24
root cause confirmed found
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:
Regarding the 0x12B update, Intel® is working with its partners to roll out the relevant BIOS update to the public.
- 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.
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.
Last edited: