No, your motherboard isn't showing signs of failure. It's functioning normally.
No, your motherboard isn't showing signs of failure. It's functioning normally.
Hello everyone, a few months ago I upgraded to a Ryzen 5800X and an ASUS TUF x570 motherboard. Around a month ago my system began crashing when using a Corsair MP510 M.2 as the boot device. At idle and light load it worked fine, but once I started Anno 1800 or similar heavy programs it would shut down instantly. I replaced the drive with a SATA unit and sent the M.2 back in for return, but the problem persisted. After reinstalling, I found my BIOS was showing low voltage on the 3.3V rail, so I rechecked all power connections on the Corsair RM850X, which resolved the issue temporarily. However, the drive still wouldn’t work properly, and Windows would often block reading or writing to it. Since reinstalling the M.2 caused performance stuttering, it seems the root cause might be related to the motherboard or power supply rather than just the card itself. I’ve already tried updating drivers, clearing CMOS, and other fixes—any suggestions would be greatly appreciated. Thanks for your time.
You should check the PSU using a voltmeter to see if there’s a problem. If not, it might be the motherboard that’s causing the issue. You could test the second M2 port on the X570 (it fully supports M2 on the chipset lanes) or use a budget PCie adapter card to bypass the problem.
I mentioned using both m.2 connections. It’s odd that they shut down together, suggesting a possible power delivery problem.
The PSU wasn’t changed either. You could easily find a backup unit from friends, family, or online sources like Amazon Prime—test it, and if it doesn’t work, return it.
Great idea. I set up the 450W power supply and everything functioned smoothly, including the M.2 drive. As noted in the original post, the BIOS was showing low voltage which wasn’t a problem with the 450W. To be safe, I took out the custom cable extensions from my 850W unit and saw it no longer reporting low voltage either. Probably the extensions were damaged or affected somehow. Either way, I’m confident this is resolved.