Chkdsk cannot run because the volume is in use by another process

'Chkdsk cannot run because the volume is in use by another process. Would you like to shcedule this volume to be checked next time the system restarts? (Y/N)' -> i typed 'Y' and it shows :

"This volume will be checked the next time the system restarts.

C:\Windoes\system32>_"

the i restart and it back to the black screen which said it checking the file system on C:

But the problem is it didnt do the checking, after it said 'Window will now check the disk' it said this :

"Cannot open volume for direct access.

Autochk cannot run due to an error caused by a recently installed software package. Use the system restore feauture from the control panel to restore the system to a point prior to the recent software package installation.

 

This is kind of what happened to me when i tried to do a Chkdsk or chkdsk /f on my Win7 with a SSD. I think i ran at least one chkdsk on my SSD before without any problems, but i am not sure if i ever ran a chkdsk since i had the SSD. Sometimes i get crash's soon after i come out of sleep, so i wanted to run a chkdsk.

 

Hi Dragon.

Does this command work?

Code:

chkdsk C: /r

Also. I have found that crashing problem after coming out of sleep caused by the SATA controller driver that your system drive is connected to. Is your computer very old?

 

Ime crashing problems after coming out of sleep are caused by different Power Schemes on my Lenovo laptops. There's Lenovo Power Manangement & there's M$ Power Management & unless they're exactly the same crashes happen going into or out of Sleep Mode.

 

My computer is 8 years old. I did not want to try the /r, after i read on internet today that /r might not be necessary with my SSD Drive and could take a long time to run.

 

Maybe i should try a Chkdsk in Safe Mode to see if it works.

 

I have run it with SSDs for years with no ill effects.

I suspected your computer may be getting a bit old.
What controller and driver is your operating system drive connected to? For example, is it a Marvell, Intel or Microsoft controller driver? Check Device Manager.
It is highly unlikely you would be having problems with a Microsoft controller driver.

For older computers when you start getting hardware driver issues, it is a common practice to switch the unsupported driver back to a standard Microsoft driver.

 

I wonder if my RAMDisk is causing problems when i come out of sleep.

 

Intel Controller it looks like.

 

I could try to update the driver in Device Manager.

 

In Windows, try this from an Admin Command prompt...

chkdsk C: /scan

I'm not sure if this is available for Win7. If not, try chkdsk /f from a WinPE.

 

https://www.bleepingcomputer.com/forums/t/583761/system-problems/

 

Dear Dragon1952
If you have an SSD, you don't need to use any chkdsk, especially if you do that, there are two options - it doesn't do anything (if you have a new computer, it will block this feature), but for older computers, your SSD may be completely corrupted after that, and there is no way to fix nothing. chkdsk is only for HDD disks, or mechanical disks.
It cannot repair or check the electronics, it's not for SSD drivers!
The electronics cannot be repaired with a hammer and pliers.

 

@kaljukass - that is not the case. Chkdsk may be run just fine on SSDs. The /f option only checks the validity of the FileSystem structures and the /r feature looks at all the DATA and if it finds it in error (based on feedback from the device itself) it will rewrite it to the disk to eliminate the DATA error.

Chkdsk treats all disks the same whether SSD or HDD...

 

When my computer crashes after coming out of sleep, it always shows some error message about my graphic card, but it goes by so quick that i can't write it down. I then hit enter to do a normal restart, following what the screen tells me. I did install and new version of the card driver in device manager a year ago, but it did not stop the crashing. I also disabled all my shell extensions a year ago, but that did not stop the crashing.

 

You may find these messages in the Event Viewer.

You could try this:

1. Shut down the RAM disk software.
2. Enter sleep mode.
3. Wake-up your computer:

Still having crashes?

Just out of curiosity: May I ask what RAM disk software you are using?

 

RAMDisk

 

I get these all day long in event viewer. It could be related to my graphic card because of

1. CCC stands for Catalyst Control Center, and it’s part of your ATI video card driver package—or to be more specific, it’s part of the utilities bundled along with the drivers, and adds features like customizing your display, or setting hotkeys for different display profiles.
   + System
   - Provider
   [ Name] ACEEventLogSource
   - EventID 0
   [ Qualifiers] 0
   Level 4
   Task 0
   Keywords 0x80000000000000
   - TimeCreated
   [ SystemTime] 2020-07-26T22:30:01.000000000Z
   EventRecordID 131192
   Channel ACEEventLog
   Computer User-PC
   Security
   - EventData
   0000000099: 2020-07-26 18:30:01:959 Unable to obtain Color Correction information, dem status: -2 Error Called by: ATI.ACE.CLI.Aspect.DeviceDFP.Graphics.Runtime.RT_DeviceDFP:arse processID:06560 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceDFP.Graphics.Runtime, Version=3.5.4402.7530, Culture=neutral, PublicKeyToken=90ba9c70f846762e)

 

Dragon, you haven't mentioned your SATA controller driver. For example, is it Marvell?

 

Yes, that's an obvious thing to try. I would have thought that Dragon would have already tried that. Maybe not.

 

In post #9 i did.

 

Sorry, I missed it. What date is the driver?

 

Sometimes i don't get a crash for 2 or 3 days, so i can't just stop one thing after another and wait for the next crash. I did not stop the RamDsk, but i changed the chrome target in the shortcut to default and not for the RAMDsk over a year ago. That did not help so i set the target back to the RAMDsk.

 

8/1/2013

 

All of my crashes show some error message about my graphic card, so i should just have a new card put in. The graphic card that came with the computer blew out after a year or two, so maybe the replacement is bad now but has not completely stopped working like the first one.