I have had this board working fine for almost a month with 9950x and Kingston RAM. I haven't done any overclocking. Last night I turned it OFF and it has refused to boot again after that. It just shows code 00. I tried Ryzen 9600 but still stuck at code 00. I have tried resetting the bios with the button on the back as well as removing the battery but still no boot. I then tried to do bios flashback but it seems like that is also not working for me. I plugged a usb next to the lan port and held the flashback button but nothing happens, also tried a usb 2 flash drive and still nothing. I am not sure what to do at this point and also very conused as to what caued this issue. Any ideas

I'm trying to build a new PC, bought all new parts. I choose an Asrock X670-E Taichi Carrara as my motherboard, but the PC will not start and it shows code 00 on DR. Debug. Never worked, completely new build with a new Ryzen 7800X3D CPU. What I tried so far:

1 - Bios flash back to versions 1.28, 1.24 and 1.04, all show the same error

2 - Tested the PSU on another PC, it works fine

3 - Tried with memory, and without memory, with cooler and without cooler

4 - CMOS reset

Nothing works still stuck at 00, PC won't boot or show anything. What else can I try? I'm thinking about asking for RMA.

Full list of components is:

PSU: Super flower leadex III 850W

CPU: Ryzen 7 7800X3D

MEMORY: 2X 16GB CORSAIR VEGEANCE DDR5

VGA: RTX 3070

But for now I'm trying with just PSU, MB and CPU. It should at least progress from 00 to another code.

Here is 2 photos of it. Testing with bios 1.28:

Please can someone help? I'm very frusted and sad with all this situation.

Hey everyone. Here're my specs and some background:

ASROCK B650E Taichi Lite
Ryzen 7800x3d
Arctic Liquid Freezer III 360 AIO
MSI RTX 4090 Gaming Trio
be quiet! DARK POWER 13 1000w
G.SKILL Trident Z5 Neo 64GB(2X32) DDR5 6000Mhz CL30-40-40-96
2x SAMSUNG 990 PRO NVMe m.2
CASE = Lian Li Lancool 216

I just finished building my first computer and it worked OK for 2 days. Installed all of my software, ran time spy from 3dmark on day 1, looked fine. Next day, i ran Steel Nomad from 3dmark. Completed all 20 cycles fine. GPU went to like 78C max, CPU was like 58C max but i think steel nomad is mostly about GPU. When i ran timespy during the CPU test i think the 7800x3d went up to like 80 but i have seen it go up to like 85-86 when i was playing on an emulator while waiting for adobe creative cloud software to install. Regardless, 15-20 mins after i ran Steel Nomad, while the PC was idling, the monitors go black, the PC keeps running but using the power / reset buttons wouldn't do anything, so i had to switch off the PSU to turn it off. Everytime i try to power it on, everything seems to be working but i get error code 00, nothing shows up on the monitors, and i can't power off the PC unless i turn off the power supply.

Here's what Asrock's Debug LED Troubleshooting Checklist says about error code 00.
Please check if the CPU is installed correctly and then clear the CMOS.

• Initially, before starting the build at all i flashed the BIOS to the latest version ( 3.02 ) before installing the 7800x3d.

• The board has a Clear CMOS button in the back and the manual says that this function is only workable when you power off your computer and unplug the power supply. I tried holding that down for like a minute but i don't get any visual feedback from anywhere that something is done. Not sure if there should be any either though. I'm new to all this.

• Until this happened, the PC was working properly, It was super quiet. I didn't notice anything out of the ordinary at all. It is the first time i build a PC but i've had PCs for like 18 years by now.

I would appreciate any suggestions. I'm just super demoralized right now.
Thanks.

Creating a post for better visibility. This investigation took place here: https://www.reddit.com/r/ASRock/comments/1i7a2nd/comment/m8jzl59/

I'll continue updating this post with news. Sorry that this post is a bit of a mess, but I'm confident that the information might be valuable for people. Trusting SEO to do a better job finding it.

In case you're seeing this, please reach out to ASRock for them to either provide you with a new 3.18 version (they provided me with 3.18.MEM03) or downgrade to 3.10 / 3.12.AS02.

