The thing that bugs me about MCR is if its saved to a bios profile, then load another bios profile (with MCR on when it was saved) it still takes a couple minutes to boot with the chosen bios profile despite the fact that the bios profile is already saved (with the MSR on) . So shouldn't the motherboard be remembering the precise settings for the RAM from the bios profile in the first place & that of course includes MCR being on? I've seen this problem on an Asrock, MSI & even a Gigabyte AM5 boards I have here despite agesa updates for several months already. There is still work to be done to fix these bios problems with Zen 4.
Cold boots can't possibly risk that, because you never know if the RAM has been changed.
Ask the MB makers, it wasn't in the launch BIOS until people complained about 1min boot times lol. The struggles and dial up and waiting 10 minutes for windows to load was a real thing. Could go make. A sandwich and come back.
I'm just about to boot up my first AM5 system (not a clients, my own) and poke these things. I'll see what i can spot with boot times since i have a few kits of ram on hand today.
Been able to replicate the traditional slow boot problem with way too fast RAM for AM5, but that's half the point of trying to poke the bear
Stock settings works fine every time, but using EXPO with RAM guaranteed to push the board to it's limits was failing, often taking a few cycles to do before booting at JEDEC (4800?)
. Hearing the CPU fan spin up to 100,000RPM was a clear indicator of when the failed boots happend
DDR5 8000 on the Taichi Cararra
Running lower Infinity fabric speeds didn't help it booting - EXPO manually set 1.30vsoc and Fclk to 2000, as well.
Trying new BIOS now...
7600 works just fine, 8000 does the repeated failed boots.
I recorded videos, but had a dog running over my feet so it's more for me to use as a timer.
7600: 18 seconds
7800: same, 18ish seconds
8000: 120 seconds, BIOS booted at JEDEC
Lowering infinity fabric (FCLK) has zero benefit to the boot times, If the DRAM speed is too high it just fails. This will be due to whatever secondary and tertiary timings the boards are running and why BIOS updates make such a difference.
TL;DR: The CPU and board can both simply have limits you may be reaching, in MCLK or UCLK. BIOS updates may fix it, but rather than fight it just tune in the highest that boots reliably, including cold boots.