M.2 SSD causing my PC to not post

[Korish]

So today I decided to install the Crucial MX300 525 GB M.2 SSD I got for Christmas into my system. On the first boot it didn't post, and instead went into a weird loop of black screen and then power off then reboot and doing it over and over again. I decided to remove the M.2 and to my surprise, even without it it still 'bootlooped' without posting.
Since then I've tried almost every viable combination of my parts, but I can't get the system to post no matter what. Even the speaker I had laying around gives no beeps after I installed it. The weirdest thing is that I was using the PC just fine earlier, so it almost seems as if the M.2 was like a USB Killer in disguise or something. I'm at a loss of what to do, here's my build if that helps.

CPU: R5 1600
GPU: MSI R9 380
Mobo: ASRock B350M Pro4
RAM: 16GB (2x8) Corsair Vengeance LPX 2400
PSU: Sentey XPP725-HS

Thanks for any help

 

[jr9]

If you can't even get into BIOS with the previous configuration:

Try clearing the CMOS by using the CMOS clear jumper on the board
or removing the CMOS coin battery and then putting it back in
or using the CMOS clear button if your motherboard has one

Do this with the older configuration of course. The goal right now is get into your BIOS settings.

 

[USAFRet]

Which M.2 socket do you have that Crucial drive in?

That is a SATA based drive, and can only be installed in the m.2_2 slot.

 

[Korish]

If you can't even get into BIOS with the previous configuration:
Try clearing the CMOS by using the CMOS clear jumper on the board
or removing the CMOS coin battery and then putting it back in
or using the CMOS clear button if your motherboard has one
Do this with the older configuration of course. The goal right now is get into your BIOS settings.

I reset the CMOS via jumpers and battery replacement, still no luck. When powering on the PC all of the fans and lights start, but there are no beeps, no post, and then the pc powers off, reboots, and starts the process over again

 

[Korish]

Which M.2 socket do you have that Crucial drive in?
That is a SATA based drive, and can only be installed in the m.2_2 slot.

I may have installed the drive into the M.2_1 slot at first and powered on (accidentally), would that be enough to short out the motherboard or something?

 

[marksavio]

well i guess theres no harm in doing the 30-60second rule trick
(unplug all the power cables, usb. switch off psu. hold the power button for a min. put back the power cable and turn on. )

 

[madmatt30]

You'd think that inadvertently putring a sata m2 into a nvme slot would just not work rather than damage anything BUT a lot of boards have dual purpose nvme/sata m2 slots that can switch between either on a hardware level.

The pro 4 though (as youre now fully aware) does not & only asrock know exactly how that circuitry is wired.

I own an mx300 & pro 4 but you'll have to excuse me from not doing a tryout in the nvme slot myself.

If anything had beem shorted it would be on the pci express lanes & it may have inadvertently affected the gpu .

Which slot do yoh have this in? Are you getting any display at all ??

The pro 4 has 2 full size slots , try moving the gpu to the other one.

 

[Korish]

You'd think that inadvertently putring a sata m2 into a nvme slot would just not work rather than damage anything BUT a lot of boards have dual purpose nvme/sata m2 slots that can switch between either on a hardware level.
The pro 4 though (as youre now fully aware) does not & only asrock know exactly how that circuitry is wired.
I own an mx300 & pro 4 but you'll have to excuse me from not doing a tryout in the nvme slot myself.
If anything had beem shorted it would be on the pci express lanes & it may have inadvertently affected the gpu .
Which slot do yoh have this in? Are you getting any display at all ??
The pro 4 has 2 full size slots , try moving the gpu to the other one.

I tried both PCIE slots with the 380 and also thinking that the GPU may have been the issue, I swapped in an old GT430 with still no luck. I don't think my CPU is the culprit, so now I'm pretty sure that the issue lies within the RAM or MOBO. Because I'm not even getting any beeps, the issue is probably with the motherboard. Ordering a replacement soon so we'll see what happens.

 

[SoarinSoars]

I'm having this exact issue Just got a samsung 970 evo, and my * wont post, while using the asrock pro4, I have a new mb comming wensday