LE: Seems like ASRock pulled 3.18.AS01 from X870E Taichi Lite website: https://download.asrock.com/BIOS/AM5/X870E%20Taichi%20Lite(3.18.AS01)ROM.zip

LE2: Seems like ASRock added back 3.18.AS01.

LE3: Seems like ASRock added 3.18.AS02 for X870E Taichi Lite. Be aware that this causes the same 00 debug code as it does not include the CPU voltage increase from 3.18.MEM03. Tested with my own 9800X3D and X870E Taichi Lite. This is only for the 9800X3D units that are affected by this.

Also, ASRock confirmed to me that 3.18.MEM03 that they provided to me increases the voltage to 1.2V for the 9800X3D and that allows it to boot and fix the 00 debug code. The issue is that not enough voltage was applied for some 9800X3D units and it was not stable. They will continue doing some validation tests and then probably release it publicly.

LE4: AMD release BIOS 3.20 Beta which fixes the 00 debug issue: https://download.asrock.com/BIOS/AM5/X870E%20Taichi%20Lite(3.20)ROM.zip

Original post starting from here:

Seems like my X870E Taichi Lite with 9800X3D is hanging with diag code 00 on the motherboard after flashing it. Tried clearing CMOS and it still doesn't boot. Was running 3.17.AS02 before. Anyone else having issues?

LE: Trying BIOS Backflash right now.

LE2: Didn't work with BIOS Flashback.

LE3: Since it's weekend, I thought I should be giving it another go before sending both CPU and mobo for warranty. After reflashing 5 versions of the BIOS via BIOS Flashback, 3.18.AS01, 3.17.AS02, 3.16, 3.10, 3.05, I tried again with exactly the same setup, same USB stick, the 3.05 BIOS. I wasn't expecting it to come back, became pretty used with code 00. It started memory training and sure enough, it booted up fine. Tried again upgrading to 3.18.AS01 and same 00 code. So, probably a borked BIOS. I know it's labeled as beta, but this never happened before. Especially since I already tried downgrading to 3.05 the same day this happened.

LE4: Seems like I cannot run anymore BIOS 3.15, 3.16, 3.17.AS02. All three result to the same 00 error code on the Dr Diag screen on the mobo. Was running 3.16 and 3.17.AS02 just fine before trying to flash 3.18.AS01. Not sure what's actually going on.

I tried incrementally going from 3.05 (3.05 was BIOS flashbacked to "revive it") -> 3.06 -> 3.08 -> 3.10 -> 3.15 -> 3.16. Then I settled on 3.10 which I could revert to as the latest version of the BIOS that still works (via Instant Flash or BIOS Flashback). I still don't understand why I cannot go anymore past 3.10. It worked fine before trying to update to 3.18.AS01.

I'm starting to suspect this being the RAM, although it POSTs fine even with the XMP profile loaded (6000MHz CL30). I'll try running a memtest with the 3.10 BIOS and see if it returns errors.

LE5: It's not the RAM kit. Passed 4 times on passmark memtest. My kit is: CMK64GX5M2B6000C30. This kit is not on the QVL, but it's new and worked just fine until this BIOS release.

Also, found this post on this forum related to this issue: https://www.hardwareluxx.de/community/threads/9800x3d-l%C3%A4uft-nicht-mit-neueren-agesa-microcode.1363382/

And another Reddit user mentioned of this issue here: https://www.reddit.com/r/ASRock/comments/1i9mcuf/9800x3d_x870e_nova_error_00_does_not_boot/

