Network Connections Constantly Crashing, Need Help!

Here's the critical bits from the SFC scan...

Code:

	Line 9203: 2015-08-01 19:46:37, Info                  CSI    00000349 [SR] Repairing 1 components
	Line 9204: 2015-08-01 19:46:37, Info                  CSI    0000034a [SR] Beginning Verify and Repair transaction
	Line 9207: 2015-08-01 19:46:37, Info                  CSI    0000034c [SR] Cannot repair member file [l:22{11}]"dot3api.dll" of Microsoft-Windows-Dot3svc, Version = 6.1.7601.17514, 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
	Line 9210: 2015-08-01 19:46:38, Info                  CSI    0000034e [SR] Cannot repair member file [l:22{11}]"dot3api.dll" of Microsoft-Windows-Dot3svc, Version = 6.1.7601.17514, 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

I'll post a fix protocol a little later.

I've uploaded a file - letaa.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:\letaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\letaa
or
DIR E:\letaa

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

XCOPY <drive>:\letaa <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

I must admit I didn't expect that to actually cure your problems! - glad it did!

Good luck.