What's the Significance of These CHKDSK Errors?


  1. Posts : 7,909
    Windows 11 Pro 64 bit
       #1

    What's the Significance of These CHKDSK Errors?


    I had a BSOD on shutting down my desktop PC yesterday and the PC hung when trying to reboot. The PC booted OK when I powered it off and restarted. There was no error dump file produced. I ran chkdsk c: /f to check my SSD system drive which detected and corrected errors in the security descriptors as shown below. What's the significance of these errors and why do they arise?

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

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

    Stage 1: Examining basic file system structure ...
    591616 file records processed.
    File verification completed.
    19402 large file records processed.
    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    2219 reparse records processed.
    744648 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    2219 reparse records processed.

    Stage 3: Examining security descriptors ...
    Cleaning up 6641 unused index entries from index $SII of file 0x9.
    Cleaning up 6641 unused index entries from index $SDH of file 0x9.
    Cleaning up 6641 unused security descriptors.
    CHKDSK is compacting the security descriptor stream
    Security descriptor verification completed.
    76517 data files processed.



    CHKDSK is verifying Usn Journal...
    40749704 USN bytes processed.


    Usn Journal verification completed.
    Correcting errors in the Volume Bitmap.

    Windows has made corrections to the file system.

    No further action is required.

    174768204 KB total disk space.
    52528568 KB in 335203 files.
    201180 KB in 76520 indexes.
    0 KB in bad sectors.
    710588 KB in use by the system.
    65536 KB occupied by the log file.
    121327868 KB available on disk.


    4096 bytes in each allocation unit.
    43692051 total allocation units on disk.
    30331967 allocation units available on disk.


    Internal Info:
    00 07 09 00 e5 47 06 00 88 7f 0b 00 00 00 00 00 .....G..........
    65 05 00 00 46 03 00 00 00 00 00 00 00 00 00 00 e...F...........


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


  2. Posts : 8,114
    windows 10
       #2

    There are 2 sorts of errors hardware were you have bad sectors on the drive and file system errors which you have got these are caused most often when things are in memory and dont get written back to disk due to a crash there is nothing wrong with the hd
      My Computer


  3. Posts : 19,518
    W11+W11 Developer Insider + Linux
       #3

    Steve C said:
    I had a BSOD on shutting down my desktop PC yesterday and the PC hung when trying to reboot. The PC booted OK when I powered it off and restarted. There was no error dump file produced. I ran chkdsk c: /f to check my SSD system drive which detected and corrected errors in the security descriptors as shown below. What's the significance of these errors and why do they arise?

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

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

    Stage 1: Examining basic file system structure ...
    591616 file records processed.
    File verification completed.
    19402 large file records processed.
    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    2219 reparse records processed.
    744648 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    2219 reparse records processed.

    Stage 3: Examining security descriptors ...
    Cleaning up 6641 unused index entries from index $SII of file 0x9.
    Cleaning up 6641 unused index entries from index $SDH of file 0x9.
    Cleaning up 6641 unused security descriptors.
    CHKDSK is compacting the security descriptor stream
    Security descriptor verification completed.
    76517 data files processed.



    CHKDSK is verifying Usn Journal...
    40749704 USN bytes processed.


    Usn Journal verification completed.
    Correcting errors in the Volume Bitmap.

    Windows has made corrections to the file system.

    No further action is required.

    174768204 KB total disk space.
    52528568 KB in 335203 files.
    201180 KB in 76520 indexes.
    0 KB in bad sectors.
    710588 KB in use by the system.
    65536 KB occupied by the log file.
    121327868 KB available on disk.


    4096 bytes in each allocation unit.
    43692051 total allocation units on disk.
    30331967 allocation units available on disk.


    Internal Info:
    00 07 09 00 e5 47 06 00 88 7f 0b 00 00 00 00 00 .....G..........
    65 05 00 00 46 03 00 00 00 00 00 00 00 00 00 00 e...F...........


    Windows has finished checking your disk.
    Please wait while your computer restarts.
    You can sleep now, all's super.
      My Computers


  4. Posts : 11,247
    Windows / Linux : Arch Linux
       #4

    Hi there
    This can often be caused by removing for example external USB drives before all I/O has completed and quiesced which is why you should always use the eject hardware icon (usually at bottom right of your windows desktop on the quick launch taskbar) and wait until it says "safe to eject hardware".

    If you have a linux live distro and can mount the relevant disk you might also see message "Windows wasn't shut down cleanly on this drive ... fixing" which does a similar job to the chkdsk function -- "you pays your money and takes your choice....."

    same can happen if Windows stalls or you restart without an orderly shutdown.

    This is why decent modern file systems (unlike NTFS) are journalised so you can't normally break them this way as any broken chains etc are rebuilt from the journals when the system restarts again -- however it's always good practice to ensure HDD's etc are quiesced before removing them from a system.

    Cheers
    jimbo
      My Computer


  5. Posts : 5,048
    Windows 10/11 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #5

    Hi Steve -

    I would run it again like this - system will need to reboot - keep an eye on the verbose output -

    CHKDSK C: /F /V

    After reboot:

    SFC /SCANNOW

    If both come back clean, leave it alone.

    FWIW.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:41.
Find Us




Windows 10 Forums