[Intel] Sept 2024 (Update on Instability Reports on Intel Core 13th and 14th Gen Desktop Processors

[Silent_Scone]

September 25th Update:

Beta BIOS Links (microcode 0x12B)

Note: Some pages may not have propagated, please check back later

• ROG MAXIMUS Z790 HERO

• ROG MAXIMUS Z790 HERO EVA-02 EDITION

• ROG MAXIMUS Z790 DARK HERO

• ROG MAXIMUS Z790 APEX

• ROG MAXIMUS Z790 APEX ENCORE

• ROG MAXIMUS Z790 FORMULA

• ROG MAXIMUS Z790 EXTREME

• ROG MAXIMUS Z790 HERO BTF

• ROG STRIX Z790-E GAMING WIFI

• ROG STRIX Z790-E GAMING WIFI II

• ROG STRIX Z790-F GAMING WIFI

• ROG STRIX Z790-F GAMING WIFI II

• ROG STRIX Z790-A GAMING WIFI

• ROG STRIX Z790-A GAMING WIFI II

• ROG STRIX Z790-A GAMING WIFI D4

• ROG STRIX Z790-H GAMING WIFI

• ROG STRIX Z790-I GAMING WIFI

• PROART Z790-CREATOR
  
  Z690
  

• ROG MAXIMUS Z690 HERO
• ROG MAXIMUS Z690 HERO EVA EDITION
• ROG MAXIMUS Z690 APEX
• ROG MAXIMUS Z690 FORMULAROG MAXIMUS Z690 EXTREME
• ROG MAXIMUS Z690 EXTREME GLACIAL
• ROG STRIX Z690-I GAMING WIFI
• ROG STRIX Z690-A GAMING WIFI
• ROG STRIX Z690-A GAMING WIFI D4
• ROG STRIX Z690-G GAMING WIFI
• ROG STRIX Z690-F GAMING WIFI
• ROG STRIX Z690-E GAMING WIFI

Z760

• PROART B760-CREATOR
• PROART B760-CREATOR D4
• PROART B760-CREATOR WIFI
  
  Intel Community Forum
  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. 

______________________________

August 2024

Hi all,

This update will be pinned here for clarity on the ongoing situation with some 13th and 14th-gen CPUs experiencing instability exhibited at stock.

Intel has issued the following statement (07/22/2024)

Based on extensive analysis of Intel Core 13th/14th Gen desktop processors returned to us due to instability issues, we have determined that elevated operating voltage is causing instability issues in some 13th/14th Gen desktop processors. Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor.

Intel is delivering a microcode patch which addresses the root cause of exposure to elevated voltages. We are continuing validation to ensure that scenarios of instability reported to Intel regarding its Core 13th/14th Gen desktop processors are addressed. Intel is currently targeting mid-August for patch release to partners following full validation.

Intel is committed to making this right with our customers, and we continue asking any customers currently experiencing instability issues on their Intel Core 13th/14th Gen desktop processors reach out to Intel Customer Support for further assistance.

https://community.intel.com/t5/Processors/July-2024-Update-on-Instability-Reports-on-Intel-Core-13th...

For CPUs that exhibit unstable behaviour

Ensure you're on the latest BIOS for your motherboard

Update your motherboard BIOS to the latest revision containing microcode 0x125. Whilst this ucode revision does not resolve the issue, Intel has clarified that it contains fixes within microcode pertinent to Enhanced Thermal Velocity Boost (ETVB) behaviour that results in unexpected boost behaviour under certain thermal conditions.

Use Intel Base Profiles
The latest BIOS for your motherboard should contain Performance Preference options for Intel Base profiles. Ensure Intel Default Settings is selected. If using a 13th-Gen or 14th Gen i9 processor, choose Profile Performance.
If not selected already, ensure that SVID Behaviour is set to Intel Fail Safe

My CPU is running hotter using Intel Base Profiles than Asus Optimised, is this normal?
Yes, it can be normal for your CPU to run hotter than usual when using Intel base profiles. This occurs because following Intel's guidelines more closely often results in higher core voltages under certain workloads. Previously, motherboard vendors set the Load-Line Calibration (LLC) lower than Intel's recommendations to achieve lower temperatures while still delivering high performance. However, depending on your motherboard adhering to Intel's guidelines can lead to increased voltages whilst operating within Intel's current limits. This can result in higher operating temperatures depending on the workload.

Disable XMP

XMP is considered overclocking. To eliminate overclocking instability XMP should be disabled if experiencing crashing or unstable behaviour. Be sure to retest the behaviour at DRAM defaults.

Evaluate Cooling

Ensure your CPU cooling is working within the expected realms. If still experiencing instability under the conditions described above, consider reapplying the thermal application and removing any third-party CPU contact frames which may impact signal integrity.

Is my CPU damaged?

If still experiencing instability at Optimised Defaults [Intel - Performance / Extreme Profile] with XMP overclocking disabled, you will need to contact Intel.

I've read there was a fabrication issue with oxidisation, Intel has confirmed it.
This issue is unrelated to the ETVB behaviour and firmware and is a physical defect. Currently,  Intel has gone on record to state that a number of 13th-generation CPUs from 2023 are potentially impacted by this issue

ASUS FAQ

[inge70]

This up and down of the values ​​means nothing. It does not indicate a deterioration of the CPU. In the last 4 UEFI updates I sometimes have a higher value and sometimes a lower one. As you can see, only the value of the E cores changes. It is simply an estimate by the UEFI. Nothing more. If it showed a deterioration of the CPU (see Intel chaos of the last few months), the P cores would certainly also be affected and you would have completely different problems than these values.

[Silent_Scone]

Outside of SP being determined by P0 VID, how the score is ultimately determined isn't public knowledge. It however doesn't have any relation to any kind of silicon aging.

[gur_helios]

Briefly for information because a lot of people are upset that the C1E setting in the BIOS can't be disabled anymore.

You can use ThrottleStop for disabling the C1E state which is permanently set now in the latest BIOS and can't be deactivated anymore. By using ThrottleStop the cores won't be clocking down anymore. Please read the following posts.

https://rog-forum.asus.com/t5/intel-700-600-series/z790-new-bios-2703-cpu-throttling-to-800mhz-probl... 

Regards, Uwe

[Yuvaletzi]

I couldnt find the post that you was saying that it's intel fault with this new C1E enhanced c-states setting but it not! it's totally ASUS fault! I was looking over the websites of MSI and Gigabyte and they not listing that they force on their users this setting, I also have a friend with Aorus MOBO with the newest update and microcode 0X12B he can turn this setting OFF! PLEASE Send a message there to your friends at Asus asking them to release another BIOS update that fixes this! It shouldn't be like this! Why ASUS force on their users to use this setting and the other competing companies won't force their users ???? It really annoys me!! The amount for LATENCY now is not normal really a drop in level!! in a chip that really works well! Why do this? To show the world that the temperatures are lower on the Asus motherboard? Is that the approach?? I won't accept this!

[Silent_Scone]

Intel intends to remove C1E state options through Intel's new RC code update that comes with the microcode. I've not looked at what other vendors are doing, perhaps go to the Intel forum and ask for clarification there.

[Yuvaletzi]

why not give the user an option to choose? this C1E thing for more than a year we could turn on or off the setting why now it will interrupt with something?? trust me it's not what killing this chips and everyone knows it! that's other vendors letting user to tweak this setting that a fact it won't ruin the chip or even degrade him you don't need to be an engineer to understand that, ASUS decided to take the rule to their hands and force you to use this setting for god know which reason if it lower temps or something else which is for the benefit of Asus and not for the benefit of the user, I won't accept that!

[Silent_Scone]

Some important things to take into account here.

I've since reaffirmed with RD that Intel has documented to all motherboard vendors to enforce enabling C1E. Given these changes coincide with multiple Intel RC and CPU ucode updates geared towards extending the longevity of the CPU, they've rightfully followed guidance.

You're free to roll back to an earlier UEFI if you'd rather throw caution to the wind in light of these changes, and nobody here is in a position to fully understand or justify why some vendors may have ignored Intel's guidance, or whether disabling the function in the GUI has any impact.

[Electronic_Punk]

A good compromise would be to make it the default, as it must be now, but allow users to change it.

[Silent_Scone]

Not really, as that was already the case. This guidance from Intel is new. Either way, this is how it is. I'd suggest rolling back if you're not happy.

I've been using the update for some time on the Apex Encore and haven't experienced any adverse behaviour or performance.

[Yuvaletzi]

but why not let the users to choose? at least with the new 0X12B if that so I need to roll back to 0X129 and keep my cpu in "danger" so why not release a new 0X12B without this force setting before? why I need to put my cpu in danger and sacrifice performance ? Please keep this matter forward and ask ASUS if they can release new BIOS update that at least let you choose like you can choose Advanced OC profile ASUS right? you can still put your CPU in danger so why force people to use a settings they won't even need???