[SOLVED] Unrepaired corruption, high CPU usage

[kindleaire]

My system has been consistantly sitting at >50% CPU use. After digging around with Process Explorer I found TiWorker.exe being a large part of that usage, as well as a lot of kernel time I couldn't quite account for. I stumbled upon SFCFix and tried running it in safe mode and now I'm here with some corruptions it doesn't know how to fix.

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-26 20:39:50.548
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.








AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-


telemetry-


client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.ap


p.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-


telemetry-


client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\teleme


try.ASM-WindowsDefault.json




SUMMARY: Some corruptions could not be fixed automatically. Seek advice


from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-06-26 20:54:11.040
----------------------EOF-----------------------

Tried twice to upload my CBS.zip to the forum but failed (on the server side seemingly). So here's a GDrive link instead:
https://drive.google.com/file/d/0B7F1q29r7lh9b1NhcXhiWkdhcUE/view

 

[BrianDrab]

Hi and welcome to Sysnative. The two telemetry corruptions you list above are a known issue and can safely be ignored. More info on that is below.

https://support.microsoft.com/en-us/kb/3022345

Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.

We can do one more scan however to see if there is any other hidden corruption or issues. Please do the following.

Step#1 - DISM /RestoreHealth Scan
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.

1. Right-click on the Start
   
   button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
   Dism /Online /Cleanup-Image /RestoreHealth
3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
   copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
   
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
   Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[kindleaire]

Thanks for your help. Here's my cbs.txt

View attachment cbs.txt

 

[BrianDrab]

As suspected this doesn't appear to be a Windows Update/Servicing issue. Your logs are clean. I suggest you post an inquiry in our Windows 8 forum as the experts there have more knowledge is such things. You can let them know you were checked out and cleared in the Windows Update forum.