0x800736B3 installing KB2937610 on Win7 x64

There's the summary from your CheckSUR log...

Code:

Summary:
Seconds executed: 559
 Found 42 errors
  CSI Could Not Open file Total count: 1
  CSI Missing Identity Total count: 1
  CSI Replacement File: CreateFile Failed Total count: 16
  CSI Payload File Missing Total count: 1
  CBS Registry Error Total count: 4
  CBS Watchlist Package Missing Total count: 26
  CBS Watchlist Component Missing Total count: 5
  CSI Missing Winning Component Key Total count: 4

Looking at the detail results, many of them appear to be the result of bitflips - often caused by failing hardware (most often RAM).


As you saw, the SFC result shows just the one problem...

Code:

 Line 3453: 2014-08-24 18:18:13, Info                  CSI    00000302 [SR] Repairing 1 components
 Line 3454: 2014-08-24 18:18:13, Info                  CSI    00000303 [SR] Beginning Verify and Repair transaction
 Line 3455: 2014-08-24 18:18:13, Info                  CSI    00000304 [SR] Cannot repair member file [l:20{10}]"System.dll" of NetFx-System, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

I'll post a fix for the file error later - in the meantime, please do the following...

1) Test your RAM using Memtest86++ by following this tutorial - RAM - Test with Memtest86+ run at least 3 full passes and let us know what happens.

2) upload your COMPONENTS registry hive...

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

Actually that's the one thing I neglected to add in the first post.

ie: that I had installed an extra 4GB RAM about a week ago only to discover 3 days ago that *it* was the root cause of the corruptions I now face.

Very well picked up!

Yes, I have already run memtest86 on that RAM, discovered it was bad (from 6213.4MB to 6213.5MB failed consistently - it was literally just 100-200kB that failed every test), removed and replaced it, and re-run memtest86 successfully with the replacement 4GB. Pity we cannot 'format' RAM and mark them as bad sectors - a waste of otherwise healthy 4GB...

I will upload the components hive soon and post a link then.

Edit: ...and here it is...
https://dl.dropboxusercontent.com/u/.../COMPONENTS.7z

Thank you for such great detective work already...

I've uploaded a file - s96aa.zip - to my OneDrive at Noel's OneDrive
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:\s96aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\s96aa
or
DIR E:\s96aa



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



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



(e.g. XCOPY P:\wfire P:\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 reply

The pending moves are normal, and can be ignored (there is a way to clear them - but I prefer to leave well alone)
The SFC is clear now, so I'll get to work on the Components hive and see what I can fix in there.

I've uploaded a file - s96ab.zip - to my OneDrive at Noel's OneDrive (it may take a while - try again every hour or so)
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\s96ab\COMPONENTS C:\Windows\System32\config

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

I next need a copy of your SOFTWARE hive - which isn't as easy to get at
Please boot to the Repair Environment and copy the file using the command

COPY C:\Windows\System32\config\SOFTWARE <drive>:\s96aa

(where <drive> is the same drive letter you found above for the file replacement)
Then boot back into Windows, zip the file C:\s96aa\SOFTWARE and upload it to a reply.
I'll try and tackle the bitflips there - and a couple of other things, while I'm at it!