Increased Vcore After Microcode BIOS Update

[Akheem]

I have a 13700K in an Asus PRIME Z790-P WIFI.

Before any updates to my system were made, I ran the latest Cinebench multi-core stress test which resulted in a max 1.45VCore maximum with a 1.4Vcore average.

I updated the BIOS to v1663 with the Microcode fix and noticed that some of the default settings were changed; i.e. Current Excursion Protection (CEP) was changed from Auto to Enabled.

I ran the Cinebench multi-core stress test again which resulted in a 1.54Vcore max and a 1.5Vcore average.

Intel recommends not to push voltage beyond 1.4V, but here it is pushing my system 0.1V beyond it's own recommendation by default.

Has something gone wrong? I do not and have not overclocked this processor.

Edit: with the help of a contributor from this post, I rolled back my BIOS update to 1661 but now my Vcore maximums are going to 1.590v.

https://www.intel.com/content/www/us/en/gaming/resources/how-to-overclock.html

https://www.asus.com/ca-en/motherboards-components/motherboards/prime/prime-z790-p-wifi/helpdesk_bios?model2Name=PRIME-Z790-P-WIFI

https://community.intel.com/t5/Processors/June-2024-Guidance-regarding-Intel-Core-13th-and-14th-Gen-K-KF/m-p/1607807

[SmartOne_2000]

Why use a non-k BIOS code for a K-based processor???

"The new BIOS includes Intel microcode 0x129 and adjusts the factory default settings for the non-K processors, enhancing the stability of Intel Core 13th and 14th gen desktop processors"

I almost made this mistake on my z690 based 13900K.

[Akheem]

Good find. I got baited. Working on rolling this back now. Thank you.

[SmartOne_2000]

No worries and an easy mistake to make, considering what's at stake. I  posted this just as I saw your reply.

[Akheem]

Thanks, but that post confused me again. The Asus website has these three BIOS microcode updates available right now:

1663 - microcode 0x129 non-k processors (released Aug 14, 2024)

1662 - BETA microcode 0x129 update for non-k processors (released Aug 9, 2024)

1661 - microcode 0x129 update for unspecified processors (released Jul 10, 2024)

When I first posted, I was on 1663. I rolled back to 1661 because of your initial reply. But now it sounds like Asus doesn't even recommend going to 1661 for K-skew processors?

Would appreciate it if you could clarify Thank you.

[SmartOne_2000]

As of today, the current 0x129 microcode in BETA form, is for non-k processors ONLY. Do not install any 0x129 based bios yet ... until it says its meant for k-based processors. 1661 - 1663 codes are for non-k processors only.

What I've done in the meant time for my 13900K is to limit SVID to 1550mV (1.55v) as recommended by the Intel guy on this forum. Its default value was AUTO. Not sure what voltage it was.

[Akheem]

Thank you!

[SmartOne_2000]

My sincerest apologies, @Akheem . It seems I fed you some bad info unfortunately. The 0x129 microcode update is for ALL 13th/14th gen processors, regardless of variants. I mistakenly told you it was for non-k processors. I misunderstood what Asus said on its bios page. My sincerest apologies once again. If you haven't upgraded yet, you may want to do so now, since most code is no longer in beta form.

[Akheem]

Thanks for taking the time to come back and correct the error. It's a shame this post has been read nearly 1,000 times already. Hopefully anyone else who shows up won't make the same mistake.

[Akheem · Accepted solution]

I found the solution with the help of a lot of other people over the internet and reading the BIOS manual for my motherboard:

Fix 1: The newest BIOS with the microcode update for my motherboard is set to use Intel's Default Profile. This profile sets SVID Behavior = Intel's Fail Safe. According to this Asus post, Fail Safe is only for CPUs already suffering instability that can only be fixed by a high Vcore. After setting SVID Behavior to Typical, my Vcore maxed out to ~1.35V under a Cinebench load which is much better. The fact that Intel's Fail Safe is enabled by default feels negligent. Users who don't know how to monitor these sensors won't see the affects of this setting until it is much too late.

Fix 2: I also noticed my E-cores were down-clocking under-load. I'm not sure when this started happening but to fix this I had to turn CEP (Current Excursion Protection) to Disabled. Keep in mind, Intel's June 2024 Guidance regarding Intel Core 13th and 14th Gen K/KF/KS instability reports say to leave this Enabled. To address the reduction in performance caused by this, MSI (another motherboard manufacturer) is rolling out BIOS that allow their users to turn this off. You'll need to decide if this is right for you.

I made a number of other changes to the BIOS to fit my needs but these were the biggest two causing issues for me.