Solved Startup repair running for 9+ hours after bsod

[Bmck]

Hi,
First Im on my phone and don't have PC access so please excuse my post inadequacies.

My PC bsod today and hung at windows splash screen. Bsod was probably atapi.sys but was definitely something disk related and it wouldn't start the memory dump.

Next boot attempt brought up startup repair and it has been on repairing disk errors for almost all the 9 hours. I thought it switched to a different phase at one point but could be wrong. Haven't noticed it rebooting but could be wrong. I'm tempted to stop it but don't want to loose progress or cause additional problems so I'm here asking if cancellation could cause that. Need it back asap for work.

Computer has multiple drives so wondering if it could be trying to repair one of them. Os dive is a mushkin chromos 240gb ssd so I wouldn't think it should take so long. Largest drive I have is 5tb so I'm wondering if they are being scanned. I also have a drive with vista from an old computer thown in but it's not dual boot and don't think bios is even set to be able to boot from it but still wondering since it is taking so long.

If it won't loose progress or especially not cause damage I'm thinking need to cancel and disconnect the othe other drives.

Hope to get a reply before sleep so it can be working overnight.

Thanks

 

[Bmck]

Well, when I try to cancel it say the current repair operation cannot be cancelled. Will turning the PC off cause problems?

Also, fyi the drive doesn't have it's own bootable diagnostic tool, or non bootable tool for that matter.

 

[Megahertz07]

Welcome to the Forum.

It's typical OS disk problem.

Boot from the win 7 installation disk, go to repair and open a cmd window.
Type
chkdsk c: /f

If it doesn't find bad clusters or bad blocks type
sfc /scannow

 

[TechnoMage2016]

Like, who in this day and age has an OS install disk? They don't come with new computers anymore.

I'd stop that recovery process, even if you have to power DOWN the PC. Then disconnect every over drive on the system but the C: drive and reboot and just see what happens.

At that point, if it were me, I'd boot up the system from my Ghost Boot CD and run a restore of my last C: drive backup. But I'm guessing that if you had a backup copy of C:, you would have already used that. Eh?

If you were closer, I'd say bring that PC down here and I'd fix it for you.

So all I can do from here (Central FL.) is wish you Good Luck.

Cheers Mate,
TechnoMage

 

[Bmck]

Yeah I powered down last night and ran chkdsk from startup repair command prompt. Strange that the automated disk repair stalled out like that. I would think it was doing the same thing.

I had an image of the drive but it was a couple of months old. Trying to get an image now. Takes a few tried with macrium reflect due to ataport.sys bsod for some reason.