Windows – CHKDSK doesn’t complete, can’t clear dirty bit

bad-sectorschkdskhard drivewindows 8.1

At some unknown point, the dirty bit on my C: was set (verified with fsutil), and now chkdsk runs on every boot. However, it always aborts at ~51%, preventing the dirty bit from being turned off. I booted into the Recovery Console and tried almost every chkdsk recovery option (/f, /r, /b), and they all fail some way through. From what I have gathered, this implies that there are sectors that are bad in ways that chkdsk doesn't handle (although those details are obviously unclear).

I tried a Hail Mary suggestion from another site: back up an image of the drive, format, restore the image, but that was ineffective…I used Acronis Backup & Restore, and I suspect it's restoring the problematic sector as well.

I don't think the drive is bad or is going bad. It's a fairly new Crucial mSATA SSD. Best guess, something like a power blip caused the corrupted sector. Otherwise, there are no problems, and everything runs fine.

Any suggestions on what to try next? Since I've successfully round-tripped my backup image, I'd be willing to try just about anything.

Edit: FYI, this is the chkdsk output using any of the repair options:

Stage 2: Examining file name linkage ...

Correcting error in index $130 for file 203615.
An unspecified error occurred (766f6c756d652e63 461).

That's where it ends, and punts me back to the command prompt. I also tried the suggestions I have seen for this error – run Dism and/or sfc – but neither worked.

Best Answer

You should first ensure you have a good backup. Then you should check Crucial's site for any firmware update for your specific drive model which addresses these issues. Also I would recommend running a drive testing utility (manufacturers sometimes provide these but I couldn't find one for the Crucial SSDs) which tests every sector on the physical drive.(for example, Western Digital has their free Data Lifeguard software for testing drives). Don't depend on chkdsk to do this. I would lean toward a failing drive. Again, backup, backup, backup!

Related Question