New
#11
That's what I'm trying to figure out here. On boot, I either get the black screen with c0000001 error or it just boots directly to recovery console.
Can't run Sfc /scannow
-
-
-
New #13
@Carwiz, Yes, it recognizes the primary disk.
-
New #14
I have a hunch that if I could run sfc /scannow on the drive, it would fix it. Booting from the OS disc didn't let me do it trying with the normal and offboot method. Even plugging the drive into another Windows 7 machine, running cmd as admin I can't run it on this drive. The closest I get is running:
sfc /scannow /offbootdir=c:\ /offwindir=f:\windows\
where C is a good, working Windows 7 drive and F is the messed up one, I get the following message, "Windows Resource Protection could not start the repair service.
If only there was a way to run a repair install on a slave drive.
-
New #15
See if you can execute this command in an elevated prompt.
fsutil dirty query c:
Added: When you tried to boot from the c: drive, do you get the Windows 7 startup screen or does it die before that?Last edited by carwiz; 27 Apr 2014 at 00:08. Reason: Addition
-
New #16
Running fsutil from recovery console gave me the "not recognized" error. But when I ran it from another working computer on this bad drive the command said the drive was not dirty.
When I boot, it appears to boot directly to recovery console. If I boot to Safe Mode the Starting Windows screen stays up for a half a second then stops around the 4th or 5th dll, I think kdcom.dll, then jumps directly to the recovery console.
Thanks for your assistance and patience, Carwiz.
-
-
New #18
Maybe you missed what I wrote?
"Even plugging the drive into another Windows 7 machine, running cmd as admin I can't run it on this drive. The closest I get is running:
sfc /scannow /offbootdir=c:\ /offwindir=f:\windows\
where C is a good, working Windows 7 drive and F is the messed up one, I get the following message, "Windows Resource Protection could not start the repair service."
Make sense?
-
New #19
Ok, then we know the drive is not dirty from a power failure. The changes in the boot are confusing. On one hand, it appears the boot sector may be toast. Then on the other, it's getting past the boot and starting Windows. Perhaps a root kit? I'm not sure.
If you're displaying the boot sequence (driver list) the driver causing the problem will most often be the one just before the driver displayed at the stop. This isn't always the case as the problem driver could be before that if it's a hardware driver the hardware isn't responding.
If it were me, I would try to re-claim as much data as your can from the disk while connected in another PC and make sure it's scanned. It looks to me that the only way out is a clean install after you clean the disk with the other PC.
-
New #20
That's what I was afraid of. Oh well, data is still retrievable so it's not a complete loss. Thanks for all your help, Carwiz!
Quote
Related Discussions