Hello, I want to apologize in advance because this will be a little longform. The drive in question is a Samsung 970 EVO Plus 1TB solid state NVMe drive.
Yesterday, while watching Netflix on my PC, Firefox suddenly froze up and then went back to normal. Didn't think anything of it, went to boot up a game and then Steam and Firefox both froze up again. Figured maybe I had my computer on for too long, so I decided to shut it down and start back up. After doing so, I was taken straight to UEFI BIOS. The drive was detected and listed under SSDs (along with both of my HDDs), but it wouldn't show up as my boot drive, which I found weird. Tried pulling the card out of the PC and putting it back in to no avail.
Decided on a whim to try and enable CSM for Legacy and reboot. Upon this, I get a system message telling me that no bootable media was found on the boot drive, and to put boot media on the device and press a key to continue. When I rebooted and went back into BIOS, the drive now shows up as my boot drive but the previous mentioned error persists when I try to boot to Windows. I'm kind of confused as to why this makes my boot drive show up, because it was formatted with GPT and not MBR. Diskpart's disk list reflects this fact.
Figuring something was aloof, I went and made a Windows media USB and popped it in so I could try some things on there in the hopes that it would do something to get me going again. When I try Windows startup repair, it searches for errors for about five seconds and then reports back that it couldn't repair any errors.
Opened command prompt, went to diskpart and everything appears to be in order there. All of my disks show up as online. SMART shows OK all across the board.
Went to run chkdsk, and while it is able to scan and identify issues, the /f /r /x commands don't work. When attempted, the command returns a message stating that it cannot be completed because the drive is write-protected.
When attempting to run sfc, it can identify issues when using the /verifyonly command, but using sfc /scannow reports back that "Windows Resource Protection was unable to complete the request" after it finishes the scan.
Using Diskpart to clear the read-only attribute doesn't work as the issue persists, and I'm not sure what to try to get sfc and chkdsk to work.
There appears to be something wrong with the file system, but I can't figure out what to do to fix it. The only thing I haven't done is attempt to change the read-only value in the registry. I've not attempted to back any of my media up either, as I don't believe I can move any of the data over to a portable drive due to the write protection. Is there anyway I can fix this without having to put in a new SSD?
Any advice would be appreciated.
Yesterday, while watching Netflix on my PC, Firefox suddenly froze up and then went back to normal. Didn't think anything of it, went to boot up a game and then Steam and Firefox both froze up again. Figured maybe I had my computer on for too long, so I decided to shut it down and start back up. After doing so, I was taken straight to UEFI BIOS. The drive was detected and listed under SSDs (along with both of my HDDs), but it wouldn't show up as my boot drive, which I found weird. Tried pulling the card out of the PC and putting it back in to no avail.
Decided on a whim to try and enable CSM for Legacy and reboot. Upon this, I get a system message telling me that no bootable media was found on the boot drive, and to put boot media on the device and press a key to continue. When I rebooted and went back into BIOS, the drive now shows up as my boot drive but the previous mentioned error persists when I try to boot to Windows. I'm kind of confused as to why this makes my boot drive show up, because it was formatted with GPT and not MBR. Diskpart's disk list reflects this fact.
Figuring something was aloof, I went and made a Windows media USB and popped it in so I could try some things on there in the hopes that it would do something to get me going again. When I try Windows startup repair, it searches for errors for about five seconds and then reports back that it couldn't repair any errors.
Opened command prompt, went to diskpart and everything appears to be in order there. All of my disks show up as online. SMART shows OK all across the board.
Went to run chkdsk, and while it is able to scan and identify issues, the /f /r /x commands don't work. When attempted, the command returns a message stating that it cannot be completed because the drive is write-protected.
When attempting to run sfc, it can identify issues when using the /verifyonly command, but using sfc /scannow reports back that "Windows Resource Protection was unable to complete the request" after it finishes the scan.
Using Diskpart to clear the read-only attribute doesn't work as the issue persists, and I'm not sure what to try to get sfc and chkdsk to work.
There appears to be something wrong with the file system, but I can't figure out what to do to fix it. The only thing I haven't done is attempt to change the read-only value in the registry. I've not attempted to back any of my media up either, as I don't believe I can move any of the data over to a portable drive due to the write protection. Is there anyway I can fix this without having to put in a new SSD?
Any advice would be appreciated.