what to do if HDD fails Short DST test? (Seagate tools log and chkdsk log in description)

harshmishra19898

Prominent
Jan 1, 2018
8
0
510
Recently Google Chrome was frequently not responding ,Games stuttering after playing for an hour (guess Cpu needs new thermal paste) and I had 2 Invalid kernel handle BSOD which went away from video driver reinstall,Still I was suspected of corrupted files so i ran sfc scannow in admin cmd which said Windows found some corrupt files but was unable to fix them ,
Then I ran Seagate tools SMART test and short DST test(log below)
then Chkdsk on C(log below)
VOLUME C IS CLEAN
what should i further do
Please Comment for more clarification required from my side,Thank you

Seagate Tools Log -
9/5/2015 8:22:53 PM
Model Number: ST1000DM003-1CH162
Serial Number: Z1DBKZEG
Firmware Revision: CC47
Identify - Started 9/5/2015 8:22:53 PM
Identify - Started 9/5/2015 8:27:12 PM
SMART - Started 9/5/2015 8:28:08 PM
SMART - Pass 9/5/2015 8:28:13 PM
Short DST - Started 9/5/2015 8:28:39 PM
Short DST - FAIL 9/5/2015 8:28:46 PM
SeaTools Test Code: E196DEE6
SMART - Started 9/5/2015 8:33:45 PM
SMART - Pass 9/5/2015 8:33:51 PM
Identify - Started 9/6/2015 1:42:10 PM
Short Generic - Started 9/6/2015 1:42:56 PM
Short Generic - FAIL 9/6/2015 1:43:19 PM
SeaTools Test Code: E196DEC6
SMART - Started 1/12/2018 6:42:42 PM
SMART - Pass 1/12/2018 6:42:47 PM
Identify - Started 1/12/2018 6:43:37 PM
Short DST - Started 1/12/2018 11:10:26 PM
Short DST - FAIL 1/12/2018 11:10:33 PM
SeaTools Test Code: E196DEE6
Identify - Started 1/16/2018 10:49:45 PM

CHKDSK LOG-


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
528384 file records processed. File verification completed.
668 large file records processed. 0 bad file records processed. 2 EA records processed. 61 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
639122 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
528384 file SDs/SIDs processed. Cleaning up 1138 unused index entries from index $SII of file 0x9.
Cleaning up 1138 unused index entries from index $SDH of file 0x9.
Cleaning up 1138 unused security descriptors.
CHKDSK is compacting the security descriptor stream
55370 data files processed. CHKDSK is verifying Usn Journal...
36202424 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x2a1ceb0000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x2a1ceb2000 for 0x1000 bytes.
Windows replaced bad clusters in file 316828
of name \Users\pc\AppData\Local\Temp\C0729E~1.TMP.
528368 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
8247115 free clusters processed. Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

307096575 KB total disk space.
273197928 KB in 472094 files.
270124 KB in 55373 indexes.
12 KB in bad sectors.
640051 KB in use by the system.
65536 KB occupied by the log file.
32988460 KB available on disk.

4096 bytes in each allocation unit.
76774143 total allocation units on disk.
8247115 allocation units available on disk.

Internal Info:
00 10 08 00 74 0c 08 00 99 30 0f 00 00 00 00 00 ....t....0......
32 14 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 2...=...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.















 
Solution
I have never seen a drive fail either the short or long DST that was not bad unless there was a faulty power supply issue or a bad cable causing the test to be flawed. If the PSU is good and the cables are good, and the test result is fail, then IMO the drive is bad.

I suppose it's possible for a faulty storage controller on the motherboard to MAYBE cause a faulty test result, but I personally have never seen that happen. Usually when the storage controllers have issues, the drive either cannot be tested or just doesn't show up at all.
I have never seen a drive fail either the short or long DST that was not bad unless there was a faulty power supply issue or a bad cable causing the test to be flawed. If the PSU is good and the cables are good, and the test result is fail, then IMO the drive is bad.

I suppose it's possible for a faulty storage controller on the motherboard to MAYBE cause a faulty test result, but I personally have never seen that happen. Usually when the storage controllers have issues, the drive either cannot be tested or just doesn't show up at all.
 
Solution