LE6: Installed a brand new 9600X on the same board and flashed 3.16 and 3.18.AS01 (which don't work on my 9800X3D, results in 00 when trying to boot with it, but did work before flashing 3.18.AS01 the first time) and it boots just fine. I think this pretty much confirms the fact that something broke the 9800X3D when flashing 3.18.AS01 or this can be fixed with a new AGESA release. I highly doubt it can be mitigated by an AGESA release, though, and probably I need to RMA my 9800X3D. Seems like the motherboard is not actually the issue.

LE7: For my curiosity, I installed back my 9800X3D and tried re-running 3.16 and sure enough, 00 diag code. So, it's pretty much confirmed that it's probably a borked CPU, as it works fine for other members.

LE8: Sent out my 9800X3D for a warranty claim from the place I bought the CPU from (Flax Romania) and they tested it with two other boards and it works fine for them. Even ran stress tests like OCCT on it. One test was done with a board with their supplier, while the other test was done with a board that they had (ASUS PRIME X670E-PRO WIFI) . Asked more specifically the BIOS version they tested with, which was the latest stable release. I asked him to try and do the test with BIOS version 3201, which contains AGESA to ComboAM5 PI 1.2.0.3a: https://www.asus.com/motherboards-components/motherboards/prime/prime-x670e-pro-wifi/helpdesk_bios?model2Name=PRIME-X670E-PRO-WIFI

He confirmed to me the next day that the motherboard POSTed with that 3201 BIOS version as well, which probably tells me there's a bug in ASRock's BIOS? I'm not really sure. They sent the CPU back to me. I'm not exactly sure how to go forward with this. ASrock's support recommended me to run the latest 3.12.AS02 BIOS (last version I've described that works on my 9800X3D) until they receive a 9800X3D with this problem so they can test. They are expecting that 9800X3D unit to arrive to them and conduct their tests and maybe we'll see another BIOS release. I'll see how this evolves and if it's not fixed via a new BIOS release, I'll do a warranty claim again for the CPU, but probably directly with AMD.

LE9: ASRock provided me with BIOS 3.18.MEM03 and this finally boots up just fine on my "defective" 9800X3D. Probably not defective after all. I've informed them on this, asked for a changelog and permission to share the file here. Will upload it once I get more information from them.

LE10: ASRock said this is a "special" BIOS for my unit, so they advised me to not share it. They response on what's changed is it's the CPU voltage, there has been adjustments to it. I've asked them if it's a decrease or increase. My thinking is it's an increase, probably voltage was insufficient on 3.18.AS01 and they bumped it up. If it would've been the other way, it would have been a fried chip, I guess. They said they're still in the process of verification, so a stable version of this 3.18.MEM03 BIOS will not be released for now.

So I just built a new PC with the ASRock X670E Taichi. Here's my full specs:

CPU: AMD Ryzen™ 9 9950X
MOBO: ASRock X670E Taichi
CPU Cooler: Corsair iCUE H150i Elite Capellix 360mm
RAM: G.SKILL Flare X5 64GB (2x32GB DIMMs) 6000MT/s CL30-40-40-96
GPU: ASUS ROG STRIX RTX 2080 Ti
NVME1: Samsung 990 PRO 4TB M.2 PCIe v4.0 (7.45 GB/s)
NVME2: Samsung 970 EVO Plus 2TB M.2 PCIe v3.0 (3.50 GB/S)
NVME3: Samsung 970 EVO Plus 2TB M.2 PCIe v3.0 (3.50 GB/S)
PSU: Corsair HX1000 CP-9020139-NA
Audio Interface: RME HDSPe AIO PCI-e 192KHz, 38 Channels, 24bit

Occasionally, but not always, the motherboard will fail to boot and throw me code 0d. I've read about others experiencing this code and apparently this means an undetected CPU / RAM issues / PCIe issues.

The thing is, for the most part the computer boots fine. I only get the error code maybe one out of five times after restarting the PC. All stress tests pass with flying colors. I can run Prime95 / OCCT stability test / Karhu RAM Test for hours and get no errors. Under 100% load the CPU is only in the mid 70ºC range, and on stock settings the 9950X is benchmarking way above normal in OCCT. I am really hoping this is isn't the CPU as my temps and benchmarks are amazing.

The first thing that comes to mind is that while building I think I may have dropped an m.2 screw somewhere below the PCIe 5.0 nvme slot. I searched all over the motherboard, took it out and literally shook it to hear if the screw got stuck somewhere and heard nothing. I tried to take off the extruding front panel to see if I could find it but was unable to take it off (don't have the right hardware).

So I kind of shrugged it off, figuring I just dropped the screw somewhere on my floor and continued building. But in the end I did not find the screw on the floor so now I am really worried that the motherboard is literally short circuiting.

Another thing I'm worried about is that maybe I tightened the waterblock on the Capellix too tight.

Should I RMA the motherboard? I can't really effectively test what's causing the issue because it mostly doesn't throw this error code. Only once in awhile.

I'm leaning towards an RMA. Any thoughts?