[SOLVED] [Win7SP1 x64] WU Error Code 8007370B - SURT total detected corruption count: 218.

J

Joeicam

Well-known member
Joined
Jun 11, 2017
Posts
68
Hello everyone,

I was referred over here from SleepyDude at GeekstoGo. I am having troubles updating my Windows 7 machine, and he said it was something with the registry. Every time I try and run Windows Update it always returns with the error above. I have included the required information and attached my logs.

Thanks,
Joe

View attachment CBS.zip

______________________________________________

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-06-11 22:01:13.461
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22814_en
us_c36ee628cf91f72d
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22814_en%us_b8b533318999a4c7
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22814_en-us_67504aá5173485d7






SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 218
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-06-11 22:02:33.780
----------------------EOF-----------------------
 
Hello! Yes I am still in need of assistance, thanks :). And no problem. You guys have more than enough threads to stay on top of
 
Please start with the following.

Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.
 
Thanks. Please do the following.


Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Hello! Here is the contents of the SFCFix.txt file :):

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-07-10 07:01:56.935
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Joe\Desktop\SFCScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\16408a1f1e2..9738a912369_31bf3856ad364e35[11.2.9600.18524_82fc8ce080779eb7.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0fdeac5f61..afbddabd31b_31bf3856ad364e35_6.1.7601.23020_b5ad5683db07022c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_02ab950c56be36601f788a516e76f386_31bf3856ad364e35_6.1.7601.23020_none_a7b577d2a8f8bb24.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.17239_none_5e8ca56653bd8515.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\16408a1f1e2..9738a912369_31bf3856ad364e35[11.2.9600.18524_82fc8ce080779eb7.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\16408a1f1e2..9738a912369_31bf3856ad364e35_11.2.9600.18524_82fc8ce080779eb7.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0fdeac5f61..afbddabd31b_31bf3856ad364e35_6.1.7601.23020_b5ad5683db07022c.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0fdeac5f61..afbddabd31b_31bf3856ad364e35_6.1.7601.23020_b5ad5683db07022c.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_02ab950c56be36601f788a516e76f386_31bf3856ad364e35_6.1.7601.23020_none_a7b577d2a8f8bb24.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_02ab950c56be36601f788a516e76f386_31bf3856ad364e35_6.1.7601.23020_none_a7b577d2a8f8bb24.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.17239_none_5e8ca56653bd8515.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.17239_none_5e8ca56653bd8515.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\16408a1f1e2..9738a912369_31bf3856ad364e35[11.2.9600.18524_82fc8ce080779eb7 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\16408a1f1e2..9738a912369_31bf3856ad364e35_11.2.9600.18524_82fc8ce080779eb7.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0fdeac5f61..afbddabd31b_31bf3856ad364e35_6.1.7601.23020_b5ad5683db07022c with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0fdeac5f61..afbddabd31b_31bf3856ad364e35_6.1.7601.23020_b5ad5683db07022c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_02ab950c56be36601f788a516e76f386_31bf3856ad364e35_6.1.7601.23020_none_a7b577d2a8f8bb24 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_02ab950c56be36601f788a516e76f386_31bf3856ad364e35_6.1.7601.23020_none_a7b577d2a8f8bb24.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.17239_none_5e8ca56653bd8515 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.17239_none_5e8ca56653bd8515.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2017-07-10 07:01:58.959
Script hash: jLK1m1v8IIGtpz63AxmzbZw7jXiP1qV5yK1c0oVDl9g=
----------------------EOF-----------------------
 
Thanks. Please do the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
I haven't recently. It was awhile back, maybe.. 3 years ago? I added 4GBs of RAM to my machine. Do you want me to reseed it?
 
I believe you have some bad RAM. Before you reseat anything, we should test to see which module is bad. Please do the following.

Test RAM With Memtest86+

Please ensure you allow 8 passes of the program!

Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting
 
Hi BrianDrab,
Is there something that you wanted me to post from that tool, or did you just want me to reseat it and then continue with another step?

Thanks,
Joe
 
Hi BrianDrab,
Sorry about the late reply. I was up north with my family for a few days. The tool didn't identify any errors. I have provided an attachment to this post of what I saw when it was ran.

Thanks,
Joe
20170716_175908.jpg
 
Ohhhh, I apologize. I was looking at the wrong area. I was looking where it says Test #8, not where it says "Pass: 0".
 
Finally got around to running the scan and letting it run 8 passes. Took quite a long time tho. It actually ran 11 passes and still found no errors.
 

Attachments

  • 20170723_160244.jpg
    20170723_160244.jpg
    307.8 KB · Views: 0
You must log in or register to reply here.
Back
Top