F5F Stay Refreshed Hardware Desktop Code 00 on the motherboard indicates a hardware or system error.

Code 00 on the motherboard indicates a hardware or system error.

Code 00 on the motherboard indicates a hardware or system error.

H
HaTuYanga
Junior Member
22
12-14-2023, 01:06 PM
#1
I’m working with an MSI X670E Carbon board paired with a 7800X3D processor. I’m facing problems during reboots, often hitting error code 00 with the CPU’s red LED and RAM’s yellow LED. What I’ve tried so far includes resetting the CMOS, powering off completely for a while, and testing RAM one stick at a time. The fix seems to work only after a reboot. If I power it back up right away, everything functions normally. However, leaving the system on for long periods—like overnight—tends to trigger the “00” error again. I also observed some discoloration around the motherboard connector and CPU heatsink, but it doesn’t match the burn patterns seen on other X3D chips.
H
HaTuYanga
12-14-2023, 01:06 PM #1

I’m working with an MSI X670E Carbon board paired with a 7800X3D processor. I’m facing problems during reboots, often hitting error code 00 with the CPU’s red LED and RAM’s yellow LED. What I’ve tried so far includes resetting the CMOS, powering off completely for a while, and testing RAM one stick at a time. The fix seems to work only after a reboot. If I power it back up right away, everything functions normally. However, leaving the system on for long periods—like overnight—tends to trigger the “00” error again. I also observed some discoloration around the motherboard connector and CPU heatsink, but it doesn’t match the burn patterns seen on other X3D chips.

C
Cyanstrophic
Senior Member
668
12-16-2023, 04:47 AM
#2
Check if the problem continues when disabling XMP. If it does, the board might be faulty.
C
Cyanstrophic
12-16-2023, 04:47 AM #2

Check if the problem continues when disabling XMP. If it does, the board might be faulty.

M
m4xesh3pard
Member
177
12-16-2023, 03:53 PM
#3
I believe this might involve a conflict between BIOS configurations and the AMD GPU driver. When you apply overclock settings through the GPU driver, you can select whether to affect the whole system or just the CPU or GPU. Previously, after reseating the CPU and letting the motherboard refresh the microcode, the issue didn’t appear. However, when you load the overclock profile last Sunday, the problem resurfaces.
M
m4xesh3pard
12-16-2023, 03:53 PM #3

I believe this might involve a conflict between BIOS configurations and the AMD GPU driver. When you apply overclock settings through the GPU driver, you can select whether to affect the whole system or just the CPU or GPU. Previously, after reseating the CPU and letting the motherboard refresh the microcode, the issue didn’t appear. However, when you load the overclock profile last Sunday, the problem resurfaces.

T
TheSimple
Member
229
12-16-2023, 05:50 PM
#4
I think I found the source of the problem: the Zen4/Zen5 I/O Die seems overly reactive when using an extension PCIe cable. Keeping the motherboard BIOS defaults (Auto PBO and EXPO off) should prevent the error. But when the I/O Die is under heavy use—such as with PBO enabled and EXPO active via the extension cable—the issue comes back.
T
TheSimple
12-16-2023, 05:50 PM #4

I think I found the source of the problem: the Zen4/Zen5 I/O Die seems overly reactive when using an extension PCIe cable. Keeping the motherboard BIOS defaults (Auto PBO and EXPO off) should prevent the error. But when the I/O Die is under heavy use—such as with PBO enabled and EXPO active via the extension cable—the issue comes back.