Checkdisk error "cannot open volume for direct access"

This problem started happening randomly and now I cannot run checkdisk at all on reboot. Basically I cannot run Checkdisk at all on my OS drive because it always says in Windows that it is in use and needs to run the scan on next reboot. After I reboot, the above error message displays (see thread title).

I've ran a virus scan and spyware/adware scans and I'm now pretty sure that it isn't the issue. I've tried disabling all non-essential services in services.msc and disabling all startup items under msconfig.exe, neither of which made any difference.

I'm really beating my head against the wall on this one, I have no idea what the cause is. Any advice appreciated.

edit:

Before anyone refers me to the Microsoft KB, I have Service Pack 2 already and the error is occuring with it installed properly.

 

It seems you can correct the problem by installing SP2.

Here's the info from Microsoft: http://support.microsoft.com/?kbid=823439

 

Try this:
Start> Run> type: chkdsk.exe /f /r and press OK.
The dialog will tell you that it can't run right now - and will ask if you want to schedule a check during the next boot. Answer Yes (Y) and reboot.

Edit: I just thought that the problem might be running from the GUI.

 

It appears he's already done both of those suggestions.

 

Not sure if you want comments or possible solutions.

A few other links that may have a possible solution:

http://www.mcse.ms/archive55-2004-6-811167.html (conflict with Diskeeper or Zone Alarm)

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q180694

http://www.annoyances.org/exec/forum/win2000/1087548926?s

http://www.mytechsupport.ca/index.php?option=com_smf&Itemid=42&topic=3503

http://www.windowsitpro.com/Articles/Print.cfm?ArticleID=14614

 

Try booting into your XP CD and running it from the repair console.

This problem is peculiar and I would interpret it as indicating a potentially very serious underlying problem. I am just guessing, but it seems to me that your inability to run chkdsk is indicating an overwhelming and imminent need to run chkdsk. If you can't run it any other way, take the HD out and install it in another computer THEN run chkdsk.

When you succeed in running it, if it doesn't find anything horrible with your file system (and I am betting that it will show a serious problem) then you need to be looking for bootblock viruses, rootkits in BIOS, or some kind of trojan.

 

It would be a really bad idea to try to install a service pack on a system that had a corrupted file system.

 

Sounds like it was already installed.

Might also try running it from a Diagnostic Setup from MSCONFIG.

 

Diagnostic startup made no difference. I also tried uninstalling my virus scanner in case it was interferring, but it also made no difference. I tried sfc /scannow for the heck of it, but no difference was made and it only replaced a few files from what I could tell.

I was able to run chkdsk from the Windows XP Recovery Console and it fixed a few errors, HOWEVER the original problem of it not being able to acquire the drive at reboot remains unchanged. I'm starting to wonder if this isn't signifying a really nasty nasty virus hiding somewhere like that one guy said.

How does one go about detecting and removing a BIOS virus? My virus scanner before I uninstalled it found no problems on my comp...

 

Try running chkdsk from the repair console, doing a surface scan as well. Could be you have some bad clusters on the HD.

In the unlikely but not impossible event that something is in your BIOS, you'll have to flash the BIOS to get rid of it.

 

I did a surface scan with /R but the problem is still there with regular chkdsk not working at bootup.

 

Do you, by chance, have Spyware Doctor installed on your computer ?

 

Yes I did and removing Spyware Doctor actually did indeed fix the problem, for whatever reason.

Thanks

 

There is a known issue with Spyware Doctor. If you would have deleted the file 'ikhlayer.sys' from c:\windows\system32\drivers, your chkdsk would have worked again.
Glad you're fixed up, though !