I've been having some trouble with my Asus ROG Crosshair X670E Extreme. In short, the problem is that the Extreme gets stuck in a "non-boot" loop at times, where the LiveDash OLED permanently reads "Memory Test", Q-LEDs often start out with the yellow (memory) bit lit up but after 5-10+ minutes can move to the red (CPU) indicator. The Q-Codes displayed tend to stay for a long time and range from 15 to 1A and possibly others. There is no monitor video output as of yet, and when its in this loop it never makes it to the BIOS et al. The behavior will persist even after turning off the power by holding down the mobo power button or disabling the mobo power button; after restoring the PSU power and pressing the power button again it begins the same process as above. Its worth noting that the "freeze/loop" described above seems to always happen if the PC crashed to reboot during stability testing (using AIDA64, YCruncher , OCCT or other tools ), will sometimes happen after manually instructing the OS (for the sake of it I've been using Windows 11 during the testing phase, but my primary OS of choice is Linux) to shut down and/or reboot. Outside of crash-to-reboot seeming to nearly always provoke this behavior, the chance of the 'memory test' freezing is variable for both of them, but seems less likely (but not impossible) to happen with an ordered reboot vs a shutdown.
The only thing that I've found that can reliably resolve the issue is to use the ClearCMOS button on the rear I/O. Upon pressing it (which shows the momentary disruption in board lighting confirming its usage) and then using the mobo power buttons, the system boots "normally" more or less including activating the monitor output (currently using the iGPU) and displaying the "first time boot up, press F1 to go to BIOS" style message. Going into the BIOS as normal , all the defaults have been activated. Typically, I simply enable the EXPO1 RAM setting, change the QFan option for CPU_FAN from the Standard curve to Turbo, and then save and restart, allowing me to reach the OS. Things function seemingly normally until there's another crash and/or shutdown/reboot which restarts the PC, where the possibility for the Memory Test loop/freeze returns.
--Hardware specs
AMD 7950X3D CPU
Asus Crosshair X670E Extreme mobo w/ 2204 BIOS
Gskill 64GB DDR5 6000mhz CL30-36-36-96 1.4V EXPO compatible RAM
Temporarily using iGPU DisplayPort USB-C connection > HDMI adapter > Monitor . Discreet GPU to be added later when system is stable and ready for daily use.
Samsung 990 PRO 2TB, 980 PRO 2TB both in ROG GEN.Z2 module + SATA 870 EVO 2TB SSDs.
--
I am unsure if the problem started when either A) I replaced what I would discover was a bad stick of RAM, RMAing my old kit and replacing it with an identical one that unlike the previous passed OCCT Memory and AIDA64 Stress Test Memory when the old kit errored immediately or B) after I updated the mobo firmware. I know it had a much older firmware when I started the build, updated to 2007 before anything, and then 2124 and 2204 when they arrived. I know the issue is happening on 2204, and I think it happened on 2124, don't remember 2007 or not.
Searching for Asus ROG X670E mobos being "stuck on Memory Test" or something similar that won't boot shows a variety of users with different circumstances, from bad RAM, CPU issues, to an incomplete (?) motherboard BIOS update that required swapping in a new RAM kit to propagate through etc. Some of these discussions, on the ROG forums and elsewhere are more recent and others go back to last year so I wanted to check given the current understanding of possible issues, compatibility and the like. Thanks
P.S. - Unrelated, but I'm sure you know about this, but please fix the "TEST NVRAM" OLED display if possible. When everything is working properly and boots normally, the OLED displays TEST NVRAM ever since the last couple BIOS updates; it seems to b the case for others as well. I hear that using Armory Crate in Windows is the way to specifically fix/control it, but I'd greatly prefer for the LiveDash OLED to function independently at the BIOS/UEFI level and of course, can interact with it on non-Windows OSes like Linux. Some seem to suggest the latest Beta BIOS fixes the issue so hopefully that's the case. Just thought i'd mention.
