Sandisk 256GB SSD dying?

[mxnerd]

Got a Sandisk SSD showing error in event viewer like this.

Block number is different for every error event.

CrystalDisk Info shows completely healthy disk.

Installed Windows 10 & WIndows 8 on same disk and got same errors on same laptop.

If switch to laptop 2.5" disk, then no errors.

The SSD was used on a machine that's rarely used, I moved it to my notebook then found this.

Whats's going on? Is it disk problem or controller problem?

Don't remember where I bought it and don't know where my receipt is.

In Windows 7, it shows this error

 

[mxnerd]

OK.

Pulled this Sandisk SSD and put it into another PC, no disk error or warning at all! No matter which Windows OS it's running.

So apparently it's compatibility problem.

So whose fault is this? Sandisk, HP or Intel?

Chipset is C220, CPU is i3 4000M.

All drivers installed.

 

[UsandThem]

HP.

The motherboard manufacturers add support for drives, RAM, and CPUs with BIOS updates. The problem with OEM PCs and the motherboards they put in them, they usually don't get many updates unless it's security related.

I've owned a few HP machines, and in my opinion, they usually provide the least amount of any kind of updates after a few months of the PCs shipping.

 

[aigomorla]

have you tried using a different sata cable, or using a different sata port?

you'd be amazed sometimes how something tiny like that can cause the issue....

 

[XavierMace]

HP.

The motherboard manufacturers add support for drives, RAM, and CPUs with BIOS updates. The problem with OEM PCs and the motherboards they put in them, they usually don't get many updates unless it's security related.

I've owned a few HP machines, and in my opinion, they usually provide the least amount of any kind of updates after a few months of the PCs shipping.

Sorry, I'm calling BS on that. BIOS's don't "add support" for drives.

I'm more concerned with OP's SMART data showing 75 Petabytes of host reads. That and having 5 partitions on an SSD makes me cry.

 

[UsandThem]

Sorry, I'm calling BS on that. BIOS's don't "add support" for drives.

I'm more concerned with OP's SMART data showing 75 Petabytes of host reads. That and having 5 partitions on an SSD makes me cry.

You can call "BS" on whatever you like. It doesn't mean what I said is incorrect.

Motherboard manufacturer's release BIOS updates to add support for additional SSD/NVMe drives, just like they do for RAM compatibility. It's the same reason they also have QVL lists for SSD/NVMe drives as well (just like RAM).

I can spend more time providing links and stuff, or you can check it for yourself to see that I am not providing "BS".

 

[Iron Woode]

Sorry, I'm calling BS on that. BIOS's don't "add support" for drives.

I'm more concerned with OP's SMART data showing 75 Petabytes of host reads. That and having 5 partitions on an SSD makes me cry.

I call BS on your BS.

BIOS updates add drive support as well as add-in card support, cpu support, ram support, etc.....

also the OP's problem could be the ssd's firmware needs an update.

 

[XavierMace]

NVMe is a different story than SATA which is what we're looking at here. Show me a BIOS update that says it's adding support for specific SATA drives. I also don't recall ever seeing a SATA QVL for a motherboard and a quick check of recent motherboards on Asus and Asrock's sites show no SATA QVL. Common sense would tell you that drives aren't dependent on a BIOS update because if that was the case you'd never be able to use a drive newer than your BIOS. Even if it's possible it's the BIOS, I'd be looking at chipset drives and if the drive is in AHCI or SATA mode first.

 

[UsandThem]

NVMe is a different story than SATA which is what we're looking at here. Show me a BIOS update that says it's adding support for specific SATA drives. I also don't recall ever seeing a SATA QVL for a motherboard and a quick check of recent motherboards on Asus and Asrock's sites show no SATA QVL. Common sense would tell you that drives aren't dependent on a BIOS update because if that was the case you'd never be able to use a drive newer than your BIOS. Even if it's possible it's the BIOS, I'd be looking at chipset drives and if the drive is in AHCI or SATA mode first.

Common sense now? That's really necessary after the earlier BS call-out?

So you're saying that out of all the different SSDs out there (or other SATA devices), no motherboard manufacturer ever had to release a newer BIOS to add support or fix issues for any SSD?

When I have time to waste, I will give you that link you a BIOS update that added support or fixed issues for specific SSDs. And to add a cherry on top, I'll even show the rare occurrence where a particular brand of SSD will not work on certain motherboards period.

 

[XavierMace]

