Solved chkdsk - cannot open volume for direct access

[sh4dow]

Anything I've found about this relates to dead hard drives or driver issues. I however have no issues aside from chkdsk annoying me.

To explain: I guess Windows didn't take too kindly to the latest BSOD and upon reboot, I got that error for my primary drive. But it boots fine.
Of course it should probably be checked. But... Getting rid of the annoying chkdsk prompt is a much higher priority to me.

Does anybody here know how I could convince chkdsk to either not run or to make it work (I.e. get rid of the direct access issue)?
It is a Crucial m4 SSD by the way and SMART values are perfectly fine.

 

[Kaktussoft]

All disks are accessible? You can create and delete and access files on the filesystems?

In http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

chkdsk/f  C:

that gives the error?

 

[Kaktussoft]

In the elevated command prompt:

fsutil  dirty  query  c:

Is it DIRTY?

 

[sh4dow]

Yes, everything worked just as usual.
No, I did not run chkdsk myself. Windows started running it automatically after a BSOD.

Thanks for the fsutil tip, the dirty bit really was set!
And when googling the meaning and consequences, I came across the following solution suggestion that worked for me:

First, exclude the drive from chkdsk and reboot. Windows will boot without chkdsk prompt:

chkntfs /X C:

Then, force chkdsk myself with the usual command:

chkdsk /f C:

After I did this, chkdsk was able to scan C:, it's not marked as dirty any more and Windows boots without chkdsk again.

 

[Kaktussoft]

Now do:

chkntfs /D C:

To reenable automatic chkdsk in case of disk errors.

Very strange the chkdsk command works ... it's the same that run automatically

 

[sh4dow]

Thanks for making me aware of this, I would've assumed that it was a one-time thing.

It's just

chkntfs /D

though by the way