Disk check: all passed bar last item.

Boot tine disk check ran this morning. Everything was pass until last item. From memory ( the dos screen changes so quickly) the failed item was something like C:\ WINDOWS\BCD.

The computer nonetheless seems to run properly, so what is the significance of the failure and what need I do to rectify matter? Please!

Go to Control Panel, select Administrative Tools, and open Event Viewer. Expand the tree on the left to expose the Windows Logs folder and its contents. Select the Applications log and search for a Wininit event. It should contain the chkdsk results.

Chkdsk ran in a benign mode; ran checks as far as it could, display the info it found, but as it could not do any repairs (ready only mode) it could go no further. What it found by that point doesn't look too serious.

Try this: Hold down the Win Start key and press R. A command window should appear. Type chkdsk /r and press enter. You ought to get a message something along the lines of "chkdsk cannot check while the drive is in use" or something like that and then something like "would you like to check on the next start". Press Y to comfirm and press Enter. Reboot, let chkdsk do its job, log back in after the OS boot and check results in the event log.

I think it went much better but it was much more time consuming this time

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 03/07/2012 13:28:16
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Gordon-PC
Description:


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 5)...
381440 file records processed.
File verification completed.
357 large file records processed.
0 bad file records processed.
0 EA records processed.
60 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
435140 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
381440 file SDs/SIDs processed.
Cleaning up 179 unused index entries from index $SII of file 0x9.
Cleaning up 179 unused index entries from index $SDH of file 0x9.
Cleaning up 179 unused security descriptors.
Security descriptor verification completed.
26851 data files processed.
CHKDSK is verifying Usn Journal...
36761552 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
381424 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
134872095 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.

613844991 KB total disk space.
73764368 KB in 122220 files.
87524 KB in 26852 indexes.
0 KB in bad sectors.
504719 KB in use by the system.
65536 KB occupied by the log file.
539488380 KB available on disk.

4096 bytes in each allocation unit.
153461247 total allocation units on disk.
134872095 allocation units available on disk.

Internal Info:
00 d2 05 00 5b 46 02 00 ee 25 04 00 00 00 00 00 ....[F...%......
2c 11 00 00 3c 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.

rundwald said:

I think it went much better but it was much more time consuming this time

More time because it was run in a more thorough mode and was allowed to make repairs. But the results look good, and it appears the file system was in fair shape to start with. If you do it one more time and it runs without having to make any repairs/cleaning then I would call it quits, confirming that the one run was able to fix all that was necessary.

Thanks! :) I'll find my roundtuit.

You're welcome! Post back if it doesn't go as expected. When you get roundtuit!

A much quicker test would be chkdsk without the /r switch. If it comes back errorfree then you know the filesystem is considered to be in good shape. The /r checks/repairs more than just the file system.