I'm saying I've never seen a BIOS update to support new SATA devices. I'm saying I did a quick search and I don't see any SATA QVL's like you claim. I'm saying that even if you're correct, there's far more likely fixes rather than jumping straight to BIOS.

 

[UsandThem]

I'm saying I've never seen a BIOS update to support new SATA devices. I'm saying I did a quick search and I don't see any SATA QVL's like you claim. I'm saying that even if you're correct, there's far more likely fixes rather than jumping straight to BIOS.

And probably 99% of the time you are correct. All I said is that when there are issues, bugs, or other odd stability problems, the motherboard manufacturers are the ones that generally release a BIOS update to fix it. There was a user on here who could not get a 850 EVO to work in his pre-built Acer. He went back to Best Buy two more times and bought a new 850 EVO each time, and it still didn't work. After coming here, he went back and bought a Sandisk Ultra II if I remember correctly, put it in and it worked fine. Very rare, but it happens. If Intel screws up something with their chipsets (more or less not much an issue anymore since a lot has moved to the CPU), they would release a driver update to fix it.

Heck, going back years and years, I had to do a BIOS update when the LS120 drives were released to get it to work. More recently, MSI had to release a BIOS fix because they did something that affected Samsung 960 users, I believe.

I just was kinda shocked to see the "BS" this morning straight out of bed based on what I said in my original statement, as OEM motherboards found in pre-built PCs like HP receive limited BIOS updates to add new components/features. Heck, I have a barebone HP Z170 system in my closet upstairs that only has BIOS support for only 3 Sky Lake CPUs (i5-7400, i7-6700, and the i7-6700k). It won't boot with any other CPU.

 

[UsandThem]

Here's the fist part: The elusive SSD QVL list.

https://www.gigabyte.com/Motherboard/GA-Z170X-UD5-rev-10#support-doc

 

[XavierMace]

And I was equally shocked straight out of bed to see a moderator jumping straight to "it's HP's fault" when not even the slightest bit of troubleshooting was done.

You've admitted that 99% I'm probably correct. I'll admit that there's that 1% chance that you're correct. However, why go with the 1% chance right out of the gate?

Again CPU's are a completely different story and irrelevant to the topic. But that also ties in to my point. If it's a BIOS level issue, the device generally won't work at all. As is the case in the two examples you gave. His drive is working, he's just getting errors. It could be a driver issue which would be a split between Intel's fault and his for not having the latest drivers. It could be the cable which would be the fault of whoever made his SATA cable. It could be the ATA/ACHI setting which would be his fault. It could be a firmware issue on the drive which would be SanDisk's fault.

 

[XavierMace]

And you've won on finding a SSD QVL. However, you'll note none of the BIOS updates on that board mention adding support for more drives.

 

[UsandThem]

And you've won on finding a SSD QVL. However, you'll note none of the BIOS updates on that board mention adding support for more drives.

I haven't gotten to that part yet. I have other stuff I have to do, so I will add them here once I have more time. I promise they are coming soon.

 

[UsandThem]

And I was equally shocked straight out of bed to see a moderator jumping straight to "it's HP's fault" when not even the slightest bit of troubleshooting was done.

You've admitted that 99% I'm probably correct. I'll admit that there's that 1% chance that you're correct. However, why go with the 1% chance right out of the gate?

Again CPU's are a completely different story and irrelevant to the topic. But that also ties in to my point. If it's a BIOS level issue, the device generally won't work at all. As is the case in the two examples you gave. His drive is working, he's just getting errors. It could be a driver issue which would be a split between Intel's fault and his for not having the latest drivers. It could be the cable which would be the fault of whoever made his SATA cable. It could be the ATA/ACHI setting which would be his fault. It could be a firmware issue on the drive which would be SanDisk's fault.

It could be. But I was just answering it based on my previous experience with extremely limited OEM boards like HP uses. They get no where the amount of BIOS updates like that come from Asus, Gigabyte, MSI, Asrock, etc that fix glitches and other system stability issues.

But yes, it could just be a firmware update that is needed from the SSD manufacturer. He never responded back, so who knows for sure? The difference is if you posted what you did, I still probably would have added my experience with OEM boards, but I wouldn't have called your post "BS".

 

[VirtualLarry]

SATA whitelist/blacklist is less common I think, but it could well be a thing in OEM branded BIOSes. I would be hardly surprised to find them white-listing NVMe SSDs, and we all already know that they whitelist PCI-E wifi cards, such as in OEM branded laptops.

