z890 Steel Legend RAM issue

Hello everyone,

Got at z890 Steel Legend that used to work well with a compatible set of QVL-approved RAM for almost a whole year without problems. Now it can't work without running at JEDEC 4800, everything else would cause freezes and random BSOD at all time.

Thanks for your help.

Edited by Xaltar - 17 hours 60 minutes ago at 12:27pm

Xaltar wrote: Have you made any changes to the system that could have caused the issue? BIOS updates, upgrades, added more RAM etc? Do you remember when the issue started?

Zero changes before the first problem appeared actually. No hardware and no software.
My system just started freezing after coming back from sleep with an orange DRAM LED, every single time. Then I ended up putting the BIOS defaults, reflashing the same 3.24 BIOS, and finally using BIOS flashback.
Flashback solved the sleep issues, but since the BIOS defaults, it's non stop BSOD and freezes everywhere in XMP or 200S Boost with or without XMP, even with BIOS flashback + multiple reboots between those changes to make sure they are isolated. It has been a whole month now.

Xaltar wrote: Have you tried removing and reseating the RAM? Also, if you are using 2 modules make sure the RAM is installed in slots A2 and B2 or if a single stick thein in slot A2. The A1 and B1 slots exist to support 4 modules and don't work well if used with only 1 or 2 modules installed in the system.

Thanks for the suggestion, yes I did only boot with one stick and this works with XMP, then adding a second after a reboot also works. Then after a few reboots BSOD right away.
It seems training is messed up, the values trained for one sticks works for two sticks, but then when somehow it trains again with 2 sticks, it causes problems.

I also tried to freeze all the values that the BIOS trained to, but it seems some values are in the NVRAM only and change across reboots and trainings and fully destroys my system (I am even afraid those freezes killed my CPU, as the 200S boost freezes are very recent). BIOS training seems broken, not sure if only in the last update or previous ones too.

For A2/B2, yes, this has always been respected, thank you for the reminder!