Chkdsk
This thread is somewhat of a continuation from a prior thread located here: http://forum.acronis.com/forum/10546
I followed Gary's advice to check my disks. I have the following:
- a high end 2 year old desktop Vista computer, including 4 gigs of ram
- two internal hard drives
- Disk 1: C drive - system & software; E drive - documents (everything except media)
- Disk 2: D drive - media content and Acronis backups for C drive
Using Windows Explorer, I went to each of my drives, right mouse clicked to select Chkdsk, checked all the boxes, and then rebooted my computer.
Upon reboot, the computer checked through D drive without difficulty. Then it made its way through E drive without difficulty. And when it got to C drive, the computer's hard drive light went out and computer did nothing for about five minutes. Then I got the BSOD with a message of something about Driver Power State Failure,
I tried the same process again, and this time I only got to the E drive before BSOD.
During the initiation of the chkdsk, I got a message to saying to skip or abort the chkdsk, all I had to do was hit any key. Unfortunately, that did not work. So right now, I can't use the computer because it immediately launches into chkdsk.
Fortunately, I backed up everything the day before. I am planning to have a friend assist on Sunday. I want to start my pc and bypass the chkdsk stuff. I want to retrieve a few files off my desktop and from the local folder before reinstalling my C drive.
I have a hunch that if I were to run chkdsk on each drive individually, I would be fine. I'll find out soon enough.
If anyone has advice, I'd be most appreciative.
The "thing" that usually causes a chkdsk to run is the "dirty bit" for the disk volume. It has to be reset to stop chkdsk from running. Another thing for you to Google.
Thank you for the help.
It seems my first task is to bypass or reset the dirty bit. I think I found the answer here:
http://forums.techarena.in/vista-help/780492.htm#post3005893
To clear the Volume Status "dirty bit" you must successfully run the Microsoft CHKDSK utility with either a /F or /R parameter. This requires exclusive access to the volume.
I can run the CHKDSK utility from the Vista installation disk. I hope this allows me to bypass the hard drive.
Next, if should copy whatever files I want from my C drive to my E or D drives. If the dirty bit is cleared, I can restart and copy away. If there are other problems, I *believe* I can boot from the Vista installation CD and get the command prompt. From there, I can copy whatever files are desired. For instructions on the Vista installation CD, see here:
http://www.bleepingcomputer.com/tutorials/tutorial147.html
And last, I should get my "minidump" file (whatever that is) analyzed to determine the cause of Driver Power State Failure.
Here's a thread discussing Driver Power State Failure and minidump file:
http://www.techsupportforum.com/microsoft-support/windows-vista-windows…
I have no clue what a minidump file is. For Vista, is it located at \windows\minidump folder?
How am I doing? Am I on the correct track?
GroverH, can you please elaborate on your comment, "Check our events log and hope there is some there."?
In the events viewer, when chkdsk is run, you will usually find the results posted there. In XP, is under applications events and winlogon as the source.
In the events viewer, when chkdsk is run, you will usually find the results posted there. In XP, is under applications events and winlogon as the source.
I should have mentioned that I am using Vista. Because the PC is unable to run, I am unable to check the events viewer. Once I get things organized again, I will check.
Thank you.
I've never even thought of running chkdsk on more than one volume. I always do them separately. Now I am glad for that. I prefer doing chkdsk from either a WinPE or BartPE bootable CD (BartPE has a kind of nifty "front end" on chkdsk).
The dirty bit sometime triggers chkdsk at boot when I have a USB hard drive attached that hasn't been chkdsk'd lately..."The volume is dirty.." message on the blue chkdsk screen.
I agree, it is better to do them separately.
I don't know what a WinPE or BartP CD is. Perhaps you can elaborate?
The following are my thoughts that I will pass along to my more knowledgeable friend this afternoon. If you see anything that is amiss, please let me know.
----
*Situation:*
- a high end 2 year old desktop Vista computer, including 4 gigs of ram
- two internal hard drives
- Disk 1: C drive - system & software; E drive - documents (everything except media)
- Disk 2: D drive - media content and Acronis backups for C drive
Currently when PC is booted up, PC begins CHKDSK on Disk 2. After Disk 2 completes, CHKDSK moves to Drive E (BSOD once) and then to Drive C last (BSOD once). It appears that CHKDSK can check Disk 2, but gets stuck on Disk 1. Not sure why that is the case.
At present, PC is caught in an endless loop of reboots and BSODs. The BSOD results from “Driver Power State Failure,” which can mean any number of problems. CHKDSK sets the “dirty bit” and that needs to be cleared or ignored for the PC to function again.
*Desired Outcomes*
- Get computer operational for today.
- Be in a position to submit the relevant files for analysis to determine the root cause once computer is operational. (see Tech Support Forums below – Need to make sure that I have all necessary information for submission)
- Once the root cause has been determined, solve the issue.
*Process*
In formulating my strategy, I have found and relied upon four websites:
1) Acronis: http://forum.acronis.com/forum/10572
2) CompuServe: http://community.compuserve.com/n/pfx/forum.aspx?tsn=10&nav=messages&we… (registration and sign in might be required...have found folks at CompuServe extremely helpful over the years.)
3) Tech Support Forums: http://www.techsupportforum.com/microsoft-support/windows-vista-windows…
4) InfoCellar: http://www.infocellar.com/winxp/chkdsk-and-autochk.htm
Here are the steps I believe I should follow:
1) Verify CMOS and verify that "Legacy USB support" is ENABLED. Otherwise, USBs, mice, and printers are NOT AVAILABLE in Windows until after it loads (not operational in Safe Mode, either)
2) See if the information contained on this page is helpful: http://support.microsoft.com/kb/927392
3) If 2 doesn’t solve the issue, then try to disable CHKDSK by the command: chkntfs /x c: d: e: ( see article http://support.microsoft.com/kb/160963 )
4) If Step 3 fails, use Recovery Environment command prompt to completely back up drives C and E. Use Robocopy (hope robocopy works in Recovery Mode). I backed everything up using Acronis the day before, so I am in reasonably good shape. However, there were some changes that I want to capture AND I want to grab the mini-dump and other files necessary for further troubleshooting. The troubleshooting stuff is important. robocopy C:\ H:\CDrive /COPYALL /E /R:5 /W:15 /DCOPY:T Perform similar command for grabbing drive E.
5) Format drives C and E. As the InfoCellar mentions toward the bottom of the page: What if the Dirty Bit won't go away Method 3) if all else fails - this WILL WORK !! move all the files off the drive, reformat the drive, and then move the files back
6) Using Acronis, put back C drive information from Drive D. I can also add back the few files from my new robocopy backup too.
7) Using Robocopy, put back drive E.
8) Should be back in business with having the PC running.
9) Submit files and information for analysis. Solve whatever is outstanding.
A knowledgeable person from CompuServe suggested skipping step 2 as I don't have a boot issue. Moreover, he suggested:
Ah, the GOOD news: The command prompt is available when booting from the Vista DVD and selecting "Repair" and REGEDIT runs from there! Delete this branch and that will stop Chkdsk from running:HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\BootExecute
I checked both Vista and Windows 7 and if Chkdsk has never been scheduled, that branch does not exist, therefore, deleting it will cause no harm...