The MSI Debug LED is malfunctioning after some time. Need assistance!
The MSI Debug LED is malfunctioning after some time. Need assistance!
Hello! On the new MSI X570 MEG GODLIKE motherboard, the Debug Code LED malfunctions over time. Sometimes it fails completely after a few hours, and other times the PC shuts down after just 2-3 hours. The red LED for the CPU fan and the SYS_FAN_1 also turn off at the same time as the debug light. Could be related to Dragon Center settings? I've checked if any programs interfere, but haven't found a solution yet. Thanks for your help! Maybe someone else has encountered this issue?
The debug function is operating correctly. Zero typically means no activity and signals standard functioning. Thirty-five indicates the CPU has started after memory setup. The BSP or bootstrap processor is chosen, likely for memory training. Probably related to memory calibration. These codes aren't direct error signals like beep codes; they're more about status updates. I'm not very experienced with MSI boards, but I understand the basics.
Thanks for your response! The LED color was something I wasn’t aware of. I believe the 35 corresponds to the CPU temperature. It seems to match the Core temperature reading at least. The issue feels odd but hasn’t led to any instability yet—just restarting the PC resolves it until the next time, of course.
It's not about the temperature. The reading is next to it on the left side, which is definitely a postcode, not an error code. You might try connecting the small motherboard speaker to check if it produces beep codes when stuck at 35. This could help narrow down the problem. Is there a point after postcode 35 where the display stops working?
Uncertain about the God-like feature, but some MSI boards include a solid switch on the main board that shuts down the LED lights. Often controlled via an RGB header. Could it have been accidentally damaged?
Hello once more, I'm pretty sure the display is showing the CPU temperature, not any post or error codes. This clip from this exact machine confirms it. It might be related to the program scanning and displaying a crashing or shutting-down CPU temperature, which could cause the program to show 00. Still odd that the fan header LED is also turning off.
You didn't provide an answer. The codes appear to be related to the post section. I checked if the system was still active with that code, which is typical for a debug display. Temperatures are shown after the system starts and you can usually adjust this setting in the BIOS. To be clear, the problem seems to be about the temperature display not working, possibly due to software on the motherboard. This could vary depending on the motherboard's operating system.
The system starts up without getting stuck on any postcode. The real problem is it can't show temperatures while running or playing games. It just displays '00' and the fan header light turns off, but before that it showed normal temps and the fan light was on.