Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Chckdsk problem


  • Please log in to reply

#1
StoneSoul

StoneSoul

    New Member

  • Member
  • Pip
  • 9 posts
Here's my problem. One day I turned on my computer, chckdsk wanted to scan my C: drive, my windows drive, didn't know why, since I turned off my comp perfectly fine. But anyway, I let it, but the problem was, it stuck on 0% scan. So everytime my comp boots up, it wanna scan C: first, but get stuck at 0% and never moves, I've tried waiting for ages, and scanned my drive in Windows, but nothing works, it still wanna scan my drive on boot, but can't. What is the problem here? Thank you for any assistance.
  • 0

Advertisements


#2
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Oh, some additional information. I've installed avast antivirus, and it was after a session of boot up virus scan, that this problem appeared.
  • 0

#3
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Follow these steps:
(Note: I have used a variable x, which is the drive letter(s) for which chkdsk performs scan on boot)

1) Open cmd.
2) Type fsutil dirty query x:. Press Enter
3) If it says "Volume X: is dirty", run a manual chkdsk x: /f scan at that instant.

Reboot after u have followed the above steps for all x:

Edited by darth_ash, 23 July 2005 - 06:35 AM.

  • 0

#4
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Followed your steps above, and here's what happened. It said C: was damaged or dirty, I got norwegian windows so I'm not sure if damaged as it says here, would mean dirty in an english windows, anyhow, I then ran your command, it said it could not lock the drive, because the volume was in use by another process, then I got the question if I would check my drive on next start up, I pressed yes, I rebooted, and chkdsk started, and scanned C: fine ;) but here's what's weird, when it was done, and everything was fine with C:, chckdsk wanted to scan C: again, 30 seconds after the last scan, and locked itself at 0%, as before :tazz:
  • 0

#5
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Open regedit. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and tell me the value of BootExecute string
  • 0

#6
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Here's the BootExecute string: autocheck autochk *
  • 0

#7
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Temporarily change that value to autocheck autochk /k:c *
Afterwards repeat the steps in Post#3 again, but instead of chkdsk c: /f try chkdsk x: /f /x.
(Note:The extra "/x" switch.)

After the above steps, change the registry value(BootExecute) back to autocheck autochk * no matter whether the above steps succeed or fail.
  • 0

#8
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Did what you said, when I now ran the fsutil dirty query C:, my C: drive was NOT dirty/damaged. Repeated everything in post 3, and the chkdsk scan that stopped at 0% was gone :tazz:

Changed back the BootExecute string, but will it now return?
What might have caused this? I'm a bit curious ;)
  • 0

#9
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
U will have to change it back. Otherwise, if all anytime u get a genuine problem with C:, chkdsk wont be run for C:.
  • 0

#10
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Yeah I changed it back to autocheck autochk *
But will this mean I will HAVE to skip the chkdsk everytime I boot my comp? Because I can't tell the difference between the chkdsk that scan my drive from the one that locks up at 0%
  • 0

#11
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
After changing the value back, reboot and see if the problem persists.
How can u tell which one is going to lock up, b4 u allow it to scan?
  • 0

#12
StoneSoul

StoneSoul

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Problem is still there :tazz: I reboot, scan stops at 0% and never moves. This is a big problem, if I ever get a genuine problem with that drive, and it wanna scan it, I'm gonna think it's the one that locks up, and I skip it. Frustrating....
  • 0

#13
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Maybe ur disk has some physical errors.
Run chkdsk /r from the WinXp Recovery Console to check for physical errors
(Note the /r switch)
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP