LED remains stuck during warm restart process.
LED remains stuck during warm restart process.
I recently assembled my first AM5 setup, enhancing MB, CPU, and RAM. All recent components: - Asus TUF Gaming B650-PLUS - Kingston DDR5 6000 CL30 KF560C30BBEK2-32 (2x16 GB kit) EXPO certified. Installed on MB's QVL. - 7800X3D Windows 11 latest version with updates. Latest AMD Adrenalin and chipset drivers, current BIOS v3222. Previous components: Corsair Rm750x PSU, two M.2 SSDs (Gen4). GPU Powercolor RX6800XT Red Devil, Cooler Noctua NH-D15 with extra fan. These parts functioned well compared to my old B550-PLUS and 5700X. Initial configuration was smooth, no crashes or BSODs, and I even played a bit of game without problems. I also completed benchmarks such as 3DMark CPU Profile, TimeSpy Extreme, Cinebench r23 & 2004—everything ran without issues. I learned that enabling Memory Context Restore could speed up POST times, so I activated it plus turned on Power Down. EXPO remained enabled. One day I ran Cinebench r23 (single-core) and then restarted; it froze on DRAM LED. I reset the system, tried multiple memory stick combinations, and even swapped them around. Occasionally it would boot but then fail. After several attempts, I disabled Memory Context Restore and left Power Down auto. Now it keeps rebooting each time. The main question is: is there a problem? Memory Context Restore should be safe at Auto by default, right? And since RAM is set to JEDEC, why doesn’t it boot properly? What exactly does Auto mean here? I came across an old discussion where someone faced a similar issue with a faulty CPU. They decided to change parts but couldn’t afford new tests and needed advice. Could you help identify what might be wrong? I’m hoping to pinpoint the problem without buying many new items. Thanks ahead.
Memory context restoration retrieves the stable previous configurations it detected while training. On remains active for loading, Auto initiates loading unless a problem arises (some boards handle this differently, like skipping settings when XMP is enabled). Using Auto will reinitialize settings if they weren't deemed reliable during POST.
Everyone, the update looks solid now. I turned off MCR on both sites in BIOS settings, and it works well once it boots stable—last night I ran TM5 without any issues. During some unexpected warm restarts, memory training might drop and enter failsafe mode as per BIOS. I’m switching to EXPO II mode now because it locks more values in place instead of letting Auto adjust. On ZenTimings, the tRDWR numbers vary between sticks—one is 21 and the other 22.
Update on the situation: The problem remains unresolved after adjusting MCR settings in both BIOS configurations. It still doesn’t boot after a random warm reboot. Initially, the system lights up DRAM LED, then CPU LED, but eventually it stays stuck on DRAM LED indefinitely. Sometimes it fails the first POST and retries using JEDEC timings. In BIOS, EXPO is enabled, yet Windows Zentimings shows 4800 MHz. After rebooting from that state, it cycles through DRAM and CPU LEDs repeatedly until a forced power-off button is pressed. I recently installed the latest Asus BIOS (v3263), which includes new DDR Training settings like "DDR Training Runtime Reduction" that auto-activates by default. I disabled that feature too, yet the issue persists. The training process on JEDEC is significantly slower—about 1-2 minutes compared to 15-20 seconds in EXPO.