Rebooting issue with code “0d” in Asus Strix X870E MB

[TIG]

I have a strange rebooting issue in my newly purchased PC. When I turn on the system, it starts normal and without issue. Once I need to reboot it “restart” for any reason like update windows or download a file …. etc, my asus Rog Strix X870E-E Motherboard shows code “0d” and stuck without booting and even bios cannot be reachable. In this case, I need to force shutdown and restart again in which everything will be fine. If I want again to restart it from windows, the same thing will happen.

System specs:
Ryzen 9 9950x, 64GB Ram
Asus Rog Strix X870E-E gaming wifi
Asus Tuf RTX 4090
Windows 11 in M.2 NVMe

Things I made with no improvement:
* Bios update.
* Bios at default settings.
* Windows 11 installed
* Asus Armoury Crate deleted.
* RAM sticks removed and install back in slots 2 and 4.

By the way, once the system starts, it is very stable even under stress conditions.

Any advice for such strange reboot behavior??

Thanks

***********************************************************************************************

Update….. problem solved “temporary …!!!”

After scanning most of the possible reasons at least based on my level of knowledge in this regard, I found the situation must be around the DDR5 DIMM “RAM slots”. Asus Rog Strix X870E-E motherboard has 4 RAM slots. Initially, slot 2 and 4 were engaged with 32GB RAM each “total 64 GB RAM”.

I changed the RAM positions from slot 2 and 4 to 1 and 3 and no progress. Code “0d” came just immediately after the first restart from Windows and rebooting failed.

I changed to new 32x2 GB RAMs but with no progress. Code “0d” came just immediately after the first restart from Windows and rebooting failed.

Then a crazy idea came to engage all the 4 slots with 32x4 GB RAMs “total 128 GB RAM”.

OK, I know this would be crazy but just let us try. After having the first PC turn on, the motherboard took about 10 minutes to boot and initialize RAMs “remember; all the 4 slots are engaged now”. At this time; a new code came “15” which is the pre-memory system initializing code. After about 10 minutes, the system booted smoothly. Now, it is the time to start the test. I restated the PC from Windows to see if code “0d” will come again. Guess what… the system rebooted very smoothly without “0d”. I repeated the restart process from Windows every 15 minutes and rebooting was just perfect. The most important observation is that: the motherboard Q-Code LED behaved totally differently and quickly with 4 slots RAM engagement.

Since more than 4 hours with PC restarting every 15 minutes, code “0d” just disappeared and the rebooting issue resolved.

I do not know what exactly happened and why motherboard behaved differently with 4 slots RAM. I know 128 GB RAM is just a crazy number from gaming “might be great for content creation”, however, the situation is resolved.

Having that said, still it might not be worth it to engage 4 slots RAM to resolve the rebooting issue in this “high end… !!!” motherboard. I believe ASUS must look into this issue and provide more robust solution.

Tig

[_I_]

reset bios to defaults using the jumper

try enabling xmp, then bring the ram speed down one bump

[TIG]

Początkowo opublikowane przez _I_:

reset bios to defaults using the jumper

try enabling xmp, then bring the ram speed down one bump

Done already with no improvement.

[ˢᵈˣ FatCat]

Turn off fast startup

[Bad 💀 Motha]

Re-flash the latest bios update

[A&A]

"Reserved for future AMI SEC error codes"...
How do I know? Check your manual.

[TIG]

Początkowo opublikowane przez A&A:

"Reserved for future AMI SEC error codes"...
How do I know? Check your manual.

Exactly, I found this in the manual.
furthermore, the issue seems common for this code and Asus must do something for it. This motherboard is suppose to be high end MB and should be at that level.

[ˢᵈˣ FatCat]

there is no Bend pint right, just saying, could be that

[Phénomènes Mystiques]

Your fatal mistake was moving to Win11 way too early.

[TIG]

Początkowo opublikowane przez WinterSolstice:

Your fatal mistake was moving to Win11 way too early. :csd2smile::badluck:

😄 this strange behavior started when I had Windows 10 a month ago. So, seems Win 10 or 11 does not matter.

[Phénomènes Mystiques]

Początkowo opublikowane przez TIG:

Początkowo opublikowane przez WinterSolstice:

Your fatal mistake was moving to Win11 way too early.

😄 this strange behavior started when I had Windows 10 a month ago. So, seems Win 10 or 11 does not matter.

Okay then, new boards and CPU series that are adopted too early (i.e. YOU) will see these types of faults and the recourse to fix is by re-flashing the BIOS OR downgrading the BIOS if you can as some you cannot, read the prerequisites and stay far from BETA BIOS's.

[TIG]

Początkowo opublikowane przez ˢᵈˣ FatCat:

there is no Bend pint right, just saying, could be that

I do not think so. The system is very stable after startup and can stay under stress and load for hours.

[TIG]

Początkowo opublikowane przez WinterSolstice:

Początkowo opublikowane przez TIG:

😄 this strange behavior started when I had Windows 10 a month ago. So, seems Win 10 or 11 does not matter.

Okay then, new boards and CPU series that are adopted too early (i.e. YOU) will see these types of faults and the recourse to fix is by re-flashing the BIOS. :csd2smile:

Done already with no improvement.

[Phénomènes Mystiques]

The board might be having issues booting from M.2 - some do even when they are rated as being capable.

[ˢᵈˣ FatCat]

maybe it just simple problem like maybe you overtight your CPU cooler, my friend slot RAM 1-2 is broken because he overtight the screw

[Phénomènes Mystiques]

Początkowo opublikowane przez ˢᵈˣ FatCat:

maybe it just simple problem like maybe you overtight your CPU cooler, my friend slot RAM 1-2 is broken because he overtight the screw

Screws should always be snug unless specified by a torque rating.