Transferred the machine up two levels, but it fails to power on. The motherboard shows a "Detect Memory" alert.
Transferred the machine up two levels, but it fails to power on. The motherboard shows a "Detect Memory" alert.
I relocated my computer two levels down to a new apartment. Connected my laptop and noticed an odd message on the motherboard screen: "Detect Memory." That seemed strange, so I restarted it several times without success. I tested one stick at a time across all four slots, but nothing changed. I also tried different DDR5 modules, one at a time in each slot. Still, no improvement. I’m unsure what to do next. The motherboard model is a ROG Maximus Z690 Extreme Glacial, paired with a G.Skill 32GB (two 16GB) DDR5 6000MHz CL36 Trident Z5 RGB Silver kit.
Take your CPU out of the socket and reattach it properly. It's likely that movement caused connections to become loose.
I’ll note that most Z690 DDR5 boards will remain in "Detect Memory" (POST code 55) for a while during memory training. I’ve observed this on my Unify-X before, though it’s not very common for that board to stay there for such a long time. This suggests you might not be allowing enough time for the training process. I’m not claiming it’s certain, but since you had to disconnect the system, it will need to relearn memory. DDR5 training can take a long time, so this is plausible. Occasionally it happens, but usually not. The most frequent issue when a CPU mount fails is memory errors, as the memory subsystem—especially in DDR5—is most likely to experience signal integrity problems. This can cause memory channels to vanish or result in a POST failure with no memory training confirmation.
Consider leaving it on for a while to observe any changes. I haven't experienced this problem before when unplugging the unit, so I'm not very confident. However, the OLED screen indicates "detect memory," which might be relevant. It's possible it doesn't matter, but since it's a fullboard waterblock, I'm skeptical it could have affected the CPU stability. Spoiler: it probably didn't.
It has been running since the last update, approximately 20 minutes. The switches are currently off.