[SOLVED] SFC Scannow

A

alize00

Contributor
Joined
Jan 8, 2016
Posts
20
Location
France
Hi,

You already gave me a major help installing windows 10 from seven

All ran perfectly since yesterday.
I am back with the error 80070005 when trying to upgrade the Nvidia GTX 460 driver
The device manager shows error for the card "windows stops the card .... error C43)

SFC scannow shows errors that have not been corrected automatically
Please find attached the CBS log file

Thanks in advance for your assistance
 

Attachments

Hi there ....

Sorry for the delay ... it's been about a week - did you find a cure yet? If not, let us know .... I'm hoping for some spare time while finishing a few repairs, and should be able to have a look if you still need help.
 
Hi Gary,
Nice to take a break time to time
Since last post, it is some evolutions, the display card was out therefore it is now in thetrash can.

You will find attached the one minute ago "CBS log" file.
It still shows some errors.
 

Attachments

Hi again


That is one big CBS.log. It shows quite a mess for a few weeks, but at the very end of today's log (at the end of nearly endless "committed for repair" lists) ... there appears the following:
2016-05-02 08:27:39, Info CSI 000051bd [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Click to expand...

Quite a lot of ownership issues early in the log: items appearing that aren't owned, items with duplicate ownership, etc.

At the very end of the last run, did it show a "successful" outcome, or did it still show the "found but could not repair" outcome?

I'm hoping your newer card will enjoy a brighter future than the now-defunct fellow.

Let us know if any of the same issues show up again....
 
Thank for taking time to help me, Gary.
I do a fresh sfc scannow few minutes ago

Using a the well known filter "findstr /c:"[SR] Cannot repair " %windir%\logs\cbs\cbs.log ..." finally left the following errors
It will be a lot quicker for you to give advise

2016-05-03 09:20:59, Info CSI 000027c5 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:21:00, Info CSI 00002808 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:51, Info CSI 000046bb [SR] Cannot repair member file [l:11]"fdeploy.dll" of Microsoft-Windows-fdeploy, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:51, Info CSI 000046bd [SR] Cannot repair member file [l:7]"fde.dll" of Microsoft-Windows-fde, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:52, Info CSI 000046f1 [SR] Cannot repair member file [l:11]"fdeploy.dll" of Microsoft-Windows-fdeploy, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:53, Info CSI 00004741 [SR] Cannot repair member file [l:7]"fde.dll" of Microsoft-Windows-fde, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:54, Info CSI 00004755 [SR] Cannot repair member file [l:10]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:54, Info CSI 00004757 [SR] Cannot repair member file [l:10]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:56, Info CSI 0000479c [SR] Cannot repair member file [l:10]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:23:56, Info CSI 000047bf [SR] Cannot repair member file [l:10]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005180 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005182 [SR] Cannot repair member file [l:11]"fdeploy.dll" of Microsoft-Windows-fdeploy, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005184 [SR] Cannot repair member file [l:7]"fde.dll" of Microsoft-Windows-fde, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005186 [SR] Cannot repair member file [l:10]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005188 [SR] Cannot repair member file [l:10]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 0000518b [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 00005195 [SR] Cannot repair member file [l:11]"fdeploy.dll" of Microsoft-Windows-fdeploy, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 0000519e [SR] Cannot repair member file [l:10]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 000051a6 [SR] Cannot repair member file [l:7]"fde.dll" of Microsoft-Windows-fde, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-03 09:24:48, Info CSI 000051af [SR] Cannot repair member file [l:10]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.10586.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
 
Hi again

I'll assume, then, that the outcome of the previous run was "found, but could not fix, corrupted files" :)

Yes, I noticed the rather large amount of "cannot repair" items - but I so rarely look in the CBS logs, and they are so redundant, that it's hard to tell which file has come up earlier "cannot repair" yet later shows up as "repaired" ... I generally use other methods, since SFC has had some issues in past versions. The Windows 10 version is said to be better....

There are techs in the Windows Update forum that specialize in the SFC "found but could not fix" situation. One of the bright young techs wrote a fairly effective app called SFCFix - but it needs to be used by a tech from that forum who has gone through the training [they customize the instructions to fit each individual computer's situation]. Your situation might be a good fit to try their specialized care. If you want to post your situation with them, here's the link to the instructions for posting:
https://www.sysnative.com/forums/wi...posting-instructions-post35484.html#post35484

My next step as a generalist, should you want to try for another quick-fix before heading over to the Windows Update forum (since they are likely our busiest or second busiest forum... things take a little time), would be for you to try the DISM tool to repair the health of your system files. The online version of the command works well if you have a fast Internet connection. The DVD as a source version works if your Internet is not so great. You can try starting with the online method. Here are the instructions for that, if you decide you want to try another last-ditch effort:

Running DISM online


It's best to have a good and fast Internet connection for this method, and to make sure there is no malware presence on the computer beforehand.


1) Right-click the Windows Start Menu icon
2) From the menu, select Command Prompt (Admin)
3) To the question "Do you want to allow this app to make changes to your computer?", select Yes
7) Type in the following command: Dism /Online /Cleanup-Image /RestoreHealth


This can take quite a while - it varies a lot from machine to machine, and the speed of the Internet connection can add extra time when slow. Even if the "Percentage Complete" stops for a long time at a certian percentage, wait it out: it's fairly normal for the percentage displayed to not get refreshed for quite a long time.
___________________________

Should you try the DISM tool, and it shows errors & an unsuccessful finish ... it will be time to call in our Windows Update techs cavalry (to the rescue!) ....

I'll stay tuned...
 
Hi Gary,
Sorry for my late reply, It was my turn to leave home for a while.

I ran SFC /scannow with no better results than the other day

Following your suggestion, I used DISM as followed ( plus some other things found on this forum)
- Dism /Online /Cleanup-Image /RestoreHealth resulting in some errors
- Extracting the file install.esd from the windows.iso original folder then
- Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:c:\INSTALL_INITIAL\install.esd:1 /limitaccess

This fixes all issues as shown below (for short)
Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 0
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Before dism use to show the same problems with gpedit etc please see below

Now latest SFC shows only few errors

2016-05-11 07:35:56, Info CSI 000028b3 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-11 07:35:57, Info CSI 000028e8 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-11 07:39:09, Info CSI 000052b1 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-11 07:39:09, Info CSI 000052b4 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Far better, thanks again Gary for your patience, all the mess with double owner are still there but not so critical
 
Hi again


I think our attention now goes back to the GTX 460 situation. I'm expecting that your system files issues are in a reasonably decent state, from the results of your last DISM run and your recent SFC run.

The Code 43 error can be serious or not. When serious, it points to hardware trouble on the card. When not serious, it can be any number of things, from driver problems to the status inside the computer case.

I've seen posts where relief was found by:
1) Reseating the card (while doing this - it's a good time to use compressed air to blow out dust from the case & fans)
2) Uninstalling / Reinstalling the GTX 460 drivers.
3) Uninstalling / Reinstalling any suspected conflicting drivers ... those that I've seen mentioned most often were (oddly enough) USB/network devices. Can't hurt! Have an expedition day into Device Manager & update whatever seems likely.

The 460 was released in 2010 - if your card has been in use for several years, a nice dusting might prove refreshing for the oldster.

Let us know how it goes, and if you have any questions.
 
Gary,
I already did what you suggest, twice a year the computer take a visit to the garage to meet the compressor
The card was reasonably congested
All drivers suitable for W7 to the latest W10 dived into the hard disk with no results
Aida64 and DriversCloud did not complained to much

Finally, the card is now away into the dedicated recycle bin
The good new was the M.Board, Asus P8Z77-V which includes a decent graphic device "Intel(R) HD Graphics 4000"
I am not a gamer. This graphic card works quite well with my favorite software photoshop
Retouching 16bits/pixel, high resolution images is still nice and smooth, only concern the shared memory GPU CPU
Fortunately 16Mo helps time to decide which graphic card will replace the dead one

SFC Scannow still shows some [DIRSD OWNER WARNING] and Error - Overlap: Duplicate ownership for directory
If you have any ideas about those issues, please let me know if not, don't wary - be happy

So far, We can consider this thread as SOLVED
 
Hi again

My oldest daughter has the Intel HD Graphics 4000 on a modest Toshiba laptop, and actually can play a few older games on it. Glad to hear that Photoshop works (nice program - can do magic with pictures & designs).

I haven't found a sure-fire fix for the duplicate ownership that shows up in some CBS logs.... It might not have any untoward effects (as far as the system's performance). My guess is a permissions/ownership snag ... It's truly an interesting case, since I don't see how it would be possible to have two owners for a file (whenever I've changed ownership on a file, the only option I've see is for one owner at a time) ... If you'd like, you could try the SFC CBS.log duplicate ownership question in our Windows Update forum, the techs there have special training for SFC troubles, and also have a special tool they can modify to work its magic for each individual computer's problem.

Glad that the main troubles are over! [...for ultimate perfection, the Windows Update techs might be able to provide nirvana :) ]
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top