cancel
Showing results for 
Search instead for 
Did you mean: 

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

moe_lvr_666
Level 9

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!

RED Team
1,977 Views
146 REPLIES 146

Yes!!! It happened a few times yesterday. I was trying to launch Euro Truck Simulator 2, but the game did not start, so I tried to open the Task Manager, and it was not responding. When I tried to reboot, the system froze and eventually produced a BSOD (unfortunately I didn't write down the error string, but it had POWER in it). I seem to have fixed the issue by rolling back the latest Nvidia driver and the latest cumulative Windows 11 update (I then reinstalled the latest Nvidia driver, so maybe it's the Windows update, but for now I'll refrain from reinstalling it).

Unfortunately, today, after a reboot, I got the 0d error several times and I could boot into the system only after pressing the CMOS button. By the way, I have a Strix X670E-E Gaming-WiFi. As many others, I had a very stable system for a long time, but recently, I started having problems. OCCT does not find any hardware issue, so it's not a CPU or RAM issue. For reference, I use iCUE, MSI Afterburner and have ArmouryCrate installed.

Occasionally I also get the 00 error, which prevents the boot from happening, and it requires to cycle power on the PSU.

I am running now the latest Bios Beta with "Monitoring Software reboot workaround" enabled. So far no 0d errors at least. Could really be the Monitoring Software that is build in iCUE, Armory Crate, L-Connect and so on.

I bought Asus Hero X870e, this 0d error started a few times. I activated this function in the bios "Monitoring Software reboot workaround" and it solved the problem. Why didn't Asus communicate about this problem? Does this affect any performance?

ROG MAXIMUS Z690 HERO + 12900K + XPG 32GB RAM DDR5 6000CL40 + RTX 3080 GALAX HOF + ROG RYUJIN II 360 + LIAN LI XL + CORSAIR HX1000i + M2 SAMSUNG 980 PRO 1TB + M2 SAMSUNG 980 PRO 1TB + SSD SEAGATE 1TB. 😉

I have now 0 issues after activating the option with my PC regarding the restart. The only issue I now ran into is that the PC is not waking up from sleep mode. 

Yeah I’ve had more than once! Very frustrating as the single job of task manager is to help with that, not cause it 🤦‍♂️🤦‍♂️

I hadn’t linked it to the 0d issue though, albeit it occurred after a reboot so could be an IRQ issue from software to hardware addressing

Chamson
Level 7

Disable high brandwith support, and it will restart without error, even with xmp/expo on

Where is this option in the bios?

ROG MAXIMUS Z690 HERO + 12900K + XPG 32GB RAM DDR5 6000CL40 + RTX 3080 GALAX HOF + ROG RYUJIN II 360 + LIAN LI XL + CORSAIR HX1000i + M2 SAMSUNG 980 PRO 1TB + M2 SAMSUNG 980 PRO 1TB + SSD SEAGATE 1TB. 😉

It should be around where you enable expo/xmp. Maybe advanced memory options. On gigabyte its right under xmp/expo if you watch bios as advanced user not easy

mahava
Level 8

Just installed November Win11 CU and had the 0D error again on reboot, but again just had to press reset once and it boots fine , so the memory contex restore seems to almost solve, thx for headsup about the Monitoring Software reboot workaround im gona try that when reach stable bios (i dont feel tempted runnning a beta now ... ) 

Would beta be any worse than an unstable board/PC???

how many people here are running this new beta bios?? Any issues noticed from it?