What is the best freeware diagnostic for an SSD?

[lenjack]

Title says it all. Windows 10. Thanks in advance.

 

[Phynaz]

The one that came with your drive.

 

[Elixer]

Title says it all. Windows 10. Thanks in advance.

What are you looking to test?
For SMART, I tend to point people to use CrystalDiskInfo (portable version).
For transfer errors, I tend to tell people to archive up 1GB of data (rar, 7z, zip, whatever) then copy that to the SSD, then on the SSD, copy that to itself a few times, then, do a archive check. If it don't fail CRC checks, then that is good.
If you do have transfer errors, then rum memtest86+ overnight, and run occt or whatever on the CPU.

 

[lenjack]

The one that came with my drive is the one I mentioned in my post.

 

[lenjack]

Thanks. i'll look at Crystaldisk.

 

[lenjack]

Just ran Sandisk's extended Smart test, which showed no issues. I think it's a Microsoft issue.

 

[CiPHER]

Never run SMART 'tests'. They aren't any good and actually destroy evidence. SMART is all about the attributes. People want to push a button and then say 'DRIVE FAILED!!!' or 'DRIVE GOOD!!'. But it does not work that way. SMART has to interpreted. Most applications which automate this, do a bad job at it and provide bad advice. So your best option is to post a screenshot of your SMART data and show it to somebody who knows about SMART.

 

[corkyg]

Further, there is no uniform standard for SMART that all makers adhere to. It is at best, a very broad indicator.

 

[lenjack]

This was due to a boot issue that started when the W10 ann update almost bricked my machine. Possibly some good news. System running somewhat better, but still some startup issues. Went back to basics, and did a sfc /scannow, which found and REPAIRED corrupt files. Hoping for complete resolution of problems. Will update in a few days. Probably will suggest this to others.

 

[Elixer]

This was due to a boot issue that started when the W10 ann update almost bricked my machine. Possibly some good news. System running somewhat better, but still some startup issues. Went back to basics, and did a sfc /scannow, which found and REPAIRED corrupt files. Hoping for complete resolution of problems. Will update in a few days. Probably will suggest this to others.

sfc /SCANNOW is *not* a fix.
You want to know *why* they got corrupted in the first place, which is why I said to do those tests.

 

[lenjack]

Agree