I've known CheckSUR take over an hour to run even on a fairly fast system.
SFC usually takes around 10-20 minutes
The SFC results are interesting - the usual result in the summary is missing, so it took a little while to find the files reference....
Code:
2013-02-12 13:33:49, Info CSI 000000a7 [SR] Beginning Verify and Repair transaction
2013-02-12 13:33:51, Info CSI 000000a8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-batang_31bf3856ad364e35_6.1.7600.16385_none_13de7dc07ffbe591\batang.ttc do not match actual file [l:20{10}]"batang.ttc" :
Found: {l:32 b:ulqlFHGtUWnyAeeFxp3HyZ+k/9IrI4VEd5X8GbN1XPQ=} Expected: {l:32 b:CRurQ9Vl/KHlAM6skcV1ab+uMdOT2KeYdhHc0lnq/hk=}
2013-02-12 13:33:51, Info CSI 000000a9 [SR] Cannot repair member file [l:20{10}]"batang.ttc" of Microsoft-Windows-Font-TrueType-Batang, Version = 6.1.7600.16385, 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
2013-02-12 13:33:52, Info CSI 000000aa [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:20{10}]"batang.ttc" by copying from backup
2013-02-12 13:33:52, Info CSI 000000ab Hashes for file member \??\C:\Windows\fonts\batang.ttc do not match actual file [l:20{10}]"batang.ttc" :
Found: {l:32 b:ulqlFHGtUWnyAeeFxp3HyZ+k/9IrI4VEd5X8GbN1XPQ=} Expected: {l:32 b:CRurQ9Vl/KHlAM6skcV1ab+uMdOT2KeYdhHc0lnq/hk=}
2013-02-12 13:33:52, Info CSI 000000ac [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:20{10}]"batang.ttc" from store
2013-02-12 13:33:53, Info CSI 000000ad Repair results created:
0: Create File: File = [l:256{128}]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-batang_31bf3856ad364e35_6.1.7600.16385_none_13de7dc07ffbe591\batang.ttc", Attributes = 00000080
1: Move File: Source = [l:164{82}]"\SystemRoot\WinSxS\Temp\PendingRenames\8fd1faa66809ce01af0900003c10d008.batang.ttc", Destination = [l:256{128}]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-batang_31bf3856ad364e35_6.1.7600.16385_none_13de7dc07ffbe591\batang.ttc"
2: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\3dd35ba76809ce01b00900003c10d008._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
3: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\881f5ca76809ce01b10900003c10d008.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
4: Move File: Source = [l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\1fb85ca76809ce01b20900003c10d008.$$_fonts_40104ba9a1d20dac.cdf-ms", Destination = [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_fonts_40104ba9a1d20dac.cdf-ms"
5: Hard Link File: Source = [l:256{128}]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-batang_31bf3856ad364e35_6.1.7600.16385_none_13de7dc07ffbe591\batang.ttc", Destination = [l:62{31}]"\??\C:\Windows\fonts\batang.ttc"
6: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\69db9aa76809ce01b30900003c10d008.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
The summary only refers to this obliquely -
Code:
2013-02-12 13:39:59, Info CSI 000002eb Creating NT transaction (seq 2), objectname [6]"(null)"
2013-02-12 13:39:59, Info CSI 000002ec Created NT transaction (seq 2) result 0x00000000, handle @0x440
I think a second run of SFC /SCANNOW may be a good idea to ensure that the move is bedded in properly, but you should get a 'no problems found message at the end.
If not, please post the new CBS.log file (only)
Your CheckSUR log is clean.
Unless you have problems with the second SFC, I'll leave you to the mercies of the BSOD specialists. :)
Good luck!