Random BSODs and Failed Launches

The CheckSUR report found a large number of errors - 394 - and fixed all but these....

Code:

(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_bd3036d609e9d5f1 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_cd48131dd338388f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_78e52218b95dc04d HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_e9edab228ffde74c HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_b25a04b3f5f64bbe HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_b1190aba12cf02aa HKLM\Components\CanonicalData\Deployments

I think the best thing to do is to run the tool again, and see if it can work out a way to fix those (while I try and work out what they mean :) )
Post the new CheckSUR.log file afterwards.

Your timing is perfect :)
I've just completed the fix for the remaining errors (assuming it works!)
Please follow these instructions EXACTLY - errors can be fatal!

Download the file tlkab.zip from my SkyDrive here....
Noel's SkyDrive

and save it (preferably to the desktop).
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new file regfix.reg in the same place

Create a new System Restore point for safety's sake!

Open an Elevated Command Prompt, and run the following command

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

(you should get a success message - leave the window open!)
now find the regfix.reg file, and right-click on it - select Merge
Accept the warnings.
You should get another success message

back in the Command Prompt window, run the following command

REG UNLOAD HKLM\COMPONENTS

Close the Command prompt window, and reboot

Now run another CheckSUR san, and post the new CheckSUR log file.

Great! the CheckSUR is now clear.
Just to check that it hasn't exposed other problems, please run another SFC /scannow, and post the new CBS.log
If it comes back 'couldn't find any problems', then my job is done, and KoolKat can take you back over :)

Hopefully, the machine should run better anyhow.

... Oh - I forgot to mention - see if Windows Update behaves now :)

Heh - the repairs to the CheckSUR appear to have shaken something loose in the SFC....

Code:

2013-02-06 20:33:26, Info                  CSI    000009ff Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_2ad6e90ee30ff985\WTVGOTHIC-S.ttc do not match actual file [l:30{15}]"WTVGOTHIC-S.ttc" :
  Found: {l:32 b:tS6Hw/E8qa4Cfb0TTMItxM45D09alD5jofCgvYojr84=} Expected: {l:32 b:dzS/rYReIjLpeofj7jo1l6q+cqg4X64ygEv2P/Dh6uo=}
2013-02-06 20:33:26, Info                  CSI    00000a00 [SR] Cannot repair member file [l:30{15}]"WTVGOTHIC-S.ttc" of Microsoft-Windows-ehome-font, Version = 6.1.7600.16385, 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
2013-02-06 20:33:26, Info                  CSI    00000a01 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-dxptasks-sync_31bf3856ad364e35_6.1.7600.16385_none_f4f399f5fbb26bc8\DxpTaskSync.dll do not match actual file [l:30{15}]"DxpTaskSync.dll" :
  Found: {l:32 b:jzATHWvin0Yx2BLyktB1sC8dOT32As+1jvZXO2bxMXE=} Expected: {l:32 b:KAtKkhINEyQMiNl/oncWeb3WWK27HRId82JKphWR6sY=}
2013-02-06 20:33:26, Info                  CSI    00000a02 [SR] Cannot repair member file [l:30{15}]"DxpTaskSync.dll" of Microsoft-Windows-DXPTasks-Sync, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-02-06 20:33:26, Info                  CSI    00000a03 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_2ad6e90ee30ff985\WTVGOTHIC-S.ttc do not match actual file [l:30{15}]"WTVGOTHIC-S.ttc" :
  Found: {l:32 b:Kmhhr0oAV4t3GKKFBSHC+p3JHB4Dd8NX5lqeDwo76VA=} Expected: {l:32 b:dzS/rYReIjLpeofj7jo1l6q+cqg4X64ygEv2P/Dh6uo=}

I'll post a fix protocol later

I've uploaded a file - tlkac.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\tlkac
hit the enter key - if you get a 'Not Found' error try
DIR D:\tlkac
or
DIR E:\tlkac

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\tlkac <drive>:\windows\winsxs /y /i /s /v /h

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.