80070246 Error when installing Windows7 Service Pack 1

P

panos

New member
Joined
Oct 27, 2014
Posts
3
Hello,

I constantly get a 80070246 error when trying to install Windows7 Service Pack 1.

The output of SFCFix is the following:

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-10-27 10:54:59.755
Not using a script file.

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

Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-10-27 10:55:56.955
----------------------EOF-----------------------

The contents of CheckSUR.log are the following:

Code: 
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-10-27 11:20

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856a    x86_microsoft-windows-i..chingbase.resources_31bf3856ad364e35_6.1.7600.16385_en-us_206e7969c654ea7e    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi"rosoft-!..angua!epack_3bf3856a@364e35_    x86_microsoft-windows-i..gbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_aca9e370685fc4ba    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguaepack_3bf3856a    x86_microsoft-windows-iis-w3svc.resources_31bf3856ad364e35_6.1.7600.16385_en-us_700efba488390c7c    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_.1.7600@16385_3    x86_microsoft-windows-i..nbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_670f37f447b82e7f    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi    x86_microsoft-windows-iis-caching.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c97cb0357d5500c3    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-"..anguaepack_3    x86_microsoft-windows-i..webengine.resources_31bf3856ad364e35_6.1.7600.16385_en-us_29d31ae7eec138db    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi    x86_microsoft-windows-i..webengine.resources_31bf3856ad364e35_6.1.7600.16385_en-us_29d31ae7eec138db    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-    x86_microsoft-windows-processmodel.resources_31bf3856ad364e35_6.1.7600.16385_en-us_452fda7becf21804    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_    msil_microsoft.web.manag..iisclient.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a2dd1ed1a2ff335    
(f)    CSI C Mark Deployment Missing    0x00000000    c!miÀrosoft-`..angua"epack_3 bf3856a@364e35_.1.7600.16385_33c505c91d5c9869    x86_microsoft-windows-i..lbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2237fa51d57040a7    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..angua    msil_microsoft.web.manag..davclient.resources_31bf3856ad364e35_6.1.7600.16385_en-us_acee5ff0a4855329    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_3bf3856a@364e35_,.1.7600 16385_f 99a62f36c744f    x86_microsoft-windows-i..pprotocol.resources_31bf3856ad364e35_6.1.7600.16385_en-us_342efb42755dff82    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_    x86_microsoft-windows-i..nbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_39435327eb50f24c    

Summary:
Seconds executed: 458
 Found 13 errors
  CSI C Mark Deployment Missing Total count: 13

I also attach the complete contents of CBS folder.

Any help would be appreciated.

Thanks
Panos
 

Attachments

Hello Panos and welcome to Sysnative forums!

The CheckSUR log shows the problem:

Code: 
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856a    x86_microsoft-windows-i..chingbase.resources_31bf3856ad364e35_6.1.7600.16385_en-us_206e7969c654ea7e    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi"rosoft-!..angua!epack_3bf3856a@364e35_    x86_microsoft-windows-i..gbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_aca9e370685fc4ba    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguaepack_3bf3856a    x86_microsoft-windows-iis-w3svc.resources_31bf3856ad364e35_6.1.7600.16385_en-us_700efba488390c7c    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_.1.7600@16385_3    x86_microsoft-windows-i..nbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_670f37f447b82e7f    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi    x86_microsoft-windows-iis-caching.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c97cb0357d5500c3    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-"..anguaepack_3    x86_microsoft-windows-i..webengine.resources_31bf3856ad364e35_6.1.7600.16385_en-us_29d31ae7eec138db    
(f)    CSI C Mark Deployment Missing    0x00000000    c!mi    x86_microsoft-windows-i..webengine.resources_31bf3856ad364e35_6.1.7600.16385_en-us_29d31ae7eec138db    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-    x86_microsoft-windows-processmodel.resources_31bf3856ad364e35_6.1.7600.16385_en-us_452fda7becf21804    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_    msil_microsoft.web.manag..iisclient.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a2dd1ed1a2ff335    
(f)    CSI C Mark Deployment Missing    0x00000000    c!miÀrosoft-`..angua"epack_3 bf3856a@364e35_.1.7600.16385_33c505c91d5c9869    x86_microsoft-windows-i..lbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2237fa51d57040a7    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..angua    msil_microsoft.web.manag..davclient.resources_31bf3856ad364e35_6.1.7600.16385_en-us_acee5ff0a4855329    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_3bf3856a@364e35_,.1.7600 16385_f 99a62f36c744f    x86_microsoft-windows-i..pprotocol.resources_31bf3856ad364e35_6.1.7600.16385_en-us_342efb42755dff82    
(f)    CSI C Mark Deployment Missing    0x00000000    c!microsoft-w..anguagepack_31bf3856ad364e35_    x86_microsoft-windows-i..nbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_39435327eb50f24c

These corruptions are known as bitshifts. Lets take one error as an example:
Code: 
(f)    CSI C Mark Deployment Missing    0x00000000     c!mi[COLOR=#ff0000][B]"[/B][/COLOR]rosoft-[B][COLOR=#ff0000]![/COLOR][/B]..angua[COLOR=#ff0000][B]![/B][/COLOR]epack_3bf3856a[COLOR=#ff0000][B]@[/B][/COLOR]364e35_     x86_microsoft-windows-i..gbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_aca9e370685fc4ba
See the symbols highlighted in bold? Those aren't meant to be there. This type of corruption is typically caused by hardware failure, specifically bad RAM. To know for sure, please follow these instructions to test your RAM: Test RAM With Memtest86+ - Sysnative Forums. Memtest86+ will need to run for at least 8 passes - this will take a few hours so it's best to run it overnight.

Fortunately, RAM is one of the cheaper PC components to replace and it is often possible to return the RAM if it is fairly new. Before I can make a fix, we need to work out if it is or isn't a hardware fault and replace any failed components, otherwise the errors will continue to occur faster than I can fix them.

However, if in the last couple of months you have already found and removed a failed RAM stick, then of course the above doesn't apply :)

Regards,
Stephen
 
Hello Stephen,

Thanks for the reply. I proceeded to a clean install today morning and managed to install or windows updates. I will however run a memtest and let you know about the results. I believed that these errors indicate registry corruption and not a hardware issue, but in any case i will run the mem test.

Thanks
Panos
 
Hi Panos,

Ahh ok - glad to hear it's working again. I still highly recommend you run the RAM test, because if the RAM is faulty as I suspect, the same type of corruptions will occur again on your clean install. It could be in a years time, it could be tomorrow, I have no way of telling, but if the RAM is faulty then errors will occur again.

You are right in saying the errors are a form of registry corruption, however the way it is corrupted tells me that it is due to hardware. These corruptions occur when a binary 1 or 0 changes. These binary 1's and 0's translate to different letters and symbols, and when one of them changes, the character can change completely. For example:

0111 1001 0110 1111 0111 0101
you

becomes

0111 1011 0110 1111 0111 0101
{ou

See how the y became a }. This type of corruption is only ever really caused by faulty RAM (rarely a faulty HDD). Memtest is only a diagnostic tool - it cannot fix the RAM (that's impossible), but it will at least alert you to the problem. You can work out which stick is faulty by testing one RAM stick at a time.

-Stephen
 
You must log in or register to reply here.
Back
Top