[SOLVED] Explorer.EXE hangs on Windows 8 and Shuts down and AMD SFC SCANNOW issue mshash

W

WarEagleUS

Member
Joined
Nov 23, 2013
Posts
5
OS: Windows 8 Pro 64 Bit.
Original OS: Windows 7 Professional 64 Bit. Cleaned/Zeroed HDD and Fresh Install of Windows 8 Pro 64 bit. This is a custom built system.
OS is Full Retail OS not purchased by me but received free from University.
System Age: 2 Years.
OS install Age: 3 weeks (this is a re-install/clean install).

CPU: AMD FX 6100
GPU: XFX AMD HD6870
MB: Asus M5A99X Evo (Not R2)
PSU: NZXT Phantom 750 Gold
Memory: Corsair Vengeance LP DDR3 - 1600MHz
HDD: WD Black (boot) 1TB (2 yrs), WD Green 1TB (4 yrs), WD 160GB (6 yrs).
Custom Built Rig - NO OEM/Manufacturer

Okay so doing a GOOGLE Search for this issue: 000006eb [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch led me to yalls site here. I see a few users have had this issue that I am currently facing. I have a few different one of these error messages that come up when I run an SFC /SCANNOW on my system from a CMD window. I was hoping the information I attached and provided can help me out some. This is something that has been happening very recently and I know one issue is the ADVANCE SYSTEM CARE from IOBIT (the Monitor.EXE process) but I have never had an issue with this right here and it seems to stem from a security proc from the CPU or something. Any help is greatly appreciated. If you need any more information just let me know. The ZIP files contain CBS, PERFMON, and the BSOD collector. I will be running the Driver Verifier a little while longer (actually have been doing that for almost a whole day before coming here) and will check email from my SGS4 or laptop. Thanks.

WarEagleUS
 

Attachments

Thanks Stephen I am taking a look at it now. The problem is (if you didn't mind looking through that CBS zip that wasn't formatted with SFCFix.exe) that a few issues arise with the hash mismatch. I honestly think, and after PMing with Corrine, that IOBit Advanced System Care 7 Pro (latest) actually caused these errors. I actually ran a DSIM fix that I found on Technet Windows 8 forum and haven't had the issue like that anymore, as of now. I did get an error report yesterday that I sent to Microsoft but I haven't had a chance to look at it yet and see what exactly the error was. I do know that since I have removed IOBit and Advance Care System 7 and all its children that my computer is actually running better (guess trusting anything from a Chinese company isn't really ideal) so I will see what the latest SFC /scannow finds any integrity issues. I will upload those here (not on your excellent TUT thread my friend) and see if you see anything different. I would hate to think that I would need to download each file you have on there to get these fixed but am willing to try anything :)

Respectfully,

Eagle (AKA Jason)
 
Additional Information: Just finished SFC /scannow and it actually found corrupt files this time and fixed them. YES! LOL! Thanks for the help. I will attach my DSIM log zip file just so you can see what it saw and hopefully this can help someone else out going forward. Thanks Corrine and Stephen. I will mark this thread as Solved (unless I am unable and in that case can y'all do it?) and read up on some additional information here!

Respectfully,

Eagle (AKA Jason)
 

Attachments

Well there goes my previous reply!

That's great - and DISM is showing the same success:

Code: 
Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:    5
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    5
Total Repaired Corruption:    5
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    [B]CSI Payload Repaired:    5[/B]
    CSI Store Metadata refreshed:    True

Which is fantastic.

May I ask, was this after following the tutorial or using the

DISM.exe /Online /Cleanup-image /Restorehealth

command?

The DISM command does the same thing, but I have also seen many occasions where it doesn't work. Hence the reason for the tutorial, which I recommend.

Also, what did you think of the tutorial? Is there anything you would improve or change about it?

Is SFC now reporting "no integrity violations detected"? Because I do see one more thing in your CBS log in the original post that the tutorial/DISM didn't report as fixing -

Code: 
2013-11-23 19:42:03, Info                  CSI    000006ee [SR] Cannot repair member file [l:34{17}]"UpgradeMatrix.xml" of Microsoft-Windows-Editions-Professional, Version = 6.2.9200.16384, 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-11-23 19:42:03, Info                  CSI    000006ef [SR] This component was referenced by [l:274{137}]"Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~6.2.9200.16384.Microsoft-Windows-Editions-Professional-Deployment"
2013-11-23 19:42:03, Info                  CSI    000006f0 Hashes for file member \??\C:\Windows\Servicing\Editions\UpgradeMatrix.xml do not match actual file [l:34{17}]"UpgradeMatrix.xml" :
  Found: {l:32 b:lvIoqQHlkI+RLrC4kgMX8OXGKfAPYj7mDuDUk+Etrcs=} Expected: {l:32 b:Ts6+4EzpOnSYghKfGh9eGK5ukT2IGhqBUY4kpa6rqXo=}
2013-11-23 19:42:03, Info                  CSI    000006f1 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-editions-professional_31bf3856ad364e35_6.2.9200.16384_none_354650aaa4288444\UpgradeMatrix.xml do not match actual file [l:34{17}]"UpgradeMatrix.xml" :
  Found: {l:32 b:lvIoqQHlkI+RLrC4kgMX8OXGKfAPYj7mDuDUk+Etrcs=} Expected: {l:32 b:Ts6+4EzpOnSYghKfGh9eGK5ukT2IGhqBUY4kpa6rqXo=}
2013-11-23 19:42:03, Info                  CSI    000006f2 [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\Servicing\Editions"\[l:34{17}]"UpgradeMatrix.xml"; source file in store is also corrupted
2013-11-23 19:42:03, Info                  CSI    000006f3 Ignoring duplicate ownership for directory [l:66{33}]"\??\C:\Windows\Servicing\Editions" in component Microsoft-Windows-Editions-Professional, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

Kind regards,
Stephen
 
This was before I even got the tutorial response you posted here. I was looking around for similar issues and happened to see the TechNet forums response. I didn't even do the check health option and went straight for restorehealth.

The tutorial is easy to follow though and I really liked it. I went ahead and bookmarked the page for it so I can refer to it for future use. SFC is reporting a clean bill of health. I haven't had an issue since and especially since I removed ASC v7.

Edit: The upgrade mismatch.xml file it's reporting is odd because this was a straight fresh copy of Windows 8 Pro X64 from Dreamspark through Kaplan University. I wonder if that is referencing the Windows 8.1 update that MS keeps trying to push me to take (I don't want to as some things in my comp don't work correctly with it, even after the release to public for purchase and it causes my system issues).
 
Last edited:
Hi,

I'll take a look at the latest CBS log if you would like, to see if I can work out more about that .xml file corruption.

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Thanks for the feedback on the tutorial, much appreciated. Good move to remove ASCv7, that's such an annoying piece of software for people like us!

Stephen
 
You must log in or register to reply here.
Back
Top