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

system scan errors


  • Please log in to reply
5 replies to this topic

#1 Semjasr

Semjasr

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:canada
  • Local time:03:12 AM

Posted 01 October 2013 - 04:15 PM

I wanted to back up my entire computer.  Before doing this I wanted to make sure everything was perfect so I ran sfc scan and there was corrupt files that have been repaired but it didnt repair as subsequent scan keep reporting the same. So I ran chkdsk along with scan for and attempt recovery for bad sectors and that just hung to where I had to do a hard shutdown. So I then did a full diagnostics of my hard drive and those all passed.  So I decided to do a complete reinstallation of windows and found that these same scan errors followed.  So before I decide that the diagnostics that the manufacterer of my computer are botched. I need to know how to fix this so I can do a full backup.



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,290 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:12 AM

Posted 01 October 2013 - 06:03 PM

System manufacturer and model?

 

You can always run the diagnostic created by the manufacturer of your hard drive...to ascertain the functional status of your hard drive.  Long/extended test.

 

Contrary to what some believe...the chkdsk /r command does not test the hard drive...it concerns itself solely with the Windows partition, the file structure used on the partition, and whatever files exist on that partition.

 

If it cannot complete, it usually posts an error message, it doesn't just hang.  If it appears to be hanging, it's likely that it's trying to overcome a tough problem, IMO.

 

Your partition could be screwed up...with nothing wrong with the hard drive itself...to produce the effects you have thus far described.

 

Louis



#3 Semjasr

Semjasr
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:canada
  • Local time:03:12 AM

Posted 03 October 2013 - 05:40 AM

well chkdsk did hang unless it likes to stay in the same spot for 3 days and what about the sfc scan.  I already stated that i ran full diagnostics on my hard drive and they all passed.



#4 Semjasr

Semjasr
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:canada
  • Local time:03:12 AM

Posted 03 October 2013 - 05:53 AM

 How do I fix this---

 

2013-10-03 04:10:29, Info                  CSI    000001a8 [SR] Cannot commit interactively, there are boot critical components being repaired
2013-10-03 04:10:29, Info                  CSI    000001a9 [SR] Repairing 2 components
2013-10-03 04:10:29, Info                  CSI    000001aa [SR] Beginning Verify and Repair transaction
2013-10-03 04:10:29, Info                  CSI    000001ab Hashes for file member \??\C:\Windows\system32\wbem\Wdf01000Uninstall.mof do not match actual file [l:42{21}]"Wdf01000Uninstall.mof" :
  Found: {l:32 b:Khw6Snu1wJ++GNIoY6yxl9I9YcMFd1DIgoHfKZafkno=} Expected: {l:32 b:Yt1Cj1cn2TiRYuRVf4giD3Kg40g43GBdTTr4ip5TNCI=}
2013-10-03 04:10:29, Info                  CSI    000001ac [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-10-03 04:10:29, Info                  CSI    000001ad Hashes for file member \??\C:\Windows\system32\wbem\Wdf01000.mof do not match actual file [l:24{12}]"Wdf01000.mof" :
  Found: {l:32 b:ew+xsUJbni5eIvJoq16I+phaGGLWets5I4YF9P6gDL0=} Expected: {l:32 b:rjBJp3JUDkwqQn/7E5mVEcjWSk0b/GPJ4b/7QWTo3N8=}
2013-10-03 04:10:29, Info                  CSI    000001ae [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store
2013-10-03 04:10:29, Info                  CSI    000001af WARNING: File [l:42{21}]"Wdf01000Uninstall.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership
    Old: Microsoft-Windows-WDF-Kernel Library, Version = 6.0.6002.18574, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-WDF-Kernel Library-MOF, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2013-10-03 04:10:29, Info                  CSI    000001b0 WARNING: File [l:24{12}]"Wdf01000.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership
    Old: Microsoft-Windows-WDF-Kernel Library, Version = 6.0.6002.18574, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-WDF-Kernel Library-MOF, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2013-10-03 04:10:29, Info                  CSI    000001b1 Hashes for file member \??\C:\Windows\system32\wbem\Wdf01000Uninstall.mof do not match actual file [l:42{21}]"Wdf01000Uninstall.mof" :
  Found: {l:32 b:Yt1Cj1cn2TiRYuRVf4giD3Kg40g43GBdTTr4ip5TNCI=} Expected: {l:32 b:Khw6Snu1wJ++GNIoY6yxl9I9YcMFd1DIgoHfKZafkno=}
2013-10-03 04:10:29, Info                  CSI    000001b2 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:42{21}]"Wdf01000Uninstall.mof" from store
2013-10-03 04:10:29, Info                  CSI    000001b3 Hashes for file member \??\C:\Windows\system32\wbem\Wdf01000.mof do not match actual file [l:24{12}]"Wdf01000.mof" :
  Found: {l:32 b:rjBJp3JUDkwqQn/7E5mVEcjWSk0b/GPJ4b/7QWTo3N8=} Expected: {l:32 b:ew+xsUJbni5eIvJoq16I+phaGGLWets5I4YF9P6gDL0=}
2013-10-03 04:10:29, Info                  CSI    000001b4 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:24{12}]"Wdf01000.mof" from store
2013-10-03 04:10:29, Info                  CSI    000001b5 WARNING: File [l:42{21}]"Wdf01000Uninstall.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership
    Old: Microsoft-Windows-WDF-Kernel Library-MOF, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-WDF-Kernel Library, Version = 6.0.6002.18574, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2013-10-03 04:10:29, Info                  CSI    000001b6 WARNING: File [l:24{12}]"Wdf01000.mof" in [l:56{28}]"\??\C:\Windows\system32\wbem" switching ownership
    Old: Microsoft-Windows-WDF-Kernel Library-MOF, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-WDF-Kernel Library, Version = 6.0.6002.18574, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 



#5 sikntired

sikntired

  • Members
  • 1,072 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:05:12 AM

Posted 03 October 2013 - 06:59 AM

Have a friend who had a somewhat similar problem. You may find the following to be of interest to your particular issue:

 

http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_update/sfc-scannow-foud-corrupt-files-after-updating/384bc395-42eb-4cab-b583-a1b1deb7a3e9

 

Good Luck



#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,290 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:12 AM

Posted 03 October 2013 - 08:48 AM

If the partition or partition table is damaged...my response would be to just do a clean install after deleting the partition, since you believe that the hard drive is free from blame.

 

Others here have reported success using the TestDisk tool when encountering possible partition problems.  I myself have not experienced success when attempting to use the tool.

 

https://www.google.com/#q=fix+corrupt+partition+with+testdisk%3F

 

Louis






2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users