New PC suddenly stopped working - Q-code 0d

[Belzebutinov]

Hello all,

 

Let's get to the point!

 

THE ISSUE

 

20 days ago I assembled a new PC (specs below). It worked fine, got great benchmarks, ran games perfectly (4k, ultra options, etc.).

 

On Friday 15/01, I turn it on, log into my Windows session, go grab a drink and come back to a crashed PC which no longer boots, not even to the BIOS. As a side note : I don't have any pets, nor any one living at home with me, so this happened on its own.

 

At first, the MoBo indicated a Q-Code of "22", which I understand to be a RAM-related error. By the next day, the error code had become - and remains to this day - Q-code "0d". Also, the small led light for "DRAM" error, right under the Q-code indicator, is lit (to be precisely, it lights up the instant I turn on the PC).

 

So, as of typing this: when I turn on the computer, the Q-code briefly flashes to "10" (a normal booting up phase I understand), then switches and stays stuck to "0d" with the DRAM led lit. The computer won't boot at all and I have no access to the BIOS at all (black screen). The "DRAM" Led lights up as soon as the computer is turned on.

 

Also, in case it matters : my RAM sticks are RGB. When, in the first evening, I had a Q-code "22", they would still light up (although the computer wouldn't post). As of Q-code "0d", they no longer light up, at all. 

 

MY SPECS

 

PCPartPicker Part List

CPU: AMD Ryzen 9 5900X 3.7 GHz 12-Core Processor  
CPU Cooler: Noctua NH-D15S chromax.black 82.51 CFM CPU Cooler  
Motherboard: Asus ROG Crosshair VIII Hero (WI-FI) ATX AM4 Motherboard  
Memory: Crucial Ballistix RGB 32 GB (2 x 16 GB) DDR4-3600 CL16 Memory  
Storage: Western Digital Black SN850 500 GB M.2-2280 NVME Solid State Drive  
Storage: Western Digital Black SN850 2 TB M.2-2280 NVME Solid State Drive  
Storage: Toshiba X300 4 TB 3.5" 7200RPM Internal Hard Drive  
Video Card: MSI GeForce RTX 3090 24 GB GAMING X TRIO Video Card  
Case: be quiet! Dark Base Pro 900 Rev. 2 ATX Full Tower Case   
Power Supply: Corsair HXi 1200 W 80+ Platinum Certified Fully Modular ATX Power Supply 
Optical Drive: Asus BC-12D2HT Blu-Ray/DVD/CD Writer  
Operating System: Microsoft Windows 10 Home OEM 64-bit   
Software: Microsoft Office Home & Student 2019 - 1 Device Software

Generated by PCPartPicker 2021-01-20 08:21 CET+0100

 

I run Windows 10, 64bit.

 

As of the time of the crash, I was using the following BIOS (which was the most up-to-date, non-beta one as of assembling the PC): Version 2702, 2020/11/24, ROG CROSSHAIR VIII HERO (WI-FI) BIOS 2702

 

Final possibly relevant note : I have not overclocked anything, except for enabling DOCP in the BIOS to get my RAM to its normal 3600Mhz speed. 

 

TROUBLESHOOTING

 

I have tried the following steps :

• Took out both RAM sticks, and tried :
  • Stick 1 alone in all four slots. Q-code "0d" in each case (RGB stays unlit).
  • Stick 2 alone in all four slots. Q-code "0d" in each case (RGB stays unlit).
  • Sticks 1 and 2 together in A2*/B2* and A1/B1 configurations. Q-code "0d" in both cases (RGB stays unlit).
• Flashed the MoBo to the newest non-beta bios : Version 3003, 2020/12/07, ROG CROSSHAIR VIII HERO (WI-FI) BIOS 3003
  • Retried the RAM with it, issue remained.
• Purchased and installed new RAM: HyperX Predator RGB - 2 x 16 Go (32 Go) - DDR4 3600 MHz - CL17 (note that this model is specifically on ASUS's QVL)
  • Exact same issue: Q-code "0d", RGB stays unlit as if the MoBo won't even detect it, still no access to the BIOS.
• Ran a CMOS, re-flashed to the 3003 BIOS above (which I have to: the default BIOS won't run zen3 without an update)
  • Same problem remains. 

As a sidenote, I also made sure, in each test, that the RAM was properly clipped in, and that the board was properly powered on. 

 

Also, if it can be any help to anyone, here are two pictures: this one shows the current error on the MoBo with one RAM stick in, and this one shows the DIMM slots with nothing in (I don't seem to see any damage of any sort).

 

The most jarring thing to me, in all of this, is that for around 15 days, the computer performed absolutely flawlessly before this issue just popped up. No fooling around with it, no spilling a drink or giving it a kick, or anything : I logged into Windows, and kaboom. 

 

Having swapped out the RAM, I can only surmise that this has something to do with the MoBo itself being flawed? I very much hope not, because I would hate to have to disassemble the entire rig and cable work, take apart CPU cooler, clean it up, have to reinstall windows, all that. So if anyone can imagine any further steps that do not involve RMA-ing the MoBo, I would be beyond grateful. 

 

Sorry for the long post, but I thought it was relevant to include the steps I'd already tried. Any inspiration from you fine people will be most welcome ! Thank you in advance !

 

[Harlon]

So first thing i want to say is wow, you have an amazing system. Now most likely the issue is motherboard. If you search up 'ASUS 0d error', the top link is it and what ASUS said is that they should RMA there board so if you still have the box and everything then you should be able to get a refund but if you don't have on of the items that comes in the box then you will most likely have to get another motherboard. If all of your components are getting power so your gpu, cpu ,ram, psu, storage, if they are all getting power then it will most likely be a motherboard issue. now you motherboard is showing the error code so it could be something to do with psu but it just doesn't sound like it. Have you tried calling ASUS because if not i would just recommend doing that before you buy anymore things or RMA your board, hope this helped.

[Belzebutinov]

First off, thank you very much for your reply.

 

I've quite extensively googled anything I could about Q-codes "22" and "0d" before bothering y'all here, and yeah, I pretty much don't see any other options at this stage. I also don't expect the PSU to be at fault, because pretty much everything else is lighting up as it should.

 

But still, maybe I'm an idiot and missing out on something obvious, so here's to hoping there's something else besides the RMA option left to try