[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

[achugh]

I am with other people here. I wish that ASUS and INTEL work out the agreement to remove the forced C1 states from Intel Profiles and release that as another update like 1603.

If you watch https://www.youtube.com/watch?v=vwHVGoY-Z68 video from LEVELONETECH he shares his theory that these lower power states are requesting lower Vmin voltages which are the ones not working out for degraded CPUs. So enabling the HIGH PERFORMANCE or ULTIMATE PERFORMANCE will send a higher voltage to possible get around the issue which cannot be done now. In his video he is showing the concept with a LINUX OS but it is the exact same thing as Windows Power Profiles.

[inge70]

I've also noticed that the BETA phase is taking a lot longer this time.
For the last two updates (2402 and 2503 for my motherboard) the phase lasted a maximum of 1 week and then the BETA flag was removed, the update file remained the same and was declared FINAL.
This time it's obviously different. There might be something else coming after all.
Let's wait and see.

[Silent_Scone]

I wouldn't read too much into that. The team is busy with multiple platform launches, so time is likely limited.

[psikofunkster]

Yep, definitely much longer this time, all this makes me suspicious...

[Deadrekt]

running the 2602 beta firmware, intel default all settings, my vcore on the 13900ks goes to 1.474v in desktop, playing a new game throne and liberty, I am now starting to get EXCEPTION_ACCESS_VIOLATIONs similar to what I used to get with diablo 4. This is a brand new 13900ks, anyone else?

[stop_pretenfing]

Is there an ETA? How low they usually wait to release stable version? Im on 0x129 with z790-a gaming wifi II

[Gessler]

Usually Beta is followed by final version within a week's time. Obviously we're way past that now so this is certainly unusual.

Probably cuz they're all caught up in the Z890 launch cycle.

[inge70]

The current BETA with microcode 0x12B is stable. At least on my motherboard everything works as it should.

If you need the current microcode, you will have to install the BETA.

I don't expect any changes/adjustments to be made here and that the BETA status will be converted to FINAL at some point without changing the update itself. Asus will simply remove the BETA flag at some point. That's how it was with the last BETAs.

[darsusdj]

Hi all, today for ROG MAXIMUS Z790 APEX ENCORE the bios has been updated to 1703 (no beta) from the 1602 (beta) with the same description (microcode 0x12B), I don't know if the new bios has new internal changes. I'll try this one with my 14900k.

[inge70]

It is possible that a few "cosmetic" changes were made that do not require additional mention in the notes for a new version number to be used.
Because it seems that the Final has become a bit smaller. The last Final 1503 and the 1602 BETA were 13.39MB in size.
The Final 1703 is now only 13.35MB.
If there were no differences to the BETA, a new version number would not really make sense, unless Asus thought that because so many people are complaining that there is only BETA, they would set a new version number and make it Final by chance.
Unfortunately, only Asus itself knows that.