@Noel,
I'll talk you through what I did to fix the corruption here

Looking at the errors in the CheckSUR log, it's quite easy to see there's a fair bit of corruption in a few C marks, so firstly we begin by loading the components hive that Frondar kindly uploaded. I'm not 100% sure on what C marks are actually for, but I know that they reference another part of the registry, which is why the SURT is reporting that the C Mark Deployment is missing. I'll take the first entry as an example:
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1 amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e
This points to the following location:
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\key\\data
So a quick Ctrl+F of the key name finds it for us. For this example (it may differ in other scenarios), you will see two values - one intact and one corrupt:
c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1
So although somewhere along the line Windows Update has successfully rebuilt the C mark, the corrupt one still remains. This is pointing to a non-existent key and that's why the SURT is kicking up a fuss. Solution: delete the corrupt one.
I've listed the rest of the errors in the following format. First line: SURT log entry, second line: corrupt value under key, third line: intact value.
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1 amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e
c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1
(f) CSI C Mark Deployment Missing 0x00000000 c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.ê.7601.1632_fe4t3bb890030e5 amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265
c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.ê.7601.1632_fe4t3bb890030e5
c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.1.7601.17632_fe493bb8900c30e5
(f) CSI C Mark Deployment Missing 0x00000000 c!9f5ef6d28c2..02f083e90ec_31bf3856ad34e35_6..7601.2¥747_9b3±3c4166e1e24 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44
c!9f5ef6d28c2..02f083e90ec_31bf3856ad3
4e35_6..7601.2¥747_9b3±3c4166e1e24
This one was a little trickier as there was only the corrupt value under that key, so I had to get the name from elsewhere. I loaded my hive and cross referenced it with that, to find that the correct name should be:
c!9f5ef6d28c2..02f083e90ec_31bf3856ad364e35_6.1.7601.21747_9b313c4166e61e24
(f) CSI C Mark Deployment Missing 0x00000000 c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5 x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d
c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5
c!eeb21a67e40..e9d1dfaee9a_31bf3856ad364e35_6.1.7601.21747_f94e0906c0631db5
(f) CSI C Mark Deployment Missing 0x00000000 c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6
c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471
c!3ed19571a5d..9ea532f473c_31bf3856ad364e35_6.1.7601.17632_473994496f911471
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1 amd64_a1b01961d1ffa7e5666cc2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_none_2781c161d72e01f1
c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1
As long as the correct value exists, you are safe to delete a corrupt one
@Frondar, could you download this file:
https://dl.dropbox.com/u/16537616/COMPONENTS.zip
Extract it to your Desktop. There should be one file inside called COMPONENTS (no extension). Then navigate to:
C:\Windows\system32\config\
And rename the COMPONENTS file in there to COMPONENTS.old
Then copy and paste the COMPONENTS file on your Desktop to the config folder
Reboot, run the SURT and post the CheckSUR.persist.log please!
Tom