CHKDSK on SSD

I realize this thread is ancient, but it did pop up high in a Google search for "chkdsk on SSD", so I thought I'd add my two cents...

A couple of days ago, upon waking from sleep, my HP/Compaq laptop threw an error message in the Systray that Windows could not identify a device connected to the SATA controller...rebooting ended up in a BSOD when Windows 7 started to load, so I removed the DC power supply & battery, pressed the power button for 20-30 seconds, then re-inserted battery & charger...then again powered the laptop.

Windows Startup Repair offered to run, so I accepted, but it quickly decided it could not detect or repair any problem(s), so I let it start Windows normally & was relieved to see my Desktop after only a short delay.

I'd installed my Crucial BX100 250GB SSD about 8 months ago to replace a failing 3-year-old Hitachi spinner the laptop shipped with -- I figured the BX100 was now following suit.

So I then downloaded & installed Crucial's "Storage Executive" SSD management software, which is a web browser-based utility which oddly seems to run on Java...wow, Java in 2016?

After allowing for a reboot so the utility would fully recognize the drive, Storage Executive reports my BX100 is "in good health", it has the latest firmware, & though SMART monitoring will only open correctly sporadically (SE sometimes reports: "Drive Drive0 details cannot be retrieved at this time.
Reason: Not a valid / supported drive) when SMART DOES open, I see no red flags...no readings look bad or even marginal...

So, looong story short, I don't know yet whether the drive is pooping out or it was some transient glitch -- it could even be my motherboard's SATA controller, who knows?

Getting back to chkdsk...after the SATA failure, the laptop was acting a bit strangely, lagging, slow in opening applications, so I figured maybe try chkdsk...below is the Wininit report from that run of chkdsk:



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 3)...
Read failure with status 0xc0000185 at offset 0xc1d3a000 for 0x1000 bytes.
File record segment 29928 is unreadable.
Read failure with status 0xc0000185 at offset 0xc1d3a000 for 0x1000 bytes.
File record segment 29929 is unreadable.
Read failure with status 0xc0000185 at offset 0xc1d3a000 for 0x1000 bytes.
File record segment 29930 is unreadable.
Read failure with status 0xc0000185 at offset 0xc1d3a000 for 0x1000 bytes.
File record segment 29931 is unreadable.
205824 file records processed. File verification completed.
523 large file records processed. Read failure with status 0xc0000185 at offset 0xc1d3a000 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc1d3a400 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc1d3a800 for 0x400 bytes.
Read failure with status 0xc0000185 at offset 0xc1d3ac00 for 0x400 bytes.
4 bad file records processed. 0 EA records processed. 45 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
Index entry msmmsp.dll of index $I30 in file 0x2bc5 points to unused file 0x74e8.
Deleting index entry msmmsp.dll in index $I30 of file 11205.
Index entry msmpeg2adec.dll of index $I30 in file 0x2bf5 points to unused file 0x74e9.
Deleting index entry msmpeg2adec.dll in index $I30 of file 11253.
Index entry MSMPEG~1.DLL of index $I30 in file 0x2bf5 points to unused file 0x74e9.
Deleting index entry MSMPEG~1.DLL in index $I30 of file 11253.
Index entry MSMPEG2ENC.DLL of index $I30 in file 0x2bf7 points to unused file 0x74ea.
Deleting index entry MSMPEG2ENC.DLL in index $I30 of file 11255.
Index entry MSMPEG~1.DLL of index $I30 in file 0x2bf7 points to unused file 0x74ea.
Deleting index entry MSMPEG~1.DLL in index $I30 of file 11255.
Index entry msmpeg2vdec.dll of index $I30 in file 0x2bf8 points to unused file 0x74eb.
Deleting index entry msmpeg2vdec.dll in index $I30 of file 11256.
Index entry MSMPEG~1.DLL of index $I30 in file 0x2bf8 points to unused file 0x74eb.
Deleting index entry MSMPEG~1.DLL in index $I30 of file 11256.
Read failure with status 0xc0000185 at offset 0xfc0bd000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xfc0bd000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0xfc0bd000 for 0x1000 bytes.
The index buffer at VCN 0x0 of index $I30 in file 0x1397d
cannot be read.
Correcting error in index $I30 for file 80253.
The index bitmap $I30 in file 0x1397d is incorrect.
Correcting error in index $I30 for file 80253.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 68 e9 8e cb 06 1e d1 01 ........h.......
6d ff b4 cb 06 1e d1 01 6d ff b4 cb 06 1e d1 01 m.......m.......
Sorting index $I30 in file 80253.
260886 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file PACKAG~1.XML (80377) into directory file 80253.
Recovering orphaned file PackageInfo.xml (80377) into directory file 80253.
Recovering orphaned file sign.cat (80378) into directory file 80253.
Recovering orphaned file DEVICE~1 (80406) into directory file 80253.
Recovering orphaned file DeviceInformation (80406) into directory file 80253.
4 unindexed files scanned. Recovering orphaned file WINDOW~1 (80419) into directory file 80253.
Recovering orphaned file WindowsInformation (80419) into directory file 80253.
0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
205824 file SDs/SIDs processed. Cleaning up 185 unused index entries from index $SII of file 0x9.
Cleaning up 185 unused index entries from index $SDH of file 0x9.
Cleaning up 185 unused security descriptors.
Security descriptor verification completed.
27532 data files processed. CHKDSK is verifying Usn Journal...
36719616 USN bytes processed. Usn Journal verification completed.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
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.

224034815 KB total disk space.
48451472 KB in 110360 files.
70416 KB in 27533 indexes.
8 KB in bad sectors.
315635 KB in use by the system.
65536 KB occupied by the log file.
175197284 KB available on disk.

4096 bytes in each allocation unit.
56008703 total allocation units on disk.
43799321 allocation units available on disk.

Internal Info:
00 24 03 00 b0 1a 02 00 b4 f8 03 00 00 00 00 00 .$..............
cb 01 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 ....-...........
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.


I think this answers whether chkdsk can be useful with an SSD drive (yes, only the "f" (fix file system errors) flag, not the "r" (scan & repair all sectors) flag or checkbox enabled)...

And yeah, it's wait & see whether the Crucial drive is going bad, that's an awful big bunch of screw-ups in the above report, but for now the drive & Windows are behaving normally again...it NEEDED the Check Disk...& so much for "automatic, on-board" error detection & correction (notice chkdsk marked two clusters as bad)...and the BX100 is a well-regarded, fairly modern design...