Is this SSD dead? (pictures)

nate3654

Reputable
Feb 23, 2015
13
0
4,510
It's a sumsung 850 pro about 1 month old, it was working perfectly until yesterday morning when i turned on the computer and it wouldn't boot. In the bios the hard drive just shows as the same
3 c k c k ect. but it shows the remaining 130gb free on the drive.

I installed windows on another hd but it won't boot with the ssd plugged in because the pnpdriver.exe freezes. If i hot swap it with windows running i can find it in the device manager, it calls it a disk drive but i cant do anything with it and cant find it in Disk management.

The computer is a new build and seemed perfectly fine.

Anybody seen anything like this?



Update: Apparently it was the Samsung fimware update that nuked the drive and it's been a know issue for the past week. Samsung has pulled the automatic update and says a fix is coming but for now you can just RMA.
2u7wrrq.jpg
 
Solution
By any chance did you install that latest firmware update Samsung released for the 850 earlier this week? Because if you did it's a near-certainty that's the root of the problem. That firmware update has proven to be defective.
Hey there, nate3654!

I'd suggest to open Command Prompt (Run as administrator) and type in the command: sfc/scannow
This will verify the critical system files and it will attempt to repair them. It might take some time, so be patient.
After it is completed, reboot the computer and let me know what happens! :)

Keep me posted!
SuperSoph_WD
 



Thx for the suggestion but no luck. It says it did not find any integrity violations. I thinks it's probably a lost cause.
 
SSDs typically fail with firmware damage. The model number is reported by the ATA Identify Device command.

I would examine the drive with CrystalDiskInfo and capture both its SMART data and its Identify Device data.

You should be able to generate a text report.
 
By any chance did you install that latest firmware update Samsung released for the 850 earlier this week? Because if you did it's a near-certainty that's the root of the problem. That firmware update has proven to be defective.
 
Solution


Thats probably what happened yeah