Asus rog x670e hero shows code "0d" after system restart

[moe_lvr_666]

Hello everyone,

I've been encountering a recurring issue with my PC recently. Sometimes, after the system has been on for a while and I try to restart it, I get error code "0d" displayed on my motherboard. To resolve this and boot up correctly, I have to perform a hard shutdown, after which the system boots up normally.

This problem started occurring recently, more than a year and a half after I initially built the system. It coincided with upgrades including new Corsair QX fans and switching from an ASUS Strix 3090 to an ASUS TUF 4070 Ti Super GPU.

Here's what I've tried so far to resolve the issue:

- Tested different BIOS versions
- Replaced CPU with Ryzen 9 7900X3D
- Replaced motherboard to the same model  ROG X670E Hero
- Installed a new AIO cooler, Corsair iCUE LINK H150i
- Tested with different RAM kits, Corsair Vengeance 6000MHz 2x16GB

My PC specifications are as follows:

- Motherboard: Asus ROG X670E Hero
- CPU: Previously Ryzen 7 7800X3D, now Ryzen 9 7900X3D
- GPU: ASUS TUF 4070 Ti Super 16GB
- PSU: Corsair RM-1200X SHiFT
- RAM: Corsair Vengeance 5200MHz 2x16GB (32GB total)
- Case: Corsair 5000X RGB
- Fans and CPU Cooler: Corsair iCUE LINK ecosystem
- Storage: 2x Samsung 990 Pro 1TB, 1x Samsung 980 Pro 2TB

Any assistance you can provide would be greatly appreciated!

[polyh3dron]

Looks like I need to try the new 2804 BIOS.. Anyone else given it a shot yet?

[ReZz1DenT]

Yes, I installed a new BIOS, so far I haven't encountered any errors

[WhiskeyEcho]

All I see on ASUS' site is BIOS ver 2204 as the latest that came out 08/05/24

[ydeng]

same here.

[WhiskeyEcho]

I've cleared the CMOS, enabled memory context restore(multiple instances), disabled power down(there are multiple instances), enabled DOCP I. PC seems to run fine until I go to start a game (Fortnite specifically...my kids plays:) then I get "unexpected_krnl_mode_trap" as the game is initializing...every.single.time.

[lSonicXl]

I finally found the cause of it in my case.
MSI Afterburner 3.6.6 is to blame for it. As soon as it is installed I am getting the 0d errors on reboots.
Running now since several hours with many test reboots v3.6.5 of Afterburner and the error is gone.

[polyh3dron]

I had been running MSI Afterburner 3.6.5 the whole time and was still getting the 0d restart errors. Uninstalled it, and they persist. Installed BIOS 2302 (which fixes the Crosshair Extreme OLED issue) and the 0d errors still persist.

[mahava]

I also have this weird issue, it happened after 1905 BIOS, it happens for example if i restart for windows update or chipset drivers, if i reset the computer will boot fine but only see one stick of ram, reboot again is fine and will se all sticks, 

Happened 3 times, expo disabled for now , i switched places of the ram but it is always #4 that doesent detect on first boot on error

Else computer is 100% stable, no crashes etc 

7800x3d CPU and Corsair CMH32GX5M2B6000Z30K

[Javi7269]

For those of you that have the 0d error code try this...

Unscrew your CPU heatsink a little bit from the support brackets beside the CPU socket.

Don´t let the bracket screws go to the end, or, screw them to the end, and then, turn counterclockwise 1 and a half or 2 complete turns. Just a little bit to release pressure from the CPU socket.

I had this same problem a few weeks ago. First I thought that the problem was Armoury Crate software, but this was not the problem. I unnistalled Armoury Crate anyways, but recently I installed a new Ryzen 9900X on my Hero X670 motherboard, and the problem came back again. Just releasing a little bit of pressure from the CPU socket did the trick. I was able to replicate the problem a few times.

It´s worth to try bucause this 0d error code is very annoying.

[polyh3dron]

Yeah I had a feeling it could be this. When I drop in my 7950X3D I am going to pay close attention to this.