Just a regular day opening my browser and I get a windows blue screen with UNEXPECTED_STORE_EXCEPTION error. Upon restart, the laptop is stuck at the logo screen with the options to go into BIOS, Recovery Mode and Boot Options. The only option that was working was Recovery Mode.
Once in the settings, under boot options there is no storage device being detected. I checked the NVMe tab and there was no NVMe devices detected as well (laptop comes with 256 NVMe M.2 SSD). Luckily I had planned to upgrade to a 512 SSD and already had one so I switched out the 256 for the 512. The 512 SSD was being detected in the settings as well as the NVMe devices tab.
To check if it was an issue with the SSD itself, I put the 256 SSD in my desktop and booted normally from another drive with the OS. Once logged into windows, I did not see the 256 SSD from the laptop being detected anywhere. I restarted my desktop (with the 256 laptop SSD still connected) and upon restart, my desktop did not load the login screen, similar scenario to my laptop. Once I took out the 256 laptop SSD, everything was back to normal.
While taking the 256 SSD out of my desktop, I noticed the SSD was hot to touch while only being in the desktop for less than 5 minutes. My OS is on another M.2 NVMe 256 SSD and the laptop SSD I took out was much hotter than the one in my desktop. As such, I've come to the conclusion that my laptop SSD was fried.
It has been more than 1 year since the purchase of the laptop and I am not covered by warranty. I believe the data on that SSD is not recoverable. My main concern is whether this issue was due to the SSD itself failing or some issue with the internal hardware of my laptop. I have tried going through power cycles by holding the power button down from start up till it shuts down and starts up again but with no change observed.
If it is a faulty SSD, I am not too concerned as the data I had was regularly backed-up. If it is a faulty laptop connection/hardware, I am hesitant to put another SSD only to have that too fried as well.
Any insight into the cause of the problem and/or solutions for what to do now would be appreciated.
Note: The error occured while on battery power and not plugged into a power outlet/charging