[SOLVED] sfc not able to fix the system

brunoais · Jul 20, 2015

I've tried to run sfc and it is failing to fix my system. It finds errors but it doesn't say anything about them except for the logs.
I need help to be able to allow it run right.
So far I've tried:

Rebooting
Rebooting in safe mode and trying again.
Rebooting into administrative console (failed to boot)
Rebooting into admin console using a recovery disk.

All of them give the same issue. sfc fails to fix the system files.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

I've tried to attach the log, View attachment CBS.zip.
Please help understanding what is wrong.

zcomputerwiz · Jul 21, 2015

Read More:

2015-07-20 22:22:43, Info CSI 00000365 [SR] Repairing 1 components2015-07-20 22:22:43, Info CSI 00000366 [SR] Beginning Verify and Repair transaction
2015-07-20 22:22:43, Info CSI 00000367 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:d0R8gqC9V88kxd/hX2M0rym11RJzbpTyaDDbH4Mq8pg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-20 22:22:43, Info CSI 00000368 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-20 22:22:43, Info CSI 00000369 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ErEvcGxrC5RD30CwVgig/0sasSdfpRLjd18ZiXseYV4=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-20 22:22:43, Info CSI 0000036a [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-20 22:22:43, Info CSI 0000036b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:d0R8gqC9V88kxd/hX2M0rym11RJzbpTyaDDbH4Mq8pg=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-07-20 22:22:43, Info CSI 0000036c [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-20 22:22:43, Info CSI 0000036d [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-20 22:22:43, Info CSI 0000036e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:ErEvcGxrC5RD30CwVgig/0sasSdfpRLjd18ZiXseYV4=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-07-20 22:22:43, Info CSI 0000036f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-20 22:22:43, Info CSI 00000370 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-20 22:22:43, Info CSI 00000371 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

These files are incorrectly identified as corrupt. What is the initial problem you are attempting to remedy?

brunoais · Jul 22, 2015

A program crash always at the same point.
It is called "life is strange.exe". It is a program that belongs to the life is strange game.
After I get into a specific stage (±20 min in), it crashes.
ATM, the objective is to solve what sfc says is wrong.

Thanks for reading and identifying the information in the log.

zcomputerwiz · Jul 22, 2015

What kind of crash are you getting? Is it a blue screen of death or is the game just crashing to the desktop?

brunoais · Jul 22, 2015

The game itself crashes with an illegal access popup (I can't get an image, atm. Ask if you want it).
It shows it can't access the executable itself.
I believe it uses the unreal engine.

Their support insists that it is caused by any of windows' libraries being corrupted.

zcomputerwiz · Jul 22, 2015

Please zip and upload the contents of the minidump folder, you will need to use a service such as OneDrive, DropBox, SendSpace, etc. and then include the link with your reply.

The folder will look something like this:
C:\Users\<UserName>\Documents\My Games\Life Is Strange\LifeIsStrangeGame\Logs\

brunoais · Jul 22, 2015

Do you mind if I send the link to you by PM?
I have no issues with you seeing it but it contains some minor private information inside which I'd rather not letting just anyone to get it.

zcomputerwiz · Jul 22, 2015

That would be fine.

zcomputerwiz · Jul 22, 2015

Looks like a Null pointer exception. Is there any particular action, object, or location in the game that triggers it?

brunoais · Jul 22, 2015

It is after a specific action when there's a camera change after a long dialog.
The game history up to that point doesn't seem to affect it.

BTW, you are the first asking for the dump and the logs. Their support didn't do that yet.

zcomputerwiz · Jul 22, 2015

Hopefully they'll ask for them at some point, unfortunately it's usually easier to blame other software than to find out what is actually causing the problem

The files that are reported as corrupt are a false positive, but it won't hurt anything to replace them and a clean sfc log should give you a little more leverage with support.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

SFC Scan

Click on the Start

button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

SFC should end with "Windows did not find any integrity violations".

brunoais · Jul 22, 2015

It did show:
"Windows did not find any integrity violations"
Do I still need to send you the logs?

zcomputerwiz · Jul 22, 2015

Nope, you should be good to go :)

brunoais · Jul 22, 2015

Nice! Thank you!

Search

Search

[SOLVED] sfc not able to fix the system

brunoais

Contributor

zcomputerwiz

Windows Update Expert

brunoais

Contributor

zcomputerwiz

Windows Update Expert

brunoais

Contributor

zcomputerwiz

Windows Update Expert

brunoais

Contributor

zcomputerwiz

Windows Update Expert

zcomputerwiz

Windows Update Expert

brunoais

Contributor

zcomputerwiz

Windows Update Expert

brunoais

Contributor

zcomputerwiz

Windows Update Expert

brunoais

Contributor