I don't think that the existance of QVL for a board, necessarily means that list is embedded in the BIOS. But, I could be wrong about that, I don't have extensive experience with OEM branded BIOSes, other than they have a lack of options commonly found on custom-built / DIY / white-box mobos.

 

[aigomorla]

I'm more concerned with OP's SMART data showing 75 Petabytes of host reads. That and having 5 partitions on an SSD makes me cry.

Oh wow i completely missed this fact...

OP how old is the drive?
Your SSD should of honestly died 73 Petabytes ago...\

But i find it hard to believe you had that many host reads in a spam of 8790 hours with over 2183 reboots.

And why do you have 5 partitions on such a small drive?

 

[mxnerd]

Oh wow i completely missed this fact...

OP how old is the drive?
Your SSD should of honestly died 73 Petabytes ago...\

But i find it hard to believe you had that many host reads in a spam of 8790 hours with over 2183 reboots.

And why do you have 5 partitions on such a small drive?

Sorry, I didn't know there are so many followups.

I didn't notice that 73 Petabytes read. That's absolutely ridiculous.

The drive is for my dad and he hardly use the computer. He rarely shutdown the computer and computer probably goes into sleep mode after a while. All he did is watching some youtube videos and check weather.

I have no idea why Crystal Disk will report that 73 Petabytes was read. Absolutely nonsense.

The reason I have 5 partition was that I tried to figure out why so many disk warnings/errors once I put it in my HP laptop, so I re-partitioned the disk and install different OS on the disk to see if it makes any differences.

Anyway, after several tries and swapping between the machines, the HP laptop is the only one that exhibits this kind of issues. I have no way to change cables, it's a notebook, all the cables are special designed.

Why the hell Crystal Disk will report that absurd number? I have absolutely no idea. The disk is probably only 3-4 years, very, very light usage.

==

Regarding other member's questioning if the SSD was in AHCI mode, the answer is yes.

==

Just checked Crystal Disk info on the disk, now it says 1440 petabytes has been read.

No warning/errors. (Not HP laptop)

==

Will see if there is firmware update from Sandisk.

 

[Elixer]

I have no idea why Crystal Disk will report that 73 Petabytes was read. Absolutely nonsense.

That comes out to 8.55711649602 TB/hour, which is basically impossible with SATA III speeds.

So, yes, that is a bug in the program for this specific SSD. They must be using different values than what CrystalDiskInfo thinks it is using.

I have seen 4-5 partitions on lots of OEM drives, that isn't anything new, and it won't really harm anything.

The event log errors either mean bad cable (or loose connection with cable), bad SATA port, or the SSD needs a RMA. As for no receipt, if you paid with CC, that usually has a transaction # that you can use at the store you bought it from and they can look up the receipt.

Oh, and as for a BIOS update for SSDs, the only time I have run into such a thing was when there is a 3rd party controller on the mobo (or an external USB device), and they need to update the firmware of that controller. Sure, it is rare, but they do happen.

 

[mxnerd]

Downloaded firmware ISO here and booted from it.

https://kb.sandisk.com/app/answers/...a+-ssd-manual-firmware-update-version-x2316rl

http://downloads.sandisk.com/downloads/ssd/iso/SDSSDH2-256G.iso

Said can't find supported Sandisk devices.

Well. Just have to live with it.

 

[mxnerd]

Now it's completely dead! Not detectable by any PC I have!

Rarely used SSD died so fast by a renowned vendor.

Really don't know if I should trust SSD anymore.

 

[mikeymikec]

Now it's completely dead! Not detectable by any PC I have!

Rarely used SSD died so fast by a renowned vendor.

Really don't know if I should trust SSD anymore.

Because you've had one die. Are you serious?

I've seen one SSD become faulty, and it wasn't one I had sold (or in anything I have sold). I've easily sold enough for any reservations I might have had about 'new' storage tech to go away. SSDs are pretty much standard in anything that isn't a low-end PC, and at least 90% of the computers I build or the laptops I sell have an SSD in. If they were as unreliable as you perceive, do you honestly think that they would have achieved that kind of market penetration?

Furthermore, I'm pretty sure that anyone here who has had a least a few hard drives die will agree that usage has little to do with it.

In the six years I've been using/encountering SSDs in my business I've seen one die. I wonder how many HDDs I've seen die in a similar time frame. A quick count-up suggests I've replaced 13 HDDs in less than the last twelve months. Should they go back to tape instead of forward to SSDs?