In Windows Explorer, right click pop up has no Dropbox menu

CheckSUR/SURT very rarely displays errors - usually only when is crashes.

In your case, while not telling us exactly what's wrong, it does give us some clues

Code:

(w) Unable to open Event Log 0x000006B5 Application  OpenEventLog failed: 0x000006B5 - The interface is unknown.
.
(w) Unable to open Event Log 0x000006B5 System  OpenEventLog failed: 0x000006B5 - The interface is unknown.
.

SFC found one problem...

Code:

 Line 77505: 2014-07-22 23:23:54, Info                  CSI    00000311 [SR] Repairing 1 components
 Line 77506: 2014-07-22 23:23:54, Info                  CSI    00000312 [SR] Beginning Verify and Repair transaction
 Line 77509: 2014-07-22 23:23:54, Info                  CSI    00000314 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, 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 77512: 2014-07-22 23:23:54, Info                  CSI    00000316 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, 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 77513: 2014-07-22 23:23:54, Info                  CSI    00000317 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
 Line 77518: 2014-07-22 23:23:54, Info                  CSI    0000031a [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
 Line 77523: 2014-07-22 23:23:54, Info                  CSI    0000031c [SR] Repair complete

I am beginning to suspect that this may be the result of some driver install - it's the second/third case I can recall where this file is corrupted, and if I remember right they've all been RAID systems (I'll check when/if I can find the time)

I'll post a fix for the file error later - and once that's fixed, we'll set about finding the cause of the Event Logs errors

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



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



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