Crash w/ Formula Z690 New BIOS 3501 - Setting new equivalent of CPU Core/Cache Voltage for undervolt

[Spindlwood]

** UPDATE **

I realize / conclude that my post is in the same vein as the general discussion on overclocking instability with BIOS 3501. Take it as just one more piece of evidence that voltage changes that were stable on a previous BIOS version are no longer stable with the new BIOS.

******************

After updating to the 3501 bios, I ran with default settings for a couple of days. Today, I set XMP 1 (DDR5-4800MHz 40-40-40-77) and ran it successfully (yeah, I know, awful ram, but it was all that was available two plus years ago and I was lucky to get it).

Next, I looked to restore the setting I had for CPU Core/Cache Voltage in the old bios: Adaptive => Offset (-) => Offset Voltage (0.05)

I discovered that Asus, in the new bios, had split this setting into 3 new settings: Actual VRM Core Voltage, Global Core SVID Voltage, and Cache SVID Voltage.

I read that the new equivalent of CPU Core/Cache Voltage was to set Global Core SVID Voltage and Cache SVID Voltage. I changed both of these to Adaptive => Offset (-) => Offset Voltage (0.05) and rebooted. I was met with a BSOD which didn't reboot. When I tried rebooting, it hung at the logo. I rebooted again and it gave me a "repairing" message that kind of freaked me out.

So, I'm back to "auto" for these two settings and here to ask advice on how to do a small undervolt of 0.05v in order to reduce my temps a bit. I'm not running games, but during certain Premiere Pro renderings, it was getting too hot.

Thanks for your help.

In case it matters, I've got a Formula z690 board which shows Rev 1.xx in CPU-Z.

[airborne3406y]

I had nothing but problems with this update. you name it and I had it. tried manual OC. Ai OC. Stock. RAM issues as well. It even crashed when I was rolling back to 3401 luckily it hadnt started writing when it crashed. Got rolled back to 3401 and no issues. 

[Spindlwood]

Thanks for the encouragement to rollback to 3401. I've been waiting for the next crash to decide which version to rollback to. One user posted on the other thread that ver  2802 was their last stable release.