I recently purchased the X570 Unify and noticed that while in Windows the motherboard continues to cycle Debug Codes starting from the high 50s and cycling down all the way down to the lower 40s. Then it starts back in the 50s and cycles down one by one to the lower 40s. The chipset fan isn't turning on so I don't believe that its showing temps.

I'm not experiencing any issues (yet) and the manual coincidentally doesn't have the 40-59 Debug Codes outlined so I have no idea what they mean.

Anyone have an idea?

I bought a new MSI MEG x570 unify mainboard from Amazon.de and it is working properly most of the time but has one major issue:

When I turn on my pc after being away a few hours it displays the debug code "00", most fans of the system start spinning at a fixed rate and the LED of my GPU turns on but there is no video output.

I found two methods that work to help getting the motherboard back to normal:

1. Clearing CMOS will make it possible to boot on the pc afterwards but you will lose all personalized settings you did in the BIOS, ex. PWM Fans and RAM frequency settings.

2. Turning the power supply unit off and back on while the pc is turned on will make it possible to boot the pc normally and no settings are lost.

These two solutions are useful in the meantime but I don't want to do this on the long term so I am still searching the underlying cause of this error. I will be thankful if somebody has a suggestion on how to fix this problem.

I already tried to solve this by flashing the latest non-beta version of the motherboard BIOS (Version 7C35vA3), I also installed the Drivers from the Support website of the mainboard but it did not solve my problem.

August 2020 update: I did multiple bios updates (currently A5) but it still happens sometimes...

I’ve been searching for this issue amongst X570 board and it seems like it affects MEG Ace’s more than MEG Unify’s but the overall outcomes are similar.

The issue manifests when debug led under usual circumstances will read out CPU temps will display a code of “00.” No such code is listed in the manual. When this happens, all fans within my system will fall to base RPM despite fan curves that were initially set in BIOS. Windows is otherwise stable (no errors, BSOD, etc). I’ve left HWinfo64 up the last few times this has happened and CPU temps increase as to expected. The first instance of this occurred roughly one month after completing my build. A reboot will resolve the issue. Once the system reboots you can hear the fans spooling up to their designated fan curve speeds. After the initial “00” event, it has been occurring every 1-2 days.

This is of particular concern considering any number of CPU intensive programs could be running while all system fans, most notably CPU cooler, won’t be able to compensate beyond baseline speeds.

System is Ryzen 3700x, Noctua D-15 cooler, X570 Unify BIOS ver. E7C35AMS.A30. All fans are plugged into appropriate fan headers and all are under PWM control.

I’m hoping there is a solution for this issue. Any others with this problem please share your experience since I might have missed something.

Having an issue with an X570 Unify board that I just received, and can't find any similar reports. Computer is assembled and won't post. Tried multiple sticks of RAM in multiple configurations, multiple BIOS revisions via USB flash, but the RAM error LED remains lit. The debug displays as follows from power on, the best I can speed read:3E 14 F9 (hangs) C0

then it loops 00 33 74 dE Ad dF until manual shutoff.

I know AD is an actual code, but DE is at best an unlisted one and watching it spell out DEAD is not reassuring.

tested with Corsair HX850 PSU, Nvidia Quadro RTX4000 GPU, Ryzen 2600 CPU, and a bunch of ram. Notably Corsair CMK16GX4M2A2400C16 and CMK16GXM2B3000C15 which should be on the QVL for the processor.

Any suggestions before I start looking into RMA?

I have a unify x570, with 5800x cpu.

cleaning the pc, i accidentally hit bios flackback.

My pc works perfectly, but when I access the bios, before it put code (ab) and now it puts code (F3).

should I be worried?

Had 0d errors with this board before, but persistence and rebooting (after dumping current/power button held for 30 seconds) usually won out. Today I got a new Lian Li case, Lian Li fans, and 32 GB RAM (GSkill Trident Z RGB, 3200). Needless to say, much excite/wahwahweewah.

Upon powering on the PC, I don't even get a post. It goes straight to error code C5 for a few seconds, then switches to the all too familiar 0d.

I've tried holding the Reset CMOS button in the back, specifically holding it down for 5-10 seconds, but that doesn't change anything.

This couldn't be a BIOS issue, right?

Do I try and RMA/Warranty the board with MSI or go back to BH Photo (got it from them last November)?

Is there another option?

Sincerely desperate,

A fellow nerd Raptured_Spleen.