F5F Stay Refreshed Hardware Desktop Ryzen processor in X370 device fails to power on.

Ryzen processor in X370 device fails to power on.

Ryzen processor in X370 device fails to power on.

T
TheDark245
Member
125
03-18-2019, 12:16 PM
#1
Hey everyone, just updated my rig with a new 3600 and an MSI x370 gaming pro carbon. I changed the BIOS last night to the latest beta version from MSI. After installing the new chip, nothing happened—no lights, no fans, even after reseating the CPU and touching the CMOS jumper. The PSU test with a handheld plug-in worked fine. Now I’m back to fans and lights but can’t boot. I’ve tried re-seating RAM, clearing CMOS again, and reconnecting the 24-pin, but it still won’t start. I suspect I’ll need a different board for this model. Any recommendations for cheap B450 boards with ZEN 2 support? Also, what should I do to get my current setup back online?
T
TheDark245
03-18-2019, 12:16 PM #1

Hey everyone, just updated my rig with a new 3600 and an MSI x370 gaming pro carbon. I changed the BIOS last night to the latest beta version from MSI. After installing the new chip, nothing happened—no lights, no fans, even after reseating the CPU and touching the CMOS jumper. The PSU test with a handheld plug-in worked fine. Now I’m back to fans and lights but can’t boot. I’ve tried re-seating RAM, clearing CMOS again, and reconnecting the 24-pin, but it still won’t start. I suspect I’ll need a different board for this model. Any recommendations for cheap B450 boards with ZEN 2 support? Also, what should I do to get my current setup back online?

I
iskela99
Member
247
03-18-2019, 09:44 PM
#2
For a fresh setup, consider the MSI B450 Tomahawk MAX. It handles third-gen Ryzen chips without needing a BIOS update.
I
iskela99
03-18-2019, 09:44 PM #2

For a fresh setup, consider the MSI B450 Tomahawk MAX. It handles third-gen Ryzen chips without needing a BIOS update.

S
SirCyaniide
Member
140
03-21-2019, 12:04 PM
#3
The beta bios you tried may not have loaded correctly. This MSI board likely has a BIOS flashback option. You could try re-flashing with your earlier BIOS to test it.
S
SirCyaniide
03-21-2019, 12:04 PM #3

The beta bios you tried may not have loaded correctly. This MSI board likely has a BIOS flashback option. You could try re-flashing with your earlier BIOS to test it.

R
raider112233
Member
168
03-21-2019, 12:56 PM
#4
The new BIOS was functioning properly this morning; it started up without issues. However, I’m unable to display anything on the screen, making the BIOS unusable. My only guess is that something caused the damage, but it doesn’t clarify why the 3600 has no power while the 1600 shows fans and error lights (but no RGB or post).
R
raider112233
03-21-2019, 12:56 PM #4

The new BIOS was functioning properly this morning; it started up without issues. However, I’m unable to display anything on the screen, making the BIOS unusable. My only guess is that something caused the damage, but it doesn’t clarify why the 3600 has no power while the 1600 shows fans and error lights (but no RGB or post).

A
anakindaur
Senior Member
576
03-21-2019, 02:31 PM
#5
The fix ended up being a design issue, and I was mistaken. Initially, taking out the cooler caused the CPU to detach, which I didn’t notice. During testing, I forgot to reset the retention lever in every run. Using 3600 worked without any CPU errors, but switching to 1600 cleared CMOS and reset the 24-pin connector—still no boot. After clearing CMOS and resetting the memory with 1600, it finally booted! It turned out I hadn’t properly re-seated the RAM with 3600, but after trying all these steps it functioned. This shows how sensitive motherboards can be, or maybe just how fragile early Ryzen boards are.
A
anakindaur
03-21-2019, 02:31 PM #5

The fix ended up being a design issue, and I was mistaken. Initially, taking out the cooler caused the CPU to detach, which I didn’t notice. During testing, I forgot to reset the retention lever in every run. Using 3600 worked without any CPU errors, but switching to 1600 cleared CMOS and reset the 24-pin connector—still no boot. After clearing CMOS and resetting the memory with 1600, it finally booted! It turned out I hadn’t properly re-seated the RAM with 3600, but after trying all these steps it functioned. This shows how sensitive motherboards can be, or maybe just how fragile early Ryzen boards are.