Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Corrupt system file


  • Please log in to reply
2 replies to this topic

#1 Dark Magician Girl

Dark Magician Girl

  • Members
  • 230 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 07 September 2014 - 02:52 AM

Here is what happened:

 

1. The power to my computer was cut off while the computer was running and my external drive was in use.

 

2. When the power returned, I booted the computer. I right-clicked the drive letter for my external drive, selected properties, and then selected error checking. I did the same for the system. Both scans took 1 to 2 minutes each and reported no errors.

 

3. I allowed the computer to go to sleep.

 

4. When I woke the computer, it froze while loading a user and then crashed.

 

5. I ran sfc /scannow. Error(s) were found and not all fixed.

 

I attached a copy of the log file created by system file checker. I went through the log and found the following entry:
 

 

2014-09-06 23:32:29, Info                  CSI    000007b1 [SR] Beginning Verify and Repair transaction
2014-09-06 23:32:30, Info                  CSI    000007b2 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:/7kST3Q0S1UqJnTWuMdKZ/gzVhBBt7lSYySNF6tFClM=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-09-06 23:32:30, Info                  CSI    000007b3 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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
2014-09-06 23:32:30, Info                  CSI    000007b4 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:/7kST3Q0S1UqJnTWuMdKZ/gzVhBBt7lSYySNF6tFClM=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-09-06 23:32:30, Info                  CSI    000007b5 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, 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

 

 

I found two potential solutions. One is running a tool called SFCFix.exe from sysnative.com. The other is running DISM.exe /Online /Cleanup-image /Restorehealth then sfc /scannow. However, I want to get more input before doing either of these things. I also included a copy of the minidump just in case.

 

Edit: A third option, which I found in the Microsoft knowledge base, is manually replacing the corrupted file with a known good copy; but the knowledge base doesn't tell me how to get my hands on a good copy besides copying one from another computer running the same OS, which I do not have.

Attached Files


Edited by Dark Magician Girl, 07 September 2014 - 03:02 AM.


BC AdBot (Login to Remove)

 


m

#2 Dark Magician Girl

Dark Magician Girl
  • Topic Starter

  • Members
  • 230 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 11 September 2014 - 09:03 AM

I ran the dism.exe tool then sfc /scannow. This appears to have fixed the issue. sfc /scannow reported no missing or corrupted system files. I am going to let the computer go to sleep then run sfc /scannow again in a few days.


Edited by Dark Magician Girl, 11 September 2014 - 09:04 AM.


#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,040 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:38 AM

Posted 11 September 2014 - 11:10 AM

There are those who will not download anything that they don't know exactly what it contains.  Please post the logs in your topic.  Please do not wrap these in code or use quotes.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users