Red LED indicator on ASRockBoot, no screen or BIOS access.
Red LED indicator on ASRockBoot, no screen or BIOS access.
Hello, a few weeks back I assembled a PC for a friend. It had an Asrock B550M Pro4 with Ryzen 5 5600, 16 GB GSKill Aegis WD SN570, a 1TB GTX 1650 Bequiet System Power 10 450W, and we installed Windows 10. Everything seemed to function properly. Recently, he called saying his machine was stuck in reboot mode. I attempted remote maintenance and restarted, hoping Windows would fix it itself, but it wouldn’t boot. Now I’m stuck—can’t access BIOS, no display signal, and the Boot LED is red. I’ve tried resetting the CMOS in different slots, changed RAM modules, and checked basic components. Any suggestions? Did something happen after about two and a half weeks?
Attempt to start with just one RAM stick in slot A2 and the CPU already installed. Ensure power is connected but all other components are removed. Use a screwdriver to discharge the power pins. If it fails to respond, it may indicate a dead motherboard or CPU.
Check the CPU and motherboard LEDs. If they stay red after pressing the power button, it suggests a hardware issue. Test with another power source or reset components to determine which part is faulty.
If it stalls on the boot led, reset the CMOS by disconnecting power and applying the jumper/button. Refer to the motherboard manual for the exact location. This board can’t have its BIOS changed without entering BIOS settings, so if it fails even with minimal configuration, options are limited.
LED remains active, fans and other components are functioning normally but no signal detected. Unfortunately, the CPU isn't displaying graphics and any cable change doesn't help.
Review my changes. It seems the board fails to start properly. The component tests look correct.
Struggled locating the CLRcmos issue... succeeded now. DRAM and CPU indicators show red, indicating faulty RAM and a "no" signal from the CPU. Fixed by turning it off and on again only the boot light came back on.
I faced the same issue, and swapping the CPU resolved it for me. I hope there are more guides available for these boards. Maybe others encountering this can locate this discussion.