I would just contribute this additional information about chkdsk after answering the same questions many times:
Here is some more info on chkdsk I came up with trying to understand why somebody's chkdsk kept reporting different things, sometimes nothing and sometimes different things.
If you run chkdsk from a command prompt while Windows is running, it may report errors or it may not report errors and it may report different errors each time you run it.
Here is how Microsoft explains this observation:
...CHKDSK may report that a disk is corrupted even when there is no
real corruption present. This can happen if NTFS happens to modify
areas of the disk on behalf of some program activity that CHKDSK is
examining at the same time. To verify a volume correctly, the volume
must be in a static state, and the only way to guarantee that state is
to lock the volume. CHKDSK only locks the volume when /F or /R (which
implies "F") is specified. Thus, you may need to run CHKDSK more than
once to get it to complete all stages in read-only mode. http://support.microsoft.com/kb/187941
So if you are running chkdsk from a command prompt in XP, you are not in the static state required and you may see errors "when no real corruption is present".
Two ways to be sure you are in a static state is to run chkdsk from the Recovery Console or to schedule a chkdsk to run the next time the system restarts by appropriately answering the question:
Would you like this volume to be checked the next time the system restarts?
If chkdsk reports any errors while running in a static
state, the errors should be investigated, resolved or explained. It may take multiple executions for chkdsk to resolve all issues and some issues may not be resolved by chkdsk. I would not discount any other errors, but I will always run in a static state if things look the least bit peculiar.
If chkdsk runs the next time the system is rebooted on restart, the activity and result will show up in the Application Event Log. Look in the Application log for events sourced by Winlogon and that have the date and time close to the time chkdsk was run for the results.
I'll throw in Page Defrag to add to the chkdsk understanding in case those kinds of questions ever come up:http://technet.microsoft.com/en-us/sysinte...s/bb897426.aspx