BSODs with KB2778344

Page 1 of 3 123 LastLast

  1. Posts : 34
    Windows 7 Professional 64 bit
       #1

    BSODs with KB2778344


    This morning when booting I got a notification of new updates. As they (11) were downloading and installing I got a Critical Error 41 but the pc restarted without my intervention. Going back in to Updates revealed 5 updates had failed.

    On resuming the process, 4 of the 5 failures installed but then I got a BSOD as it tried to install KB2778344. This time the pc did not restart by itself.

    I so far have not found this particular update reported as causing problems for anyone. I am very concerned as to why it should apparently cause Critical Error 41.

    My pc was returned on Monday after having the overclock restored. It had been tested and remained stable under load for 3 days continuously prior to return. Up until now it has been stable at home. But because of this element I cannot for absolute certainty blame today's Critical Errors on the MS update. The evidence is strongly in favour of the update being the culprit.

    I have tried the MS Update Fixit download without success.

    can anyone throw any light on this issue please.
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    Please follow the Windows Update Posting Instructions and post the requested data.
      My Computer


  3. Posts : 34
    Windows 7 Professional 64 bit
    Thread Starter
       #3

    BSODs with KB2778344


    Thank you for the response.

    I tried to follow the instructions however the CBS zipped folder appears too large at 11.7 Mb to attach.

    When running the SURT it asked if I wanted to install KB947821. I okd but before it completed I got a Critical Error followed by an auto reboot. Returning then to MS Update I found that KB947821 was reported as installed and KB2778344 was awaiting download and install. I tried again to install this once again and got the message...
    Code 80073712 Windows Update encountered an unknown error.
    The retry did not produce a Critical Error this time.

    Do you have any advice about the CBS folder please?
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    You can either zip it (if you haven't already done so) before attaching it or upload it to a fileshare site such as dropbox or SkyDrive, and post a link.
    You could also split it into smaller files
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #5

    Windows crashing during the running of CheckSUR is unusual - and probably going to cause problems, but we should be able to deal with them.
    Please do NOT attempt to install any other updates until we say to - it will complicate things.
    Try running the CheckSUR tool again - see if it completes this time, and post the log
      My Computer


  6. Posts : 34
    Windows 7 Professional 64 bit
    Thread Starter
       #6

    BSODs with KB2778344


    Please see attached zips of CBS folder.

    Attachment 255024
    Attachment 255025
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #7

    The CheckSUR shows a number of problems....
    Code:
    Unavailable repair files:
     winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.17206_none_1f947cafe856e8ab.manifest
     winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_214c9927e5a07856.manifest
     winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_17b2cef2ca377b92.manifest
     winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18043_none_16f7eed5b13fb65b.manifest
     winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.21416_none_20134b75017ca18d.manifest
     winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22209_none_22077944fe983d8d.manifest
     winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.21416_none_15bea122cd1bdf92.manifest
     winsxs\manifests\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.17206_none_153fd25db3f626b0.manifest
     servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_6_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_6_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_7_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_7_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_3_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_6_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_6_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_7_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_7_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0.cat
    I'll post a fix protocol for them later.
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    I've uploaded a file - hdnaa.zip - to my SkyDrive at Noel's SkyDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder hdnaa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

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

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

    Also, please run another SFC /SCANNOW, and post the new CBS.log file - the changes may affect the results.
      My Computer


  9. Posts : 34
    Windows 7 Professional 64 bit
    Thread Starter
       #9

    BSODs with KB2778344


    Just to let you know I have followed your instructions and I'm now again running the installer for KB947821. It has been running for just over 30 minutes and is still 'Copying packages to the Windows Update cache'.

    If this fails to complete what would you say is meant by 'a few hours' in the posting instructions?
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    I would think that anything over 2 hours is unusual
    Anything over 3 hours could indicate a problem.
    After 4 hours, kill it, reboot, and try again or ask for help.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:27.
Find Us