BSOD after November Automatic Update installs


  • Last night Vista's automatic updates notification popped up asking me to install the November set of Vista and Office updates.

    All went fine and I put my computer to sleep as I had some stuff open that I didn't want to close yet.

    Sometime duing the night Vista came out of sleep (presumably to do the scheduled automatic update check), and the next morning I found in in a constant BSOD reboot loop.


    I grabbed the memory dump of the computer using the Vista setup disk's command prompt and fed it into WinDbg.
    The memory dump file's timstamp puts it at 1am in the morning - when the automatic update is scheduled to run, so is the original BSOD not the subsequent ones at startup (curiously no minidump for these).

    Here is WinDbg'd verdict:

    1: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *

    A process or thread crucial to system operation has unexpectedly exited or been
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arg1: 00000003, Process
    Arg2: 92ec0510, Terminating object
    Arg3: 92ec065c, Process image file name
    Arg4: 8248e430, Explanatory message (ascii)

    Debugging Details:

    Page 5211e not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffd600c).  Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffd600c).  Type ".hh dbgerr001" for details

    PROCESS_OBJECT: 92ec0510

    IMAGE_NAME:  wininit.exe


    MODULE_NAME: wininit

    FAULTING_MODULE: 00000000

    PROCESS_NAME:  wininit.exe

    EXCEPTION_CODE: (Win32) 0x36b1 (14001) - This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

    BUGCHECK_STR:  0xF4_36B1



    8aae1ccc 824e5084 000000f4 00000003 92ec0510 nt!KeBugCheckEx+0x1e
    8aae1cf0 82432da8 8248e430 92ec065c 92ec0590 nt!PspCatchCriticalBreak+0x73
    8aae1d20 82433141 92ec0510 92ec2600 000036b1 nt!PspTerminateAllThreads+0x2c
    8aae1d54 822a7a1a 00000000 000036b1 001af8e0 nt!NtTerminateProcess+0x1c1
    8aae1d54 77949a94 00000000 000036b1 001af8e0 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    001af8e0 00000000 00000000 00000000 00000000 0x77949a94


    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  0xF4_36B1_IMAGE_wininit.exe

    BUCKET_ID:  0xF4_36B1_IMAGE_wininit.exe

    Followup: MachineOwner

    As you can see it says that wininit crashed (which from google appears to be XP's equivalent of winlogon) which caused the BSOD. (Possible caused by a hardware glitch during it's sleep awakening)

    I also read that wininit is responsible for replacing system files during startup after an automatic update install.

    So it appears that this may have left some system files screwed hence why it won't boot (crashes right when wininit starts - just before the mouse cursor\GUI normally appears).

    Now the question is how do I fix those screwed files? (Or identify them)

    In XP it was easy to do via the setup CD's recovery install option (basically it deleted then reinstalled all system files).

    I cannot see how to do this in Vista fancy new GUI based setup CD.

    I do not want to reformat as I have far too many programs installed not to mention various documents and files scattered around.

    If this doesn't work I have decided that I will but Ubuntu on my computer and ditch Windows for my day to day activities.
    Thursday, November 20, 2008 12:48 AM

All replies

  • Leith


    Microsoft offers free support for Windows Update issues.


    They are better equipped to handle issues such as this.


    Windows Update No-Charge, Unlimited Support:


    Hope thie helps.


    If this post helps to resolve your issue, click the Mark as Answer button at the top of this message.

    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience
    Saturday, November 22, 2008 12:45 AM