19 replies to this topic

[Ax238]

Before we go through any other troubleshooting, let's try running the Check Disk utility:

• Go to Start|Run
• Type cmd and press Enter
• Type chkdsk c: /r and press Enter to run the chkdsk utility (assuming C hard drive letter)
• A reboot is normally required for the chkdsk program to lock the disk and run correctly (this is typical on machines that have only one volume), so simply restart the computer and chkdsk will run automatically. When it's finished, (This process can take quite a while depending on the size of your disk, etc.), it will boot back to normal Windows.
• Repeat steps 1-4 until there are no more errors encountered with the utility
• Repeat steps 1-5 for each hard disk connected to the system, replacing 'c' with the appropriate drive letter in step 3

Also, are there any Save Dump 1001 (Information) or System Error 1003 (Error) entries in the log?

Regards,

Ax

Edited by Ax238, 28 September 2007 - 11:55 AM.

[epictrance73]

i did "c" a few times and its still locked... how will I know when there are no more errors? Do I keep doing it until it is unlocked? Thanks, Paul

[Ax238]

That's why I said you'll probably have to restart your computer after running the command. You'll get a message something like the following:
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)

Type Y, and then press Enter to schedule the disk check, and then restart your computer to start the disk check.

After it finishes, continue to repeat the process until there are no errors encountered.

Regards,

Ax

[epictrance73]

so if it says "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)" I should keep restarting it until it doesn't say that? I have done that 3 times already and it still says this. Just keep diskchecking then? Thanks, Paul

[Ax238]

No, this is just the confirmation window that allows you to schedule the disk checking, not an actual error. You should only continue the process until the actual disk checking utility no longer encounters any errors (this is the process that loads into the blue screen after the computer is restarted). I am pretty sure three runs would be sufficient, but please make sure there are no errors encountered when the utility itself runs.