Asus Rog Crosshair Gene x670e: memory context restore weird problem

[InGrifoVeritas]

Hi all.
I don't know if this is the right section, so I apologize if not
My Build:
- MOBO: Asus Rog Crosshair Gene x670e with latest Bios (version 2007, date 2024/04/18);
- CPU: AMD Ryzen 7 7800x3D
- DDR5: 32 Gb RAM G-Skill Trident Z5 Neo RGB (A-Die) with EXPO 6000 Mhz CL30

Problem description:
with EXPO profile enabled in Bios, even if memory context restore is set to "enabled" (and power down mode too), this does not speed up the post time: I clearly can see, from the leds on the mobo Q-Code display, that the ram retraining is done anyway.
No matter if I set EXPO I, EXPO II or EXPO TWEAKED; and what's more, the problem appeared also with previous Bios versions

BUT:
If I disable EXPO by setting DDR5 values manually (and I've done so, overclocking my ram till 6400 Mhz CL30), in this case (JUST in this case) setting memory context restore to "enable" speeds up the post time .. but the problem is that I don't want to stay so long with the ram oc, 'cause I noticed some random instability when gaming.

.. and this happens regardless if I enable tweaks on the cpu (default parameters or pbo + c.o. .. it's the same)

How to figure out why this behaviour? How can I make "memory context restore enable" work simply by enabling EXPO on my DDR5?

thanks in advance

[Silent_Scone]

Hi @InGrifoVeritas 

Does the Q-CODE reader get stuck on a specific code for some time? Perhaps if you take a video of the POST process.

[InGrifoVeritas]

Ok, first of all.. 

imo the q-code remains quite a while on 9C code before post.. 

.. but yesterday I found (quite randomly to be honest) a possible workaround.

not a proper solution, but still enough so that I don't become an elderly man while I'm waiting for the boot screen 🙂

in the bios boot options I noticed that fastboot setting was set to "enable"  .. and although it didn't make any sense to me, I set it to "disable", just to see what it would happen.. then I saved and reboot .. and now the startup time has shortened by about 40 seconds!

Yes, the expected behaviour normally should be the opposite if "fastboot disable" means what it describes .. but that setting did the trick

Don't ask me why, I really don't know