Another slow POST with X670-E-E

[PeterW_R]

I also suffer from this recurrent issue, my X670-E-E Gaming motherboard with AMD 7900X and Corsair 64GB DDR5 6000Mhz 30-36-36 memory  takes a minute to POST, then it boots normally. This happens in the old 2023 I was running and also on the newest non-beta bios 2308. Memory Part Number is CMK64GX5M2B6000Z30.

Enabling context restore under memory timing settings fixes this issue, but it is really something that I think should be fixed at once on newer BIOS.

[PeterW_R]

Any input from ASUS team on this?

[achugh]

Hi @PeterW_R since you have a fix available, what else are you looking to solve? The configuration option in BIOS exists to solve this and similar problems which you have correctly used already so I am not able to understand what additional help do you need at this time. Can you please elaborate further? Thank you.

[PeterW_R]

Why is not this setting enabled by default?

[Silent_Scone]

Because bypassing memory training can cause instability if the setting is disabled prior to establishing a baseline for stability. The system doesn't conduct these tests simply for the sake of it. What's electronically stable and what's considered stable once in the OS are quite different. Disabling extended memory training routines by default is counterintuitive.

[PeterW_R]

Then I should re-enable it again? but if I do that, POST times will increase! Do you understand my point that work needs to be done on your side to correct this? it's just not fine to provide a workaround at the expense of system instability.

[Silent_Scone]

No, you simply need to check DRAM stability, if you're not sure on how best to do this - you can ask. You can use Karhu Ram Test or Memtest Pro. Once you've established your overclock is stable, you can enable Context Restore. 

This is fundamentally the same process on many platforms before AM5 and is part and parcel of overclocking and ensuring a DRAM overclock is stable - the only difference with AM5 is that the training routines can take considerable time - this is not down to ASUS.