Replace the old components, restart the motherboard every 1 to 3 minutes.
Replace the old components, restart the motherboard every 1 to 3 minutes.
I own an AMD Ryzen 5 5600X at 3.7 GHz with a 6-core configuration, an MSI B550M PRO-VDH WIFI Micro ATX AM4 motherboard, Silicon Power GAMING 16 GB DDR4-3200 CL16 RAM, a Crucial P3 1 TB M.2-2280 PCIe 3.0 X4 NVME SSD, an EVGA SC GAMING ACX 3.0 GeForce GTX 1070 8 GB graphics card, and an EVGA SuperNOVA 750 G3 750 W 80+ Gold certified fully modular ATX power supply.
Please note these components are all used except the RAM. I initially installed everything on an a520M-a pro motherboard with a different used power supply. I first connected it to the EVGA, installed Windows, and optimized the RAM to 3200mhz. Later, I placed it in a case with a shiny chrome 1000W PSU I found at Goodwill (a decent brand, but I can't recall the exact model). When I powered it on, the CPU indicator stayed lit on the motherboard. I also attempted a Ryzen 3100 build, but the same issues persisted.
I switched to a 650W Rosewell Hive power supply, which allowed me to boot via USB, but the installation process would repeatedly restart to the BIOS logo. Eventually, I upgraded to a 750W PSU and managed to boot from USB, though the Windows installation would frequently reboot, sometimes more than five percent of the time.
I suspect the problem might lie with the used components, possibly due to damaged wiring from the chrome 1000W PSU. I’m trying to piece things together, hoping the BIOS access gives me a clue. If time allows, I’ll reinstall the 3100 to see if it works, otherwise I’m limited without purchasing additional parts. The 3100 could also be faulty from the same PSU, though that’s uncertain.
Any assistance would be greatly appreciated.
temperature ranges from 37 to 40, but it only reaches 40 when the RAM operates at 3200MHz
Disable ram overclocking.
Ensure ram modules are placed in slots A2 and B2 (second and fourth from the CPU).
If this doesn't work, attempt using a single ram module in slot A2.
Once stable operation is achieved (computer no longer restarts randomly), update the BIOS to the latest version.
Be cautious during the BIOS update process, as a failed update may brick the motherboard.
I have placed the RAM in the correct slots as shown on the motherboard diagram and also tested each of the two sticks separately in A2, but the same behavior persists.
Remove your RAM, clean the slots thoroughly with a dust-repelling cleaner, ensuring no debris remains. Verify the RAM slots are free of hair and debris. Clean the RAM itself as well. Finally, confirm the RAM is securely seated; when you hear the click, check if the opposite side is properly positioned. After the click, gently push the RAM at both ends and the middle to ensure it is firmly attached. Perform a CMOS bios reset afterward and attempt the process again. Disconnect all external devices or USBs, retaining only the keyboard and mouse, minimizing connections. If using multiple drives, keep only the bootable one connected while unplugging the others. If the PC starts up, plug in one drive at a time to test if the issue persists.
There was a difficulty updating the BIOS, and I couldn't determine the reason. I repeatedly attempted to install the newest BIOS for the B550m pro-vdh wifi, following the instructions on my motherboard. After checking the BIOS settings, I found it listed as MAG B550M Bazooka. What caught my attention was that the Bazooka BIOS doesn’t support Wi-Fi, whereas the motherboard clearly does. When reviewing images on MSI, I confirmed the presence of the B550m pro-vdh wifi. It’s puzzling since the Bazooka BIOS isn’t visible when using mflash, and it doesn’t update to the B550m pro-vdh wifi BIOS even when using MSI.ROM. However, I was able to replace the existing BIOS with the latest Bazooka version, which was already present. I’ve reset the CMOS multiple times, but the Bazooka BIOS remains unchanged.
I cleaned the RAM slots and RAM. I also installed the Ryzen 3100 and observed the same issue as described previously. I shared the BIOS problem in MSI forums to check if anyone else encountered a similar issue, hoping it might be the underlying cause.