Cbs.log help

Hey guys, I was working on a computer of mine that had some kind of Power issues. I replaced the PSU and tested it using Linux from a USB until I got the new HDD. It tested out well at the time.

Installed W7 on a new drive because I thought the problem was the PSU and it was fixed. It turns out, the problem was the Power Button was not working correctly. After installing and testing W7, was experiencing the same issues as before, so I cleaned up the Power Button connections, plugged and unplugged the connector a few times to get a good connection and it all started working pretty well, with no more Power Issues like before. I tested it all day today, but I was still noticing some weird stuff going on (Different than the Power Issue) so I ran these tools:

The Power issue consisted of the Power Button Light going on and off, loosing Power. Then I shut down the pc for the night, and it started all by itself a few times in the morning, and then back off, back on quite a few times before I turned it off and fixed the Power Button. So I assume the Power issues corrupted the HDD system files. Once I fixed the Power Button, I had to do a Automatic Startup Repair at Boot, and chose the System Restore Option and the pc booted.

1. "sfc /scannow", that was Good

2. Ran "Dism /Online /Cleanup-Image /ScanHealth" and it did some repairing as can be seen in the CBS.

3. Then I ran "Dism /Online /Cleanup-Image /CheckHealth" and got this message:

Now realize most if not all of this left over Errors are Avast. In the meantime maybe I'll reinstall avast.

HTML Code:

C:\Windows\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.23403


Error: 87

The checkhealth option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

HTML Code:

Summary:
Seconds executed: 415
 Found 101 errors
 Fixed 89 errors
  CSI Unexpected Failure Total count: 6
  CSI F Mark Bad Type Total count: 89
  Fixed: CSI F Mark Bad Type.  Total count: 89
  CSI Missing Winning Component Key Total count: 6

4. Then ran "DISM /Online /Cleanup-Image /RestoreHealth" and got the same message as above:

I will attempt to Attache the CBS LOG also.

Hi Nasty7,

please run this tool, copy/paste the output

http://www.sysnative.com/niemiro/apps/SFCFix.exe
Place it on your desktop we will be using it again

The Avast errors are a known problem, but fixable via this tool download it to your desktop
Downloading Farbar Recovery Scan Tool

Roy

DISM doesnt totally work on 7 thats why you got the 87 error

I will do that, thanks very much.

Do the Errors cause problems? just curious.

I restarted, then was offered the System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014] I thought this may help, so installed it, Restarted, and ran DISM again.

Installation date: ‎10/‎18/‎2017 8:29 PM

Installation status: Successful

Update type: Important

This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found.

More information:
http://support.microsoft.com/kb/947821

Help and Support:
http://support.microsoft.com

I'll post the outcome of DISM just in case it is of use.

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-10-18 20:45

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_a338d8ea2df29efb	x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_499a1b14d5902dfc	amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_914751ebea0c5702	x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_56aba0211ca246c2	amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_962753dde6e08635	x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_9e58d6f8311e6fc8	x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8	

Summary:
Seconds executed: 586
 Found 6 errors
  CSI C Mark Deployment Not Marked Total count: 6

Clearly the only issue now is Avast...I hope. Been working at this all day lol

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-18 21:23:01.819
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 6
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-10-18 21:58:49.814
----------------------EOF-----------------------

FRST Attachments

Hi Nasty7,
Yours is a slightly unusuall version of the Avast errors, strangely not listing the "110" errors.

Download the attachment fixlist.txt and save it to your desktop.

Right-click on FRST64.exe and select "Run as administrator".
Press the Fix button.
The tool will now process fixlist.txt.
If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

REBOOT

Then please re-run SURT, attach the log


The normal corruption, with the "110" errors usually causes Avast and the system to hang somewhat,
as well as Updating problems.



Roy

Fixlog.txt

Hi Chris,

that report looks good.

Surt is KB947821, please run it, should be clean now.

As a further check, please also run from an elevated command mode
sfc /scannow.

Roy

I ran both and all looks good!

I will need to Reboot a few times to see how well it boots. It's a low powered pc so don't expect much, but hopefully a little better than it's been.

I wonder if running a Startup Repair is Warranted, or is what we've done here sufficient for Startup problems also.

I am also having those Network issues. Had this before on another computer months ago, and think it was my Internet Provider, though they would never admit it, well...one of the Senior Techs confirmed it to me later on. I'll start another Thread for this if warranted, and test my Main pc also before hand, because it was not happening on that one on Tuesday.

Thank you very much torchwood, Chris