September 25th Update:
Beta BIOS Links (microcode 0x12B)
Note: Some pages may not have propagated, please check back later
- 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:
- 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.
______________________________
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.
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
Ok as a follow up to my issue of getting above 1.55 VIDs despite updating to 0x129, I've found that my TVB settings have changed following the update, this is what they look like now:
And this was before the update (BIOS 1301, also at default):
The temp/clockspeed bins have disappeared and TVB Voltage Optimization is now set to Auto as opposed to Enabled previously (though it says default is enabled).
Is this supposed to be right? How do your TVB settings look following the update?
Leave those settings. TVB settings are enabled by default using Intel Default profile as this setting is needed to enforce Intel's voltage cap. Depending on the CPU, you may still see the CPU VID request above 1.55v, but the Vcore (see HWINFO Nuvoton section) should not exceed 1.55v (die sense).
For example using a static voltage of 1.6v in XTU
Apex Encore 1503 [ Intel Default - Extreme] BIOS Defaults
Apex Encore 1503 [ Intel Default - Extreme] TVB Settings Disabled
