How to Read the Event Viewer Log for Check Disk (chkdsk) in Vista, Windows 7, and Windows 8
Information
This will show you how to read the Event Viewer log to see the scan results of Check Disk (chkdsk) in Vista, Windows 7, and Windows 8.
You must be logged in as administrator to be able to open Event Viewer.
Here's How:
1. If you have not already, you will need to have ran Check Disk (chkdsk) in Vista/Windows 7 or Windows 8 prior before it will be in the Event Viewer System log.
2. Press the Windows + R keys to open the Run dialog, type eventvwr.msc, and press Enter.
3. If prompted by UAC, then click on Yes (Windows 7/8) or Continue (Vista).
4. In the left pane of Event Viewer, double click on Windows Logs to expand it, then right click on Application and click on Find. (see screenshot below)
5. Copy and paste Chkdsk into the line, and click on Find Next. (see screenshot below) NOTE:You can continue to click on Find Next to search for other older application logs (if available) for Check Disk (chkdsk) to see them as well.
6. You will now see the system log for the scan results of Check Disk (chkdsk). (see screenshot below) NOTE:The log will have the Chkdsk tag if Check Disk is ran only from within Windows.
7. Go back to the top of the log file list in the middle pane of Event Viewer, then copy and paste Wininit into the line, and click on Find Next. (see screenshot below step 5) NOTE:You can continue to click on Find Next to search for other older application logs (if available) for Check Disk (chkdsk) to see them as well.
8. You will now see the system log for the scan results of Check Disk (Wininit). (see screenshot below) NOTE:The log will have the Wininit tag if the computer has to restart to run Check Disk at startup instead of within Windows.
9. When finished searching for Check Disk (chkdsk) application logs, you can close the Find window. (see screenshot below step 5)
Hey Brink you're a legend mate I have been trying to find out 1) how to read the event viewer and 2) what my chkdsk's have come up with.
My local forum doesn't have such brilliant tutorials laid out like this format and I am one of those who need either an analogy or something like this to get it into the little bit of grey matter that's left you make it look so easy for silly old buggas like me
Thanks for the tutorial. It enables me to illustrate but not solve my problem. The log found is
CHKDSK is verifying files (stage 1 of 3)... 207616 file records processed. File verification completed. 185 large file records processed. 0 bad file records processed. 2 EA records processed. 109 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 283042 index entries processed. Index verification completed. CHKDSK is scanning unindexed files for reconnect to their original directory. Recovering orphaned file Chkdsk20110703093010.log (68213) into directory file 68197. Recovering orphaned file Chkdsk20110709165629.log (68214) into directory file 68197. Recovering orphaned file Chkdsk20110714133433.log (68215) into directory file 68197. Recovering orphaned file Chkdsk20110722172351.log (68216) into directory file 68197. Recovering orphaned file Chkdsk20110722173123.log (68217) into directory file 68197. Recovering orphaned file Chkdsk20110725194533.log (68218) into directory file 68197. Recovering orphaned file Chkdsk20110727084051.log (68219) into directory file 68197. Recovering orphaned file Chkdsk20110727120925.log (68220) into directory file 68197. Recovering orphaned file Chkdsk20110805083128.log (77448) into directory file 68197. 10 unindexed files scanned. Recovering orphaned file Chkdsk20110806090816.log (77450) into directory file 68197.
Unfortunately I cannot find file directory 68197: and when I run chkdsk again at the next boot chkds does the same thing. So I conclude it is NOT infact clearing the orphans. What more should I do or just leave it?
System Manufacturer/Model Number ACPI Multiprocessor PC OS Win 7 Ultimate SP1 CPU CPU Type QuadCore Intel Core i7 960, 3333 MHz (25 x 133) Motherboard Motherboard Name Asus P6T (2 PCI, 1 PCI-E x1, 3 PCI-E x16, Memory DIMMS: Kingston 99U5458-001.A00LF 6 GB DDR3-1333 DDR3 SDRAM Graphics Card Video Adapter NVIDIA GeForce GTX 480 (1536 MB) Sound Card Audio Adapter Realtek ALC1200 @ Intel 82801JB ICH10 - High D Monitor(s) Displays Monitor Hannstar HZ281H [28" LCD] (015LM3AY00458) Screen Resolution 1920X 1200
Keyboard Logitech HID-Compliant Keyboard Mouse Logitech HID-compliant TrackMan Wheel Mouse PSU APC 650 Case GameMaster Cooling 8 fans Hard Drives 586GB Western Digital WDC WD6000HLHX-01JJPV0 ATA Device (SATA)
1954GB Western Digital WDC WD20EARS-00MVWB0 ATA Device (SATA)
586GB Western Digital WDC WD6000HLHX-01JJPV0 ATA Device (SATA) Internet Speed Enabled via DHCP 30mbs Other Info Optical Drives
HL-DT-ST BD-RE BH10LS30 SCSI CdRom Device
Iomega RRD2 SCSI CdRom Device
ASUS DRW-20B1LT ATA Device
Yes but it is very annoying I have the same problem. I suspect Casper as the drive was cloned and re-created using Casper when the errors started appearing. Thye always relate to Chkdskxxx.log files.
Information
