MSI X870E EDGE Ti WiFi stuck on code 00 with red/orange LEDs after power loss

juanka1815e502f1

juanka1815e502f1

New member
Joined
Dec 4, 2025
Messages
7
Hi everyone,
I’m having a strange issue with my new build and I’ve seen many people on Reddit reporting something similar, but without a reliable solution.
I have an MSI X870E EDGE Ti WiFi, G.Skill Trident Z Royal Neo 6000 (6000J2836G16GX2), and a Ryzen 9800X3D.

The system works perfectly once it manages to boot. I’ve been playing several games with no issues at all.
The problem only happens when I completely remove power from the PC (unplug the power cord).

When I plug it back in and try to start it, the motherboard gets stuck with red and orange LEDs on, showing error code 00.
I’ve tried booting with one stick of RAM, with both, and even with none — the problem remains. It stays stuck on code 00 and never posts.

The only way to fix it is pressing the Clear CMOS button on the back of the motherboard. After that, it boots normally with default settings, but I have to re-enable EXPO and X3D support every time.

Even if I leave the memory without EXPO enabled, the issue comes back as soon as I unplug the system from the wall and try to boot again.

Has anyone found a real solution for this? It seems many users are experiencing the same behavior but there’s no clear answer.
Thanks!
 
Sort by date Sort by votes
With EXPO enabled you need to set Memory Context Restore and Power Down to enabled. This way your system will not train memory each time. With these settings enabled it will by default retrain every 30 days.
 
Upvote 0 Downvote
ericj159802e9 said:
With EXPO enabled you need to set Memory Context Restore and Power Down to enabled. This way your system will not train memory each time. With these settings enabled it will by default retrain every 30 days.
Click to expand...
Thanks for the suggestion!
I actually tried enabling Memory Context Restore (MCR) before, but the problem still happened whenever the system was completely unplugged from the wall. I hadn’t tried enabling Power Down together with MCR though.
I’ll enable both: Memory Context Restore + Power Down and test again.
If this prevents the motherboard from getting stuck on code 00 after losing power, that would finally solve my issue.

I’ll report back with the results. Thanks again for the help!
 
Upvote 0 Downvote
uranus said:
Do you see the debug code 15 (memory training) before gets stuck at 00?
Click to expand...
I don’t see code 15 at all.
As soon as I power the system back on after unplugging it from the wall, it immediately goes to code 00 with the red and orange LEDs on. It never shows 15 or any other memory-training codes.

It looks like it gets stuck instantly before even attempting memory training.
 
Upvote 0 Downvote
juanka1815e502f1 said:
It looks like it gets stuck instantly before even attempting memory training.
Click to expand...
I have no idea what the problem is. :( Could it be the power supply?
I'd also try using Optimized Performance Profile instead of EXPO. Then I'd lower the CPU VDDIO Voltage to 1.25V (if it's higher).
MSI_Overclocking_DRAM-1.png

MSI_Overclocking_DRAM-2.png
 
Upvote 0 Downvote
I finally found the cause of the issue.

It was not related to EXPO or memory training after all. The problem was caused by a PCIe remote power-on card I had installed to turn on the PC remotely.

Apparently the device was sending a power-on signal too early during cold boot after AC power loss, which caused the motherboard to hang at code 00 before proper initialization.

After removing the PCIe card, the system boots normally every time, even after completely unplugging the PSU.

So it seems these AM5/MSI systems are very sensitive during early startup initialization when certain PCIe devices interfere with the power-on sequence.

Thanks everyone for the help!
 
Upvote 0 Downvote
ericj159802e9 said:
How did you come up with the idea to check the PCIx remote power-on card?
Click to expand...
At first I suspected RAM training or EXPO because many AM5 systems seem sensitive during cold boot.

But then I noticed something important: once the system finally booted, it was completely stable. Gaming, stress tests, everything worked perfectly. The issue only happened after total AC power loss.

That made me think it was probably something related to the very early startup sequence rather than RAM stability itself.

I started disconnecting non-essential hardware one by one, and after removing the PCIe remote power-on card, the problem disappeared completely. After that, the motherboard started posting normally every time, even after unplugging the PSU.

So the PCIe card was somehow interfering with the initial power-on process before the board could properly initialize.
 
Upvote 0 Downvote
Back
Top