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

[TIG]

WinterSolstice eredeti hozzászólása:

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

Removed M.2 one by one and all with no improvement 😔

[Phénomènes Mystiques]

TIG eredeti hozzászólása:

WinterSolstice eredeti hozzászólása:

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

Removed M.2 one by one and all with no improvement 😔

When I got the x370 AM4, it had issues a lot of issues and you really do not want to update a BIOS if the system is stable.

What I learned through it all is that you might have to "live with this" issue until the next BIOS update - it can also take 3 - 5 years for board stability on new CPU architectures.

I cannot tell you how many times I had to re-flash, downgrade and upgrade the BIOS for the x370 back in the day but today, the board is completely stable (7.5 years later) and still receiving BIOS improvements.

[TIG]

WinterSolstice eredeti hozzászólása:

TIG eredeti hozzászólása:

Removed M.2 one by one and all with no improvement 😔

When I got the x370 AM4, it had issues a lot of issues and you really do not want to update a BIOS if the system is stable. :badluck:

What I learned through it all is that you might have to "live with this" issue until the next BIOS update - it can also take 3 - 5 years for board stability on new CPU architectures. :chirp:

This is not fair 😔

[Phénomènes Mystiques]

TIG eredeti hozzászólása:

WinterSolstice eredeti hozzászólása:

When I got the x370 AM4, it had issues a lot of issues and you really do not want to update a BIOS if the system is stable.

What I learned through it all is that you might have to "live with this" issue until the next BIOS update - it can also take 3 - 5 years for board stability on new CPU architectures.

This is not fair 😔

Was the system ever truly stable on other BIOS versions or is this an out-of-the-box thing?

[ˢᵈˣ FatCat]

nah man, you think PC artchitect << how do i type that , is that fragile, the worse is maybe the clockspeed not as the advertised one, but not whacky error like that

[Phénomènes Mystiques]

ˢᵈˣ FatCat eredeti hozzászólása:

nah man, you think PC artchitect << how do i type that , is that fragile, the worse is maybe the clockspeed not as the advertised one, but not whacky error like that

One time, the BIOS did something to the XMP and Profile 2.0 was mismatched which caused issues out of nowhere and I had to manually change those timings, then 5 months pass and it does it again, but this time the XMP Profile is proper timed and the system started working again until the next problem appeared - AM5 boards will take at least 3 years to become stable, such as with AM4 which took 3 - 5 years (dependent on MOBO manufacturer) but also depends on the manufacturer sticking with the board but most do support X/Z series boards for a long while (ASRock doesn't play around and still supporting the x370 after 8 years of service).

[TIG]

WinterSolstice eredeti hozzászólása:

TIG eredeti hozzászólása:

This is not fair 😔

Was the system ever truly stable on other BIOS versions or is this an out-of-the-box thing? :csd2smile:

I got this PC before a month. Normally I keep the PC running without shutdown. In the beginning, I had this issue in random once in couple days. I thought it was because Windows 10.

Then, last week, I discovered Asus Rog Strix X870E-E has a strange reboot issue once I restart the PC from Windows. So, whenever I restart it from Window code “0d” should come after the restarting process. Changing from Win 10 to 11 did not resolve the issue.

[Phénomènes Mystiques]

I don't do visual error codes but after looking it up, this is a RAM issue? Seems familiar, so you ran the RAM at stock timings, tried XMP, but have you tried to see if the timings match specifically because one time the board mismatched my timings and Profile's for XMP which was the fault of a BIOS revision, so I would check those timings and if using XMP, to also turn on OC/Performance/Game Mode (or wateva ASUS calls it) for the RAM - some are reporting RAM training error.

[TIG]

WinterSolstice eredeti hozzászólása:

I don't do visual error codes but after looking it up, this is a RAM issue? Seems familiar, so you ran the RAM at stock timings, tried XMP, but have you tried to see if the timings match specifically because one time the board mismatched my timings and Profile's for XMP which was the fault of a BIOS revision, so I would check those timings and if using XMP, to also turn on OC/Performance/Game Mode (or wateva ASUS calls it) for the RAM - some are reporting RAM training error. :chirp:

Thanks for your suggestion.
However, I think I just might figure it out. Just let me confirm it before I let you and all know. It might be crazy but worth to try it till we have ASUS be serious more and resolve the issue through a stable bios.

[Phénomènes Mystiques]

I have done some interesting unconventional solutions in my day, so unless it can kill you or the system, I say, go for it.

[TIG]

WinterSolstice eredeti hozzászólása:

I have done some interesting unconventional solutions in my day, so unless it can kill you or the system, I say, go for it. :hype:

Thanks.
Will back to you soon.

[Corona Scurrae]

TIG eredeti hozzászólása:

A&A eredeti hozzászólása:

"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.

This is why you don't buy ass.

[C1REX]

This error may happen with Memory Context restore on in BIOS.

I would try with this option off (can take a very long time to post) and with expo off.

[TIG]

Thanks all for sharing your thoughts here. I updated above my main discussion. Hope it will be with any benefit at least temporary and looking to ASUS permanent solution.

[C1REX]

TIG eredeti hozzászólása:

Thanks all for sharing your thoughts here. I updated above my main discussion. Hope it will be with any benefit at least temporary and looking to ASUS permanent solution.

By putting more memory you forced your motherbord to retrain the memory. Try turning memory context restore off with 2 memory stick in. There is a good chance it will work after new memory training.