Solved

Windows ChkDsk Logs

Posted on 2014-03-04
2
1,387 Views
Last Modified: 2014-03-04
Hello,
I just need help reading and understanding this. I ran a chkdsk command /f last night and let it run until I got back to the office. Lately this user has logged a bunch of disk errors in the event viewer so I thought this would help. Besides understanding this, I would also like to know if there might be issues with physical sectors on the drive. Below is the report:




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


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

CHKDSK is verifying files (stage 1 of 3)...
  237312 file records processed.                                          File verification completed.
  832 large file records processed.                                      0 bad file records processed.                                        4978 EA records processed.                                              92 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
  307994 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  237312 file SDs/SIDs processed.                                         Cleaning up 62 unused index entries from index $SII of file 0x9.
Cleaning up 62 unused index entries from index $SDH of file 0x9.
Cleaning up 62 unused security descriptors.
Security descriptor verification completed.
  35342 data files processed.                                            CHKDSK is verifying Usn Journal...
Read failure with status 0xc000009c at offset 0x1907aef000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1907afc000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1907afd000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1907afd000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1907afe000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1907afe000 for 0x1000 bytes.
  37661400 USN bytes processed.                                             Usn Journal verification completed.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 232308735 KB total disk space.
 110453356 KB in 192057 files.
    120212 KB in 35343 indexes.
        12 KB in bad sectors.
    348903 KB in use by the system.
     65536 KB occupied by the log file.
 121386252 KB available on disk.

      4096 bytes in each allocation unit.
  58077183 total allocation units on disk.
  30346563 allocation units available on disk.

Internal Info:
00 9f 03 00 c8 77 03 00 a0 69 06 00 00 00 00 00  .....w...i......
c0 81 00 00 5c 00 00 00 00 00 00 00 00 00 00 00  ....\...........
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.


Thank You for looking at this, much appreciated.
0
Comment
Question by:eshiram
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 23

Assisted Solution

by:Patrick Bogers
Patrick Bogers earned 250 total points
ID: 39903375
I'd use the manufacturer's diagnostics to test the drive since this log indicates there is a physical problem with the disk.
0
 
LVL 35

Accepted Solution

by:
Dan Craciun earned 250 total points
ID: 39903380
Windows says you have 3 bad sectors on the drive.
You can further diagnose this using the manufacturer's tools, but I would just replace the drive, since it has a very high chance of failing.

HTH,
Dan
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question