Solved SFC /SCANOW fails, /VERIFYONLY results posted. Corruption o Hard Drive

[fllopinh]

Around 3 weeks ago my pc was regularly BSOD'ing because I had residual ATI drivers left from a replacement card I used. Everything was fine after I uninstalled these but one of the bsod's corrupted windows files. I was able to sfc /scannow repair the damaged files and everything was fine until 2 days ago.

The pc crashed again and this time the corruption seems worse than before. I had to use windows recovery platform to use DOS to manually restore the SAM, SECURITY etc registry folders and managed to get the pc starting again.

However after running chkdsk and everything being reported fine, a sfc scan fails at 8% no matter how many ties I try it.

I have included the CBS.log from the verifyonly scan.

I don't really want to do a repair install if i can avoid it. I don't have money to buy a new hard drive, clone and migrate my C: drive. I do have access to another pc with system files if I can copy and paste.

Any advice?

I have tried quite a few other things and could happily go into more default if more information is required.

ps: windows is stable while running in safe mode, but when trying to run games of multiple software packages I get freezes, bsod's and hang ups.

part two of the log. had to split them and name one a .log instead of .txt

 

[kegobeer]

Since you have access to another computer, I'd take the problem drive out and slave it into the other computer and do a scan. If there are actual disc problems, you'll find it that way. Or, you can use a non-Windows utility to scan the drive (booting from the CD), like a LiveCD.

Based on your post, I'd wager that the OS is just borked. After you scan it, and it comes back without any hardware problems, do a repair install of Windows. I know you don't want to do it, but that will most likely be the best way to solve your problems.

 

[gregrocker]

Why do you not want to do a Repair Install which is the fix I'd run if in your situation? It only reinstalls the OS while leaving the files, settings and programs in place.

And what would indicate that replacing your HD is called for here at all?

 

[fllopinh]

I have spend a fair while modifying and customizing which services, tasks etc run. I've also customized lots of other things but I will just get over it if the slaving doesn't work.

I'll also go and properly read the repair install tutorial which is posted here. I'll let you guys know.

 

[gregrocker]

It will be interesting to see which of the "customizations" Win7 spits out, likely only the ones it deems outright corruption. You can customize Win7 too much into this sort of situation as it is already so lean it will not tolerate a lot of tampering beyond normal system settings.

Years of experience here have shown us that turning off any Services is inadvisable as there are unintended consequences down the line. This is not XP or early Vista - all Services not absolutely needed are set on Manual fast-triggers.

 

[fllopinh]

^ that's something i hadn't considered though i did research all services and components I could turn off and set to manual.

the other system i have is a windows 7 32 bit so the sfc scan will not work. I'm running a check disk with bad sector repair.

Anything else i can try now that it is slaved?


I'm currently reading through the repair install thread in preparation

 

[gregrocker]

Run the Repair Install in the original machine.

In fact I'd also run SFC -SCANNOW Run in Command Prompt at Boot from Win7 DVD.

I just reread the thread and am not catching what makes the HD suspect. But if Disk Check finds problems then run the HD maker's HD Diagnostic extended CD scan.

 

[fllopinh]

even from cmd in live boot usb sfc fails. From what I could understand fro the cbs.log was quite a few things were corrupt. I had to use the regback folder to replace the registry i had at the time of the crash.

chkdsk has run several times and found no faults, but the sfc scan will not complete. I'm going to back up and export my registry, do and upgrade and hopefully everything is ok.

Once i get some cash ill get an ssd and clone the hard drive. i think it's on it's last legs

 

[gregrocker]

Still waiting to hear what is indicating this is a HD problem. Did you edit your original post of some information?

 

[fllopinh]

no I didn't edit anything.

To go into all the detail about the health of my pc over its life time would be quite an epic reply.

I believe the HD is the problem because sfc fails at 8% telling me it has found corruptions and can not repair. Verifyonly reports back that there is problems. I cant remember the exact phrasing atm.

Chkdsk reports back that the hard drive is fine.

Checking the cbs.log i seemed the find reference to winsxs folder having corruptions

Up until I used dos to manually repair the registry, the repair disc start up recovery reported users/temp and 4 other system 4 system folders as being corrupt.

If I havn't got what your meaning just let me know.

 

[gregrocker]

System File Checker has nothing to do with the HD condition, only the condition of the Win7 OS files. If you don't know this then you shouldn't be messing with your Registry or even customizing Win7 much.

If Disk Check says its OK then I would trust it's judgement, but you can run the maker's diagnostics which I linked earlier to be certain.

If SFC fails when run from Command Line then the next step is a Repair Install.

 

[ignatzatsonic]

I believe the HD is the problem because sfc fails at 8% telling me it has found corruptions and can not repair.

Chkdsk reports back that the hard drive is fine.

SFC failing wouldn't imply a hard drive failure to me, but I don't now the details of any HD issues you may have.

 

[fllopinh]

Sorry my bad. The hard drive is fine, there is just damage to the files from the crash. The files themselves are corrupted, the hard drive is fine. Smart tests and seagate tools all indicate this.

I'm aware sfc only checks are repairs the health of windows files. It was just me being lack in my post. I don't sleep much and discrepancies and mistakes do become evident unless i concentrate 100%

 

[gregrocker]

Repair Install

 

[fllopinh]

Thanks for your help guys.

Did a repair and around 99% of what I had before is still there.

I've had one or two BSOD's again, but these were isolated but I am going to try and get to bottom of this eventually, just not now, and not on this thread.

Thanks again

 

[gregrocker]

A Repair Install is not meant to remove anything, just reinstall the OS while transferring back in your files, programs and settings.

The easiest way to get to bottom of BSOD's is to post up the bugcheck file using these tools to collect the data needed: Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Forums

You can also check the logs and use System Resources to gather clues following these troubleshooting steps