SFC seems (or at least claims) to have fixed a corrupted file - I'm not convinced :)
Code:
Line 9308: 2013-10-23 18:59:47, Info CSI 0000039a [SR] Repairing 1 components
Line 9309: 2013-10-23 18:59:47, Info CSI 0000039b [SR] Beginning Verify and Repair transaction
Line 9312: 2013-10-23 18:59:47, Info CSI 0000039d [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"imageres.dll" from store
Line 9319: 2013-10-23 18:59:47, Info CSI 0000039f [SR] Repair complete
Line 9320: 2013-10-23 18:59:47, Info CSI 000003a0 [SR] Committing transaction
Line 9324: 2013-10-23 18:59:47, Info CSI 000003a4 [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation.
Line 9325: 2013-10-23 18:59:47, Info CSI 000003a5 [SR] Repairing 1 components
Line 9326: 2013-10-23 18:59:47, Info CSI 000003a6 [SR] Beginning Verify and Repair transaction
Line 9329: 2013-10-23 18:59:48, Info CSI 000003a8 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"imageres.dll" from store
Line 9336: 2013-10-23 18:59:48, Info CSI 000003aa [SR] Repair complete
Please run another SFC /SCANNOW and post the new CBS.log files (we only need the CBS.log and the latest CBSPersist file this time).
That way we'll see if it was actually successful.