CHKDSK Contradictions

gfd · 28 Sep 2014

Greetings

I have just changed my system drive to a Crucial MX100 SSD. I restored a saved image to the new drive. Everything booted up OK, etc. When I booted into Windows, I checked the disk and Windows found no errors. Today, I got a message from Action Center suggesting I run Maintenance. The result suggested I run CHKDSK to repair errors. The results of CHKDSK are below:

CHKDSK in Windows:

Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
Volume label is SysApps.

CHKDSK is verifying files (stage 1 of 3)...
221952 file records processed. File verification completed.
852 large file records processed. 0 bad file records processed. 2 EA records processed. 57 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
274920 index entries processed. Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...
221952 file SDs/SIDs processed. Cleaning up 33 unused index entries from index $SII of file 0x9.
Cleaning up 33 unused index entries from index $SDH of file 0x9.
Cleaning up 33 unused security descriptors.
Security descriptor verification completed.
26485 data files processed. CHKDSK is verifying Usn Journal...
34252824 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

250058068 KB total disk space.
97433480 KB in 112763 files.
80060 KB in 26486 indexes.
333036 KB in use by the system.
65536 KB occupied by the log file.
152211492 KB available on disk.

4096 bytes in each allocation unit.
62514517 total allocation units on disk.
38052873 allocation units available on disk.

CHKDSK After Reboot:

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

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

CHKDSK is verifying files (stage 1 of 3)...
221952 file records processed. File verification completed.
853 large file records processed. 0 bad file records processed. 2 EA records processed. 57 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
274918 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
221952 file SDs/SIDs processed. Cleaning up 34 unused index entries from index $SII of file 0x9.
Cleaning up 34 unused index entries from index $SDH of file 0x9.
Cleaning up 34 unused security descriptors.
Security descriptor verification completed.
26484 data files processed. CHKDSK is verifying Usn Journal...
34296512 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

250058068 KB total disk space.
97107176 KB in 112754 files.
80060 KB in 26485 indexes.
0 KB in bad sectors.
333036 KB in use by the system.
65536 KB occupied by the log file.
152537796 KB available on disk.

4096 bytes in each allocation unit.
62514517 total allocation units on disk.
38134449 allocation units available on disk.

Internal Info:
00 63 03 00 f1 1f 02 00 08 ee 03 00 00 00 00 00 .c..............
63 02 00 00 39 00 00 00 00 00 00 00 00 00 00 00 c...9...........
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 also ran fsutil to check if my C: drive was dirty. It was not dirty.

Any advice would be most appreciated.

Thanks,
Graham

seankurth · 28 Sep 2014

If you just flashed an image from another hard drive, then that's probably it. Windows detected a partition table (and possibly MBR?) that it wasn't used to. It probably thinks that its still on the old drive and perceives the new drive as a corrupted version of the old one. After all, Windows isn't known for being very smart when it comes to hardware and drivers. If your drive really was corrupted, then great, Windows just fixed it for you. But I somehow doubt that.

If the warnings persist, then you can probably safely ignore them or turn off their notifications in action center. If you haven't already, check device manager to see if the drivers for your new drive are properly installed. If Windows thinks its still on the old drive, then the model name and number of that drive will show up there instead of the new one. Just scan for new hardware, install everything, and you're good to go (but DO NOT delete the old driver, even if scan for new hardware finds nothing, this can cause Windows to not boot).

If this turns out to be an issue with your hard drive (and you really can't know that its not), I hope you kept a copy of that system image :) . But as I said, its probably okay. It sounds like Windows fixed whatever it found and you can now ignore the warnings.

TL;DR: Basically, if your computer boots consistently, doesn't crash more than once a month or so, and doesn't show any symptoms of an *actual* corrupt disk like disappearing files or inexplicably failed defrags, you're fine, period.

gfd · 29 Sep 2014

Thanks Sean,

Graham