help: can't run chkdsk on c:

  • Thread starter Thread starter google_nickname_12345
  • Start date Start date
G

google_nickname_12345

(win XP Version 5.1.2600; NTFS)

Something went wrong when installing a 3rd-party app (Microchip's
MPLab), and I got a BSOD. Since then, I get a "file corrupted ... run
chkdsk" error when I boot.

I tried 'chkdsk /F c:', and answered Yes to "run on next boot?". Then
I rebooted, but it didn't (and doesn't) run. 'chkntfs c:' says the
drive is "dirty". I also tried 'chkntfs /C c:', and again got no
results. I've tried a few ideas from different googled postings (eg:
turn off ZoneAlarm). These too have done nothing, and I'm just
floundering.

What I'd like is a scheme for rationally attacking this problem. Or a
magic bullet.

Thanks,
George
 
(I thought I'd replied, but I don't see it; so, again ...)

During boot, before login, a screen comes up, ...

Checking the file system on c:
The type of the file system is NTFS
Cannot open the volume for direct access
Windows is done checking

A clue?

George
 
dsk1 - 2 partitions:
vol1 (c:) NTFS Boot XP Pro. No dual boot or anything exotic.
vol2 (d:) NTFS
CD drive (e:)
local disk (F:) Single NTFS partition
local disk (G:) Single NTFS partition

I believe I'm current with XP updates.

Googling "Cannot open the volume for direct access", I got a hit that
implicated "CrypKey Software Licensing System version 4.3". I did find
a 'crypkey license' service running, and I think it's from an old app
(Protel 99SE). But, my problem persists even with that set for manual
start only.

George
 
XP Pro, sp2 (from CD)

I'm starting to suspect that the problem is ZoneAlarm. TrueVector
service seems unstoppable, even when ZA is set to not load on boot,
even when its "protect ZA client" is off. I've read that ZA could
cause this problem, but the threads I've seen all refer to v5. (I have
6.1.737.000).

George
 
I uninstalled ZA. Truevector is gone, no vsmon.exe in the task list.
I did a diagnostic boot (tasklist after login ..

System Process (0)
System (4)
smss.exe (444)
csrss.exe (516)
winlogon.exe (540)
services.exe (584)
svchost.exe (740)
svchost.exe (840)
lsass.exe (596)
userinit.exe (1036)
explorer.exe (1060) Program Manager
msconfig.exe (1120) System Configuration Utility
cmd.exe (1168) Cmd - tl t
TLIST.EXE (1180)
)

Anyway, I still get the same results: no chkdsk, "Cannot open the
volume for direct access".

George
 
are you running any AV or disk monitoring programs (diskkeeper)?
have you disabled AV and other 3rd party programs?
Have you tried F8 Safe mode with command prompt only?

Do you have any idea wht these 2 coomands are running?
I know what msconfig is.
What is "tl t" on cmd.exe?
msconfig.exe (1120) System Configuration Utility
cmd.exe (1168) Cmd - tl t

Cannot lock volume for direct access
http://support.microsoft.com/default.aspx?scid=kb;en-us;160654
This error message indicates that Chkdsk or Autochk could not lock the
partition on which you are attempting to run Chkdsk or Autochk. This can
occur if another utility or service (such as a virus checker program or a
disk monitoring program) locks the partition before you attempt to run Chkdsk
or Autochk.
RESOLUTION
To have Chkdsk or Autochk lock the partition and perform their appropriate
tasks, complete the following steps: 1. Click Start, point to Settings, and
then click Control Panel.
2. Double-click Administrative Tools, double click Services, and then change
the Start Type of the other third-party utility to Manual.
3. Click Start, point to Settings, click Control Panel, and then
double-click Devices.
4. Check for third-party devices set to run at startup that might be locking
the volume, and if you locate any, double-click the third-party device, and
then set its startup type to Disabled.

NOTE: If you are unsure if it is safe to disable the device, create a test
hardware profile, and then disable the device in the test hardware If this
does not work, revert back to your original profile. To create a test
hardware profile: a. Click Start, point to Settings, click Control Panel,
and then double-click System.
b. Click the Hardware Profiles tab, click Original Configuration, click
Copy, and then name the profile Test.
You can now disable devices or services in the test hardware profile. To do
so, use the following steps:

a. Click Start, point to Settings, click Control Panel, and then
double-click Services or Devices.
b. Click the service or device you want to disable, click Hardware Profile,
click Test, and then click Disable.
--------------------------------------------------------------------------------
 
are you running any AV or disk monitoring programs (diskkeeper)?

disk monitoring: no, AFAIK

AV: AVG Free. But, its apps (avgamsrv, avgupdsvc) are not running on
the boot I listed.

Do you have any idea wht these 2 coomands are running?
I know what msconfig is. What is "tl t" on cmd.exe?
Click to expand...

Sorry: that's a script of mine. It just runs 'tlist -t'; it's where
the task list came from.

msconfig was running because it pops up automatically when you used it
to do a 'diagnostic boot'.

Cannot lock volume for direct access ...
... Double-click Administrative Tools, double click Services, and then change
the Start Type of the other third-party utility to Manual.
Click to expand...

I used msconfig to set 'diagnostic boot', which disables _all_ services
except DCOM and RPC (confirmed per 'services' window).

... Click Start, point to Settings, click Control Panel, and then double-click Devices.
Click to expand...

I'm not sure where this is. I think that page is about NT? In any
case, I don't have a "Devices" icon on my Control Panel. And I didn't
find anything useful in <system - hardware>.

Again, (a) I'm not aware of any app or service that's _supposed_ to
lock the volume, and (b) I think that <msconfig - diagnostic boot> is
supposed to block all that stuff.

I haven't tried the F8 startup. I'll do that forthwith, and post back.

George
 
(a) I'm having a little trouble with the F8 boot - like, F8 doesn't
seem to have any affect.

(b) Watching the boot, before "starting windows", there's a screen like
....
" ... starting Ontrack
[some clutter ...]
Press [something] to boot from Floppy, Press [something else] to
boot from CD
"

I had assumed this was all part of XP. Maybe it's not? Do you know
what "Ontrack" is? It's not something I added. Maybe it came
pre-configured on the new HDD I used when I installed XP?

George
 
Final outcome: I booted fr the original XP CD, ran the Recovery
Console, and ran 'chkdsk /r c:' from there. I didn't know you could do
that. Thanks for the assistance.

George
 
I had that same problem today and did the same thing, used recovery concole
to run the check. After the Recovery Console check chkdsk started again at
reboot and finished fine. But I found the cause of my 'Cannot Access Drive'
message. I had just installed Spyware Doctor 3.5. There is a driver in the
program, lkhlayer.sys, and it is locking the volume and preventing chkdsk
from running normally. I disabled it from loading at boot up with
Sysinternals Autoruns, and chkdsk ran fine.
I have notified PCTools aboout the problem.
 
Back
Top