I did a System File Check and a few things came up corrupted.

[BrandonTay]

This are the files or drives that are corrupted, if u guys need more info i have attached my sfc log. help me out will ya guys? thanks!



017-04-13 20:54:34, Info CSI 0000038d [SR] Beginning Verify and Repair transaction
2017-04-13 20:54:34, Info CSI 0000038f [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
2017-04-13 20:54:34, Info CSI 00000391 [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
2017-04-13 20:54:34, Info CSI 00000393 [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
2017-04-13 20:54:34, Info CSI 00000394 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2017-04-13 20:54:34, Info CSI 00000396 [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
2017-04-13 20:54:34, Info CSI 00000397 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2017-04-13 20:54:34, Info CSI 0000039a [SR] Repair complete

 

[RolandJS]

You have recent, current, OS and Data partition backups, I hope? If not, others may be able to shed some light on this.

 

[Sky Ranch]

This particular update, KB3068708, has to do with Diagnostic Tracking that caused problems a couple years ago, if I remember correctly. The errors are considered false flags and doesn't indicate any type of corruption.

You can uninstall KB3068708 then run SFC again. I do recall that MS issued a fix several months after the problem surfaced but don't remember the exact KB number.

 

[Bat 1]

Agreeing with Sky Ranch. Check this post #3: System Restore doesn't work

 

[RolandJS]

Some data recovery specialists recommend, if affordable and if possible:
-- make a one-pass/no-repetitive-read-attempts clone of this problematic HD onto any target external HD
-- or make a sector-by-sector one-pass/no-repetitive-read-attempts full image of that problematic HD
The ext target HD which received the cloning or image -- is stored in a safe place
(in case more drastic OS and Data restoration or recovery is needed)
If the present situation is a symptom of imminent HD failure, physical or "logical" -- the target HD would be
next in line for restoration or recovery attempts (after IT is cloned).