Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Ran Chkdsk on Windows 7, what do the results mean?

  • Please log in to reply
3 replies to this topic

#1 Alchemist


  • Members
  • 176 posts
  • Local time:05:25 PM

Posted 16 January 2015 - 12:34 PM

Periodically I run chkdsk on Windows 7 even if I haven't had any crashes just to make sure nothing is corrupting my file system. Well, I got some sort of fixup this time. How can I figure out what might have created this error that Chkdsk fixed? Just to see if I can prevent it happening anymore. Or is it not possible to trace which file this was?


CHKDSK is verifying files (stage 1 of 3)...
  137216 file records processed.                                         

File verification completed.
  417 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  44 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
  188020 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 3)...
  137216 file SDs/SIDs processed.                                        

Cleaning up 326 unused index entries from index $SII of file 0x9.
Cleaning up 326 unused index entries from index $SDH of file 0x9.
Cleaning up 326 unused security descriptors.
Security descriptor verification completed.
  25403 data files processed.                                           

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

Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.



BC AdBot (Login to Remove)


#2 garioch7


    RCMP Veteran

  • Malware Response Instructor
  • 3,853 posts
  • Gender:Male
  • Location:Port Hood, Nova Scotia, Canada
  • Local time:06:25 PM

Posted 16 January 2015 - 12:55 PM

I will be very interested to see what the pros respond with.  I do work on my own and friends' computers and those chkdsk results are not at all unusual in my experience.  I am not knowledgeable enough to know how unused index entries get created, or orphaned, nor do I know the reason why the bitmap gets messed up from time to time.  I have seldom, in my limited experience, seen a completely clean chkdsk report, unless one was run within days of a previous chkdsk run.


Don't know if this is of any help.  Personally, I don't lose any sleep as long as chkdsk repaired any issues that it found.  Have a great day.




Graduate of the Bleeping Computer Malware Removal Study Hall

#3 hamluis



  • Moderator
  • 56,289 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:25 PM

Posted 16 January 2015 - 01:45 PM

In the first place...those results reflect the 3-stage chkdsk that is only done when there is a problem of some sort.


Please run the chkdsk /r command, as directed in the following:  Chkdsk From Command Prompt, Win 7 - http://www.bleepingcomputer.com/forums/t/496613/contextmenu-is-causing-explorerexe-to-crash/?p=3067880 .


Chkdsk is a file tool...that attempts to correct situations in files that may cause Windows to malperform or malfunction.  I see little point in analyzing or trying to understand the details of what was done...all I want to know is that chkdsk tried its best to assist me.


The chkdsk /r command is the most comprehensive (and best) chkdsk command to use, since it does some things that any other version of the command will not. 







#4 Go The Power

Go The Power

  • Members
  • 525 posts
  • Gender:Male
  • Local time:06:55 AM

Posted 17 January 2015 - 02:22 AM

chkdsk is unfornelty one of the Windows functions that is not overlly documented.

One of the main things to look out for is the Bad Sectors these indicate where Windows has found issues on your HDD, from here Windows will block out these bad sectors. Once they have been blocked out, you or Windows will no longer be able to write to that section of the HDD.

Edited by Go The Power, 17 January 2015 - 02:23 AM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users