Sfc /scannow failed at 99%. Log details included. Kindly help. Thanks!

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Leftie
    Posts : 24
    Windows 7 OEM Home Premium 64bit (SP1)
    Thread Starter
       New #11

    NoelDP said:
    Hi there NoelDP & others, apologies for the delay as i was outstationed at work.

    QUICK SUMMARY
    The SURT/hotfix worked great and windows updates were installed.

    Some hiccups
    - SFC/scannow is totally unable to run at all.
    (previously it could run up till 99%, unable to fix corrupt files)
    (i ran as administrator in both normal & safe mode to no avail)

    - Windows update still shows me files that are already being installed

    - Still unable to run WEI. (stops at unable to measure processor performance)


    WINDOWS UPDATE BEFORE SURT



    WINDOWS UPDATE AFTER SURT



    UPDATE HISTORY STILL SHOWS FILES THAT ARE ALREADY INSTALLED



    SFC/SCANNOW ERROR




    Have attached the CBS file as instructed.
    Awaiting further instructions. Kindly let me know if anything else is needed.
    Thanks for all the help!
      My Computer
    Quote Quote

  3. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #12

    You have a number of problems - possibly caused by faulty RAM.
    Code:
    Checking Component Store
(f) CSI Payload File Missing 0x00000000 qasf.dll amd64_microsoft-windows-directshow-asf_31bf3856ad364e35_6.1.7601.17514_none_78e385451529fc1e 
(f) CSI Payload File Missing 0x00000000 NAPCRYPT.DLL amd64_napcrypt_31bf3856ad364e35_6.1.7601.17514_none_99fb87a0aad31261 
(f) CSI Payload File Missing 0x00000000 mchgr.inf_loc amd64_mchgr.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_fd11d213229f2cdd 
(f) CSI Missing Identity 0x00000000 appid mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_0b3568b5d0c39a8f 
(f) CSI Payload File Missing 0x00000000 lsi_scsi.inf_loc amd64_lsi_scsi.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_81ea6d9ef9396ec5 
(f) CSI Payload File Missing 0x00000000 machine.inf_loc amd64_machine.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a102031c07b6ad1d 
(f) CSI Payload File Missing 0x00000000 lsi_sas2.inf_loc amd64_lsi_sas2.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_61a63821397a90a8 
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-UAPICore, Cultura=neutrah, Versikn=6.1.7600.16381, PubliwKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NokSxS 浡㙤弴業牣獯景ⵔ楷摮睯ⵢ慴楰潣敢㍟戱㍦㔭愶㍤㐶㍁張⸶⸱㘲〰ㄮ㌶㔹湟湯彥〕攲慣ㄳ〶㜴ち敦 Bad identity
(f) CSI Manifest Missing 0x00000002 浡㙤弴業牣獯景ⵔ楷摮睯ⵢ慴楰潣敢㍟戱㍦㔭愶㍤㐶㍁張⸶⸱㘲〰ㄮ㌶㔹湟湯彥〕攲慣ㄳ〶㜴ち敦.manifest 浡㙤弴業牣獯景ⵔ楷摮睯ⵢ慴楰潣敢㍟戱㍦㔭愶㍤㐶㍁張⸶⸱㘲〰ㄮ㌶㔹湟湯彥〕攲慣ㄳ〶㜴ち敦 
(f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063.manifest amd64_microsoft-windows-dot3helperclass_31bf3856ad364e35_6.1.7600.16385_none_ds105fd062be063 
(f) CSI C Mark Deployment Missing 0x00000000 c!160ad7c4363.c9f2f780424_31bf3856ad364e35_6.1.7600.16778_adb5d7c6e6d1ab4 amd64_160ae7c4363a7b8730fa3c9f2f780424_31bf3856ad364e35_6.1.7600.16778_none_adb5d7c6e6d1ab4e
    Each of these is the result of a bitflip in the registry - and before doing anything else you need to chack that your RAM is working properly.
    Follow the instructions here - RAM - Test with Memtest86+ to check it out.
    Then it's likely that you'll need to do the repair install as suggested, as the corruption may be a lot more widespread than it appears.
      My Computer
    Quote Quote

  4. ICIT2LOL
    Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       New #13

    Am not so good at reading those files as Noel is but be sure the memtest he suggests is run for at least 8 passes unless you get errors straight away - many we advise to do this stop before that 8 passes and have to start all over again.

    If like in my pic/s you see that then you can stop. (One pic shows info that it should give you)
    Attached Thumbnails Attached Thumbnails Sfc /scannow failed at 99%. Log details included. Kindly help. Thanks!-memtest-info.png   Sfc /scannow failed at 99%. Log details included. Kindly help. Thanks!-memtesterror.png  
      My Computer
    Quote Quote

  6. Leftie
    Posts : 24
    Windows 7 OEM Home Premium 64bit (SP1)
    Thread Starter
       New #14

    Thanks guys for your advice.
    Will spend tonight running Memtest+86 on my ram sticks and post further results.

    In the meantime would it be advisable to download Malwarebytes/ Malwarebytes antirootkit for a full scan?
    - https://www.malwarebytes.org/antimalware/

    I have ran a full scan using MSE and MSRT and no threats found.
      My Computer
    Quote Quote

  7. ICIT2LOL
    Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       New #15

    Leftie if you want to run some rootkit scans her are a few that are good the TDSS - Kaspersky is the usual recommended one.
    Best Free Rootkit Scanner and Remover
      My Computer
    Quote Quote

  8. Leftie
    Posts : 24
    Windows 7 OEM Home Premium 64bit (SP1)
    Thread Starter
       New #16

    So far ive ran memtest on 1x2GB ram on all slots and no errors. (will be continuing tonight)

    Would like to ask this. Im running a dual-channel mobo with sandy bridge. (details in System Specs)

    Is this the right way to place the rams? Or should i occupy slots 2&4 instead with the 2x2GB?

    Slot 1 (closest to CPU): 2GB
    Slot 2: Empty
    Slot 3: 2GB
    Slot 4: Empty


    @ICit2lol noted on the Kaspersky

    @scr i thought you nailed it!! I tried both sfc /scannow with space and w/o space to no avail
    Thanks for pointing it though. At least there was a glimmer of hope. :)
    Last edited by Leftie; 04 Sep 2014 at 12:51.
      My Computer
    Quote Quote

  10. scr
    Posts : 366
    1. Windows 7 Home Premium sp1 - 64bit 2. Windows 7 Pro sp1 - 64bit
       New #17

    While I freely admit that most of this discussion is way over my head I will mention this as no one else has.

    In post #11 a screenshot of the sfc/scannow error.. Shouldn't there be a space between sfc and /scannow ..
    sfc /scannow not sfc/scannow

    Now I'll walk back to my seat on the observation deck.
      My Computer
    Quote Quote

  11. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #18

    You have a point! (Good eye, there!) - but the command does seem to have worked anyhow, or we'd have a very different error message.
    However, it doesn't change the basic analysis from CheckSUR that there is a possible problem with RAM
      My Computer
    Quote Quote

  12. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #19

    Leftie said:
    So far ive ran memtest on 1x2GB ram on all slots and no errors. (will be continuing tonight)

    Would like to ask this. Im running a dual-channel mobo with sandy bridge. (details in System Specs)

    Is this the right way to place the rams? Or should i occupy slots 2&4 instead with the 2x2GB?

    Slot 1 (closest to CPU): 2GB
    Slot 2: Empty
    Slot 3: 2GB
    Slot 4: Empty


    @ICit2lol noted on the Kaspersky

    @scr i thought you nailed it!! I tried both sfc /scannow with space and w/o space to no avail
    Thanks for pointing it though. At least there was a glimmer of hope. :)
    From the motherboard manual - pairing is across slots 1/3 and 2/4
    So you got it right
      My Computer
    Quote Quote

  13. Leftie
    Posts : 24
    Windows 7 OEM Home Premium 64bit (SP1)
    Thread Starter
       New #20

    NoelDP said:
    From the motherboard manual - pairing is across slots 1/3 and 2/4
    So you got it right
    Thanks for the confirmation Noel.
    Anyway, i have placed them in slots 2&4 now instead of 1&3, just to see if it works.


    Things done

    1) Ran memtest86+ 5.01 on both 2gb sticks separately without errors.

    2) Ran full scans of MBAM, MSRT, MSE in safe and normal mode.
    (some harmless pricegong ads were found and quarantined by MBAM)

    3) Manually checked for windows update only to encounter 80070002 error this time round.


    4) So i ran an "auto reset windows update component" from Microsoft site to no avail as well.
    - How do I reset Windows Update components?


    5) is this normal?;
    -Im not seeing any rundll32 processes in Windows Task Manager at all
    -The rundll32 file i found shows this "paper" looking icon. Is this normal?


    ive done all i can to my meagre knowledge..
    quite a noob when it comes to software
    Awaiting your further instructions.
    Cheers!
      My Computer
    Quote Quote

 
Page 2 of 6 FirstFirst 1234 ... LastLast

  Related Discussions
sfc /scannow, error, CBS.log included
in Performance & Maintenance

I have some problemd with my PC. sfc /scannow doesn't repair anything and just say: Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is...
Good day all. Firstly, thank for taking the time to read my woes! Here goes, around a month ago, I got a Titan X, since then I've been having these BSOD's, I have removed all the old drivers through both going into safe mode and removing them manually, and with Guru3D DDU, I have 350.12...
I've been trying to download some files using uTorrent, but after 10-15mins of download i get a BSOD, so i searched on the internet how to get rid of it and found this thread by z3r010... followed his instructions, and well here i am... Using Blue Screen View, i managed to see some information...
Short version: Built my new rig 9 months ago, fresh equipment, new copy of Win7 (Pro). Recently my computer wouldn't start up, it kept going into a BSoD loop. It would flash the BiOS screen, pause with cursor jumps, then show the low res Windows load screen with the bar scrolling blue bars instead...
I've recently started getting BSOD's and though I might've figured it out on my own, I'm not sure so I'm coming here for help... According to the sfc I'm hoping it's just a corrupt mcepg.dll, but it also says other things about my processor or something. Any help?
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 10:16.
Find Us