[RESOLVED] SSD not detected after turning off psu when PC was running

[Brainded]

Hi, so I had turned off my psu when my younger brother had constantly tried to get on my computer. I had the bright idea to turn off the psu while the system was still running. A little while after, I decided to turn the psu on and then I turned the PC on. I was greeted to a bios screen with disc management only showing my hdd. I'm worried that I might have bricked my ssd. Help?

 

Ssd: Samsung 970 Evo 500gb

Motherboard: Asus z97-ar

 

Edit: I would like to mention that the ssd in question is the boot drive of my computer. Every time I try to turn the PC on I'm stuck on a loop of the Asus start screen going into the bios. There's no windows screen. 

[LienusLateTips]

Try reseating your SSD first

[Brainded]

2 minutes ago, LienusLateTips said:

Try reseating your SSD first

Yeah, I took it out and placed it back in. No change 

[Snipergod87]

Do you perhaps have another M.2 slot you can try?  I doubt the Z97 chipset does though.

[Brainded]

8 minutes ago, Snipergod87 said:

Do you perhaps have another M.2 slot you can try?  I doubt the Z97 chipset does though.

No, it's just that one slot

[Brainded]

5 hours ago, Brainded said:

Hi, so I had turned off my psu when my younger brother had constantly tried to get on my computer. I had the bright idea to turn off the psu while the system was still running. A little while after, I decided to turn the psu on and then I turned the PC on. I was greeted to a bios screen with disc management only showing my hdd. I'm worried that I might have bricked my ssd. Help?

 

Ssd: Samsung 970 Evo 500gb

Motherboard: Asus z97-ar

 

Edit: I would like to mention that the ssd in question is the boot drive of my computer. Every time I try to turn the PC on I'm stuck on a loop of the Asus start screen going into the bios. There's no windows screen. 

This wasn't mentioned, but I had reset the bios to default settings. Didn't know why, but I did. That probably had caused the change in "Express Slot and M.2 Bandwidth". I changed it from "PCIeX1..." to "M.2 Mode" and hoped that it would fix it. Turns out it did. I ended up solving my own problem, but nonetheless, thanks for the replies.