Windows Update not working (Current Error: 80070246)

A

Agraavan

Contributor
Joined
Jul 19, 2014
Posts
40
Good afternoon.

Lately, I have being having a lot of BSoD and after some analysis on some logs (at the end of this post), I have been informed that it may be caused by an old build of my windows, without updates, which is very true.

The problem is, I'm not able to update Windows (7 x64) for quite some time because it keeps popping error messages on me. The first time I took notice, it gave me this error code: 8007370b. After making some research at google, I downloaded and installed the System Update Readiness tool to no avail. Right now, the new error code is: 80070246.

I have followed the pinned topic but the SFCFix was not able to fix anything on its on. Here are some informations that may be helpfull to better understando the problem:

Files Attached:

- SFCFix log
- CBS Folder

I tried to copy the COMPONENTS (at system32/config but it says it is being used and don't complete). Tell me if there is anything else I need to provide. Thanks in advance.



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 7/15/2014 3:36:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071514-24180-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164D3C9, 0xFFFFF880039A0D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 7/15/2014 3:36:23 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164D3C9, 0xFFFFF880039A0D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 7/14/2014 3:20:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071414-28080-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4613)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000D4613, 0xFFFFF88008127070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiusuário
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 7/13/2014 5:27:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071314-22417-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7A447)
Bugcheck code: 0xD1 (0xFFFFF88102949AE0, 0x2, 0x1, 0xFFFFF8800167C447)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/2/2014 10:58:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-23119-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164E3C9, 0xFFFFF88009FA9D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/2/2014 3:17:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-18907-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBFB61)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014F8B61, 0xFFFFF8800319A738, 0xFFFFF88003199FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/2/2014 3:08:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-31949-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A270128, 0xFFFFF8800A26F990, 0xFFFFF800032F22A9)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/2/2014 1:11:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-27268-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5BA35)
Bugcheck code: 0xD1 (0xFFFFF8810EE5DAE0, 0x2, 0x1, 0xFFFFF8800165DA35)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 7/1/2014 12:40:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-26036-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBE45C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014D545C, 0xFFFFF88009B9D738, 0xFFFFF88009B9CFA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 7/1/2014 3:01:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-25287-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x10A85)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000650A85, 0xFFFFF88005BFEAF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Click to expand...
 

Attachments

Hi,

I'll leave the BSOD's for the minute, and pass you on to the BSOD experts once we're done with Windows Update.

SURT has done a lot of heavy lifting when it's come to your corruptions, dealing with practically all of them:

Code: 
 Found 2957 errors
 Fixed 2944 errors
  CSI Manifest Missing Total count: 2
  CSI Manifest and S256H Do Not Match Total count: 2
  CSI Missing Component Key Total count: 585
  Fixed: CSI Missing Component Key.  Total count: 585
  CSI Missing Pinned Component Key Total count: 77
  Fixed: CSI Missing Pinned Component Key.  Total count: 77
  CSI Corrupt Deployment Keyform Total count: 1
  CSI Corrupt Component Keyform Total count: 1
  CSI Missing Identity Total count: 669
  Fixed: CSI Missing Identity.  Total count: 669
  CSI Corrupt Identity Total count: 18
  Fixed: CSI Corrupt Identity.  Total count: 15
  CSI Mismatched Identity Total count: 1
  CSI Missing C Mark Total count: 784
  Fixed: CSI Missing C Mark.  Total count: 784
  CSI C Mark Deployment Missing Total count: 1
  CSI Located Replacement: Invalid (S256H) Total count: 18
  CSI F Mark Value Wrong Total count: 4
  Fixed: CSI F Mark Value Wrong.  Total count: 4
  CSI F Mark Missing Total count: 886
  Fixed: CSI F Mark Missing.  Total count: 886
  CBS Catalog Missing Total count: 1
  Fixed: CBS Catalog Missing.  Total count: 1
  CBS Registry Error Total count: 2
  Fixed: CBS Paired File.  Total count: 1

This has made the log incredibly hard to read, so could you please run SURT once more for me? Once you've done that, can you please run the following script to upload your files to us.

SFCFix CBS & COMPONETS Collection

  1. Download SFCFix.exe using the following link and save the tool to your Desktop: [sfcfixdownload]Download SFCFix[/sfcfixdownload]
  2. Download SFCFix.txt and save this to your Desktop as well: https://dl.dropboxusercontent.com/u...ic/Collect/CBS and COMPONENTS/SFCFix.txt?dl=1
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFix.txt.
  4. Drag the file SFCFix.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles and COMPONENTS hive to our server.


Stephen
 
Done and done.

I ran SURT (Windows6.1-KB947821-v33-x64) three times just to make sure, restarted the PC and just sent the logfiles to the server. BTW, thanks for the readiness.
 
Sorry to double post, but I really need some help, since I have no clue what to do or what may be causing this issue.
 
Sorry, I did not get a notification for the logfiles. I will review them now for you - although I may have to call in another expert at some point depending on what the issue is like.

Regards,
Stephen
 
No problem. I was just afraid to have been forgotten since you guys must recieve a sh*t ton of help request.
 
That's fine! :) If I do forget to reply in 48 or so hours, feel free to bump it, because you're right - we can get overwhelmed by threads at points.

The errors in your log are quite complicated and there are quite a few of them, so I'm not going to be able to fix them all at once. It's going to take multiple fixes, and probably some investigation to fix everything. Let's start with this.

Windows Update Package Replacement

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. Please download the file, Packs.zip from my Dropbox -->here<--and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Winsxs\Manifests


    ​
  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages


    ​
  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log    ​


Stephen
 
Thank you, Stephen. Right now I'm at work and wont be able to run this fix until night, but I'll update it as soon as I can.

Thanks, again.
 
Just to be sure1, I should substitute the files on those directories with the ones on the pack, right?
Just to be sure2, the SURT is the same Windows6.1-KB947821-v33-x64 I mentioned early, right?

If yes to both, I did everything and here is the log:

[edit]I hope this log is supposed to be this big...

EDIT Tekno Venus - I've had to cut the log from your post, zip it and attach it because it was so large it was breaking things :p Congrats on having the largest SURT log I've ever seen! :0
 

Attachments

Last edited by a moderator:
Hi,

Firstly, wow, that SURT log is huge! I've had to attach it to your post.

Unfortunately, I think you put the files in the wrong place, since the fix didn't do anything. It's quite a common mistake, there are other similarly named SURT folders. There shouldn't have been any files in the folder (I don't think), so check you've got the right folder and try again.

Stephen
 
I don't think I did, no. :/

The Manifest Folder on my PC had two files, with the same name as two of those 4 files on the Dropbox-Manifest, I substitute then.
The "Packages" Folder on my PC have two files as well, but the Dropbox-Packages was empty, so I did nothing there.

I'll try to reboot the PC and redo the SURT.

Does it look that complicated? Do you think if I upgrade the Windows to W8.1 it is gonna fix the problem? I'll not be able to do it very soon, but if you don't think it will be fixable, I might see if this is a possibility.
 

Attachments

  • Folder.jpg
    Folder.jpg
    182.8 KB · Views: 4
  • Package.jpg
    Package.jpg
    121.6 KB · Views: 2
Here is the 'new' log.

(Should I be double posting to up the thread and let you know of new developments or editing my previous post?)

Again, Thanks a lot for the help you have given so far, tonight I'll make sure to make a donation.
 

Attachments

Double posting is fine by me :)

Those manifests aren't being taken by SURT, so we may have to go about fixing those another way later. I think I have an idea why they're not being taken, but I shall have to investigate that later.

Regarding the difficulty of this issue, it is definitely a tough issue, but it's certainly far from unrepairable. I don't normally deal with registry corruption threads myself, and will speak to some of the other experts here to get some ideas if I need it. But I think this should be fixable.

I'm going to need some time to review the log files and I'll be back to you. If you don't hear back from me in 72 hours, bump the thread. Feel free to post with any new information you have if you feel it's suitable.

Stephen
 
I'll be waiting, anxiously, to hear from you regarding this issue. When it's all said and done, I'll name my fiftieth son after you, I promise. :)
 
Just a quick update. I've pretty much got a fix together for everything, it's all repairable you'll be glad to hear. Currently reviewing the fix with another expert to make sure I've not made any mistakes, and then I'll post it to you.

I've not forgotten you! :)

Stephen
 
Tekno Venus said:
Just a quick update. I've pretty much got a fix together for everything, it's all repairable you'll be glad to hear. Currently reviewing the fix with another expert to make sure I've not made any mistakes, and then I'll post it to you.

I've not forgotten you! :)

Stephen
Click to expand...
Really glad to hear that ;_;

I was refreshing this thread so much I was afraid I was gonna crash the server. I'm waiting, here's hoping this is gonna resolve the issue, including the constant crashs I have been having.
 
You do know you get email notifications right :p

There's no guarantee this will fix the BSODs, but we have a lot of BSOD specialists here too, so once I'm finished, I'll pass you over to them to do a full analysis on your dumps. :) Unfortunately, our other two experts are currently on holiday, so whilst they're still around, they're not getting back to me so quickly. Shouldn't be long though, thanks for your patience.

Stephen

P.S - Thanks for the donation, much appreciated! :)
 
No problem ;)

Nothing compares to opening the thread and seeing there is a new post. It's quite exhilarating. But sadly, I have being giving you more trouble than I antecipated and you haven't came up with a fix just yet. I'll keep refreshing till I see it, you can bet on it, hehe.
 
No more waiting, lets get down to business! Your fix is going to come in two parts, so don't expect any improvement after this first one. I need to check this fix has worked successfully before the second one. I can't stress the importance of backing up the COMPONENTS hive enough, so be sure to follow the below steps exactly.

Replace COMPONENTS Hive

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. Please download the below file, components.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing a file: components (it has no file extension)
  5. Then navigate to C:\Windows\system32\config and rename the file components to components.bak.
  6. Copy (Ctrl+C) and Paste (Ctrl+V) the components file on your Desktop into this folder.
  7. Run the System Update Readiness Tool (SURT) again and when it finishes installing, attach the log to your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


Components.zip - https://www.dropbox.com/s/dow3tce6i9...COMPONENTS.zip

Note: If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

Regards,
Stephen
 
Last edited:
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