sfc scan stuck at 96%

My laptop has been getting various BSOD's.
Page in Unpage Area & PFL list corrupt; but sometimes it just crashes into BSOD without a heading.

I should perhaps avoid having ccleaner being run; as this clears the mini dumps.

But; despite that; I've added cbs / sfc / malwarebytes logs atm & now properly running DM Log.

What was the initial reason for running an SFC scan in the first place?

Hi, I've seen your error on the CBS log and I will get in contact with someone who could probably help you much better than I can.

The CBS.log reveals the real problem - to some extent, at least...

Code:

2014-09-29 01:10:59, Error                 CSI    00000313 (F) STATUS_FILE_CORRUPT_ERROR #6779333# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_READ_DATA), oa = @0x95cf70->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[108]"\SystemRoot\WinSxS\x86_microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_none_3b0e32bdc9afe437\vcomp.dll"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x95d020, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000102]
2014-09-29 01:10:59, Error                 CSI    00000314@2014/9/29:05:10:59.137 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2014-09-29 01:11:01, Error                 CSI    00000315 (F) STATUS_FILE_CORRUPT_ERROR #6779332# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000102]
2014-09-29 01:11:01, Error                 CSI    00000316 (F) STATUS_FILE_CORRUPT_ERROR #6779331# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|AccessDeniedIsOk), da = (SYNCHRONIZE|FILE_READ_DATA), oa = @0x95d618->SIL_OBJECT_ATTRIBUTES {s:40; on:"vcomp.dll"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE), file = NULL, disp = Invalid)
[gle=0xd0000102]
2014-09-29 01:21:04, Info                  CBS    Reboot mark refs incremented to: 1

The SFC scan crashed before completion - so (rather stupidly) gave a 'no problem' response.

I would not be at all surprised if the best way to deal with this is to uninstall Visual C++ 2005 completely, and then reinstall it (carefully!).

Having said that, I need to do some research... and my time is severely limited at present.
If you haven't heard within 48hours, please SHOUT!

Okay; thanks for your help.

I will attempt to uninstall & re-install

I have discovered something new; it seems I have installed 2 of this (somehow)

edit:
I went ahead and installed 2 Visual C++ 2005's.
I hope these are the right ones.

http://www.microsoft.com/en-ca/downl...s.aspx?id=3387 (x86)
http://www.microsoft.com/en-ca/downl....aspx?id=21254 (x64)

OK - please run a new Check for Updates, and see if the updates found install properly.