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

[Leftie]

Hi there Sfc code experts,


- I ran sfc /scannow and it failed at the 99% mark. (unable to fix corrupt file as well)

Not sure if this helps, previously i was able to run Windows experience index (WEI) but not anymore since the sfc /scannow fails.
- The WEI gives an error and stops at - "could not measure processor performance"


Am not too sure if my RAM config is affecting anything.
Im running a total of 8G rams = (2x2GB Team Elite 1333) + (4GB kingston)
All rams at (PC3-10700)(667MHz)


Kindly need help here.
I cant make head or tails of the log file so hoping someone could give me a heads up,
so that i can find a remedy to proceed from here or better still give me a solution to it.

Awaiting help.
Thanks!!

 

[ICIT2LOL]

Hello and welcome Leftie mate try it in safe mode along with a chkdsk.

 

[Leftie]

Hello and welcome Leftie mate try it in safe mode along with a chkdsk.

Thanks for your reply ICit2lol,


The chkdsk said "0KB in bad sectors" which i assume is ok
but sfc/scannow still fails at 99% in safemode

 

[ICIT2LOL]

Leftie mate the sfc is showing a lot of "cannot repair" stuff.
You could try this http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html
I know it is a lot of fiddling around but may just get those files back in order.

Now before you do anything back up all of the data you need just in case you have to reinstall you can do this from an image for example if you have made one.
Otherwise just back up the data to something - I do an image on a regular basis to an external drive.

 

[indianacarnie]

What ICit2lol said definitely. You might also want to take out that 4gig stick and see if that helps to at least finish the sfc/scannow. I tried a mismatched setup like that once on this machine (see spec.'s) with not so good results.

 

[ICIT2LOL]

What ICit2lol said definitely. You might also want to take out that 4gig stick and see if that helps to at least finish the sfc/scannow. I tried a mismatched setup like that once on this machine (see spec.'s) with not so good results.

That RAM as indianacarnie says mate I was wondering earlier but then dropped the idea.

Personally I use matched stuff where I can - that is one dedicated stick or a a pair or quad number as the usually come from the same manufacturing batch and therefore more likely to be "in sync" with each other. Again as Indianacarnie said mixing brands also not such a good idea unless one is strapped for money or course.

 

[Leftie]

Once again, thanks to ICit2lol & Indianacarnie

Will try it out when i get home from work.
And update results.

Cheers!

 

[Leftie]

Hi there ICit2lol & Indianacarnie and everyone else out there.

Ive tried removing the single stick of 4GB ram leaving only 2*2GB team elite ram running
Tried running sfc/scannow in both safe and normal mode afew times to no avail.
Still fails at 99% and unable to fix corrupt files.

(Although sfc/scannow fails ive been using the com for afew months now without problems)

Now im left with the option of repairing the windows files.

Would like to ask ----> If i were to do a repair of windows files (NOT re-installation of windows), would it erase my (documents, pgms, jpegs, movies++) in my hdd?

or it would be safe to leave my (documents, pgms, jpegs, movies & stuffs) in Hdd while doing the repair?

Cheers

 

[andrew129260]

See this tutorial:

It will answer all your questions: http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[NoelDP]

Before you do start a repair install - let's see if we can fix the existing one...


Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[Leftie]

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!

 

[NoelDP]

You have a number of problems - possibly caused by faulty RAM.

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 - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html 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.

 

[ICIT2LOL]

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)

 

[Leftie]

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.

 

[ICIT2LOL]

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

 

[Leftie]

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.

 

[scr]

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.

 

[NoelDP]

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

 

[NoelDP]

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

 

[Leftie]

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!