[SOLVED] [Win7SP1 x64] Win.update and MSSE errors with SFC

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-11 11:53:39.553
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Kanabrew\Desktop\SFCScript.txt [0]








RegistryScript::
Failed to delete registry key HKEY_LOCAL_MACHINE\22509\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad\64e35_11.2.9600.18349_15f13a07f09c509c. A root key cannot be created under this hive.
Failed to import registry key HKEY_LOCAL_MACHINE\22509\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad364e35_11.2.9600.18349_15f13a07f09c509c. A root key cannot be created under this hive.
Failed to delete registry key HKEY_LOCAL_MACHINE\22509\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.>.9600.17633_none_3e5fd1f886cd80df. A root key cannot be created under this hive.
Failed to import registry key HKEY_LOCAL_MACHINE\22509\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.2.9600.17633_none_3e5fd1f886cd80df. A root key cannot be created under this hive.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-04-11 11:53:39.558
Script hash: M3S5YnfH5425MgASQActew6JSlPXo/LYWHo/f0L2U38=
----------------------EOF-----------------------
 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-11 12:09:19.709
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Kanabrew\Desktop\SFCScript.txt [0]








RegistryScript::
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.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.>.9600.17633_none_3e5fd1f886cd80df.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.2.9600.17633_none_3e5fd1f886cd80df.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad\64e35_11.2.9600.18349_15f13a07f09c509c.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad364e35_11.2.9600.18349_15f13a07f09c509c.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.>.9600.17633_none_3e5fd1f886cd80df.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.>.9600.17633_none_3e5fd1f886cd80df.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.2.9600.17633_none_3e5fd1f886cd80df.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad364e35_11.2.9600.18349_15f13a07f09c509c.
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_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.>.9600.17633_none_3e5fd1f886cd80df with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adf3bbf6ae771eced8018c9ba7281483_31bf3856ad364e35_11.2.9600.17633_none_3e5fd1f886cd80df.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2017-04-11 12:09:20.228
Script hash: 73nw/gBqsxBdP1FUjNE0kIJCvbEVnr4fMYbxGoVWvk0=
----------------------EOF-----------------------
 
Excellent. Please do the following again.

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.
 
OK, 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

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-11 15:26:06.605
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Kanabrew\Desktop\SFCScript.txt [0]








RegistryScript::
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.
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.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\47d60bdee86..21c181192d2_31bf3856ad364e35_11.2.9600.18349_9a10c9279f9040e8.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\aab4ad3a691..3ec69b8e289_31bf3856ad364e35_11.2.9600.18349_42708c8dd06cb027.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d0ad0d907aa..e661ea65529_31bf3856ad364e35_11.2.9600.18349_c61900500a2432e9.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad\64e35_11.2.9600.18349_15f13a07f09c509c.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\47d60bdee86..21c181192d2_31bf3856ad364e35_11.2.9600.18349_9a10c9279f9040e8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\aab4ad3a691..3ec69b8e289_31bf3856ad364e35_11.2.9600.18349_42708c8dd06cb027.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d0ad0d907aa..e661ea65529_31bf3856ad364e35_11.2.9600.18349_c61900500a2432e9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2017-04-11 15:26:07.068
Script hash: SjKkvDal6q/zSjFXbsLV0rm4OCz28tQSXs64Moj1AOg=
----------------------EOF-----------------------
 
Excellent. Please do the following again.

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.
 
Please do the following.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-03-2017
Ran by Kanabrew (11-04-2017 16:12:50) Run:1
Running from C:\Users\Kanabrew\Desktop
Loaded Profiles: Kanabrew (Available Profiles: Kanabrew & LogMeInRemoteUser)
Boot Mode: Normal
==============================================


fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad/64e35_11.2.9600.18349_15f13a07f09c509c]
*****************


HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad/64e35_11.2.9600.18349_15f13a07f09c509c => key not found.


==== End of Fixlog 16:12:50 ====

and yes I'm remote-ing in to home from work with logmein
 
Please do the following.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop. (YOU CAN USE THE ONE YOU ALREADY DOWNLOADED)
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-03-2017
Ran by Kanabrew (11-04-2017 16:18:29) Run:2
Running from C:\Users\Kanabrew\Desktop
Loaded Profiles: Kanabrew (Available Profiles: Kanabrew & LogMeInRemoteUser)
Boot Mode: Normal
==============================================


fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad/64e35_11.2.9600.18349_15f13a07f09c509c]
*****************




========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed197a00ff2..e13de19b15c_31bf3856ad/64e35_11.2.9600.18349_15f13a07f09c509c => key removed successfully


==== End of Fixlog 16:18:30 ====
 
Excellent. Please do the following again.

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.
 
Good. Assuming you are still having BSOD issues, would you mind doing another memory test using the following procedure? I know you mentioned you did one previously.

No problem, have fun. When your back let's test your RAM and then we'll check your Hard Drive out. It appears you have two 4GB RAM chips. Let's see if one of them is having issues.

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
 
Brian,
Turns out my motherboard didn't like two of my four sticks of Ram. An one stick was totally bad. No BSOD since removing 8 of 16gb. Not happy with the performance degradation, but i have a much more stable machine. Thoughts on what to do next or let it ride for as long as possible until another BSOD.

Thanks,
BK
 
That's what I suspected unfortunately. Glad you found the bad ones. Now that your machine is stable, are you having issues with Windows Update?
 
no sir not at this time. It checked for updates earlier this morning and as well as myself manually checking.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top