Been running a B650E board with a 7800X3D and 32GB of 6000 CL30 EXPO for a couple months. With Memory Context Restore off, cold POST is around 30-40 seconds and I can live with it. Turned MCR on last week and warm boots are basically instant, cold boots mostly fine too. Problem: every few days it hangs on the DRAM debug light and I have to hold power or hit reset. After that it trains and boots normal.
Is this just the AM5 tax, or is there a combo setting that makes MCR actually reliable? I've seen people mention Power Down Enable has to match, but I haven't messed with it yet. Also on latest BIOS, not some launch-day build.
Yes! This is exactly the rabbit hole I went down. On most AM5 boards MCR and Power Down Enable are linked — if you enable MCR but leave Power Down disabled, you can get those random cold-boot DRAM hangs. Have you tried enabling both MCR and Power Down Enable in the DRAM/AMD CBS section? That fixed my B650 board with a 7600X and 6000 CL30 kit. Also check whether your board has a separate 'Memory Context Restore' under AMD Overclocking vs the CBS menu; sometimes one doesn't apply. And if you're on EXPO, try bumping VSOC a tiny notch or checking that your kit is actually stable with a quick TM5 run. MCR doesn't fix unstable training, it just skips it!
Honestly I just leave MCR off. The 30 seconds annoys me for about a day and then I forget. Had the same occasional DRAM-light hang and decided I'd rather have slow and boring than fast and moody. If you do keep it on, SiliconMoss is right about Power Down Enable — that's the first thing I'd try.
Yeah, that's fair. I mostly care because the PC is in the living room and the cold boot fan ramp plus waiting is noticeable. I'll try MCR + Power Down Enable together and see if it goes a week without a hang. If it still does the DRAM-light thing I'll probably just go back to MCR off and use sleep. Not gonna chase my tail over a few seconds.
I ran MCR on for a while on a B650E + 7800X3D and it was fine until it wasn't. One hang every week or two, always cold boot. What helped me was updating to a newer AGESA BIOS and then clearing CMOS and re-entering settings manually instead of loading an old profile. Could be placebo, but it's been quiet since. Also make sure you're not overclocking the fabric or messing with curves at the same time — too many variables.