SSD drive failed DST test, but now it passes

digityzed

Distinguished
Mar 27, 2006
153
0
18,690
After a laptop started having issues booting Windows 7, I ran its built-in diagnostics and it reported the factory installed SSD failed the short DST test. I cloned the SSD to a brand new SSD (old SSD to disk image, disk image to new SSD), but continued to have booting issues. I assume whatever hardware failure the old SSD had had corrupted some system files, I tried to isolate which ones with little to no luck, but somehow managed to get Windows Update to install the free Windows 10 upgrade. The laptop now boots reliably and runs beautifully with the new SSD and new Windows 10 installation (I assume it's because Windows 10 carries over little to no Windows 7 system files). Curiosity got the best of me so I cloned the new SSD to the old SSD (via a dual bay SATA to USB duplicator dock), popped the old SSD back in the laptop and low and behold it now passes the short and long DST test... any explanation on why it now passes?

P.S. - The old SSD also passed the short DST test in HD Sentinel.

 

digityzed

Distinguished
Mar 27, 2006
153
0
18,690


Hmmm... I figured that may be the case too for the Windows 7 freezing problem, but can corrupt files cause the drive to fail a short DST test? I imagine there has to be something physically wrong with the drive to trigger a DST failure and removing something on the software side doesn't cure a hardware failure... right?
 
Not necessarily. If any of the code used to report the DST results back to the software that displays the results is corrupted it may not be returning the expected values and is thus interpreted incorrectly when the result is displayed. So there may not be an error in the DST but one is being shown because of the misinterpretation.