Debugging exception in wininit.exe on boot

When I installed the November monthly security updates on my laptop
something screwed up as I now get a BSOD every time I try to start it.

I managed to use the setup DVD to edit the registry and get a complete
memory dump. Feeding this into windbg gives me this:

Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612

Machine Name:

Kernel base = 0x82251000 PsLoadedModuleList = 0x82368c70 Debug session time:
Mon Mar 9 06:09:22.369 2009 (GMT+13) System Uptime: 0 days 0:01:02.119
Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

****************************************************************************
***

*
*

* Bugcheck Analysis
*

*
*

****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 80da1d90, 80da1edc, 8248f430}

Probably caused by : wininit.exe

Followup: MachineOwner


1: kd> !analyze -v

****************************************************************************
***

*
*

* Bugcheck Analysis
*

*
*

****************************************************************************
***

CRITICAL_OBJECT_TERMINATION (f4)

A process or thread crucial to system operation has unexpectedly exited or
been terminated.

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.

Arguments:

Arg1: 00000003, Process

Arg2: 80da1d90, Terminating object

Arg3: 80da1edc, Process image file name

Arg4: 8248f430, Explanatory message (ascii)

Debugging Details:


PROCESS_OBJECT: 80da1d90

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918db8

MODULE_NAME: wininit

FAULTING_MODULE: 00430000 wininit

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

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:

8ed16ccc 824e6084 000000f4 00000003 80da1d90 nt!KeBugCheckEx+0x1e 8ed16cf0
82433da8 8248f430 80da1edc 80da1e10 nt!PspCatchCriticalBreak+0x73 8ed16d20
82434141 80da1d90 80d7a360 000036b1 nt!PspTerminateAllThreads+0x2c

8ed16d54 822a8a1a 00000000 000036b1 0024fa08 nt!NtTerminateProcess+0x1c1

8ed16d54 76fe9a94 00000000 000036b1 0024fa08 nt!KiFastCallEntry+0x12a

0024f9e8 76fe9134 76fba830 00000000 000036b1 ntdll!KiFastSystemCallRet
0024f9ec 76fba830 00000000 000036b1 00141ca8 ntdll!NtTerminateProcess+0xc

0024fa08 75ad3b68 000036b1 77e8f3b0 ffffffff ntdll!RtlExitUserProcess+0x39
0024fa1c 75a12072 000036b1 0024fa60 75a11fb4 kernel32!ExitProcess+0x12

0024fa28 75a11fb3 000036b1 ac09610c 004450f8 msvcrt!__crtExitProcess+0x17
0024fa60 75a12051 000036b1 00000000 00000000 msvcrt!_cinit+0xea

0024fa74 004398f6 000036b1 94fb450d 00000000 msvcrt!exit+0x11

0024faf8 75af4911 7ffd3000 0024fb44 76fce4b6 wininit!_initterm_e+0x1ba

0024fb04 76fce4b6 7ffd3000 77215336 00000000
kernel32!BaseThreadInitThunk+0xe

0024fb44 76fce489 0043634b 7ffd3000 00000000 ntdll!__RtlUserThreadStart+0x23
0024fb5c 00000000 0043634b 7ffd3000 00000000 ntdll!_RtlUserThreadStart+0x1b

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe

BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe

Followup: MachineOwner


Anyone know what I should now do to find what caused the “This application
has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.” exception?

I would like to get my laptop working again without reinstalling windows and
losing all of my programs and documents.

Thanks,

Leith Bade

xxxxx@leithalweapon.geek.nz

Read this, it would seem you have a virus:

http://support.microsoft.com/kb/299332

On Mon, Mar 9, 2009 at 4:01 AM, Leith Bade wrote:

> When I installed the November monthly security updates on my laptop
> something screwed up as I now get a BSOD every time I try to start it.
>
>
>
> I managed to use the setup DVD to edit the registry and get a complete
> memory dump. Feeding this into windbg gives me this:
>
>
>
> Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
>
> Machine Name:
>
> Kernel base = 0x82251000 PsLoadedModuleList = 0x82368c70 Debug session
> time: Mon Mar 9 06:09:22.369 2009 (GMT+13) System Uptime: 0 days
> 0:01:02.119 Loading Kernel Symbols
> …
>
> …
>
> …
>
> Loading User Symbols
>
> …
>
> Loading unloaded module list
>
> …
>
>
> *****
>
>
>
>
> * Bugcheck
> Analysis
>
>
>
>
>
>

>
>
>
> Use !analyze -v to get detailed debugging information.
>
>
>
> BugCheck F4, {3, 80da1d90, 80da1edc, 8248f430}
>
>
>
> Probably caused by : wininit.exe
>
>
>
> Followup: MachineOwner
>
> ---------
>
>
>
> 1: kd> !analyze -v
>
>
> *****
>
>
>
>
> * Bugcheck
> Analysis
>
>
>
>
>
>

>
>
>
> CRITICAL_OBJECT_TERMINATION (f4)
>
> A process or thread crucial to system operation has unexpectedly exited or
> been terminated.
>
> 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.
>
> Arguments:
>
> Arg1: 00000003, Process
>
> Arg2: 80da1d90, Terminating object
>
> Arg3: 80da1edc, Process image file name
>
> Arg4: 8248f430, Explanatory message (ascii)
>
>
>
> Debugging Details:
>
> ------------------
>
>
>
> PROCESS_OBJECT: 80da1d90
>
>
>
> IMAGE_NAME: wininit.exe
>
>
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 47918db8
>
>
>
> MODULE_NAME: wininit
>
>
>
> FAULTING_MODULE: 00430000 wininit
>
>
>
> 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
>
>
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
>
>
> CURRENT_IRQL: 0
>
>
>
> STACK_TEXT:
>
> 8ed16ccc 824e6084 000000f4 00000003 80da1d90 nt!KeBugCheckEx+0x1e 8ed16cf0
> 82433da8 8248f430 80da1edc 80da1e10 nt!PspCatchCriticalBreak+0x73 8ed16d20
> 82434141 80da1d90 80d7a360 000036b1 nt!PspTerminateAllThreads+0x2c
>
> 8ed16d54 822a8a1a 00000000 000036b1 0024fa08 nt!NtTerminateProcess+0x1c1
>
> 8ed16d54 76fe9a94 00000000 000036b1 0024fa08 nt!KiFastCallEntry+0x12a
>
> 0024f9e8 76fe9134 76fba830 00000000 000036b1 ntdll!KiFastSystemCallRet
> 0024f9ec 76fba830 00000000 000036b1 00141ca8 ntdll!NtTerminateProcess+0xc
>
> 0024fa08 75ad3b68 000036b1 77e8f3b0 ffffffff ntdll!RtlExitUserProcess+0x39
> 0024fa1c 75a12072 000036b1 0024fa60 75a11fb4 kernel32!ExitProcess+0x12
>
> 0024fa28 75a11fb3 000036b1 ac09610c 004450f8 msvcrt! __crtExitProcess+0x17
> 0024fa60 75a12051 000036b1 00000000 00000000 msvcrt!cinit+0xea
>
> 0024fa74 004398f6 000036b1 94fb450d 00000000 msvcrt!exit+0x11
>
> 0024faf8 75af4911 7ffd3000 0024fb44 76fce4b6 wininit!initterm_e+0x1ba
>
> 0024fb04 76fce4b6 7ffd3000 77215336 00000000
> kernel32!BaseThreadInitThunk+0xe
>
> 0024fb44 76fce489 0043634b 7ffd3000 00000000
> ntdll!
RtlUserThreadStart+0x23 0024fb5c 00000000 0043634b 7ffd3000 00000000
> ntdll!_RtlUserThreadStart+0x1b
>
>
>
>
>
> STACK_COMMAND: kb
>
>
>
> FOLLOWUP_NAME: MachineOwner
>
>
>
> FAILURE_BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>
>
>
> BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>
>
>
> Followup: MachineOwner
>
> ---------
>
>
>
> Anyone know what I should now do to find what caused the ?This application
> has failed to start because the application configuration is incorrect.
> Reinstalling the application may fix this problem.? exception?
>
>
>
> I would like to get my laptop working again without reinstalling windows
> and losing all of my programs and documents.
>
>
>
> Thanks,
>
> Leith Bade
>
> xxxxx@leithalweapon.geek.nz
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

That article applies to Win95, et. c. and he is using Vista; are you sure that it’s relevant?

mm

Jim Donelson wrote:

Read this, it would seem you have a virus:

http://support.microsoft.com/kb/299332

On Mon, Mar 9, 2009 at 4:01 AM, Leith Bade > mailto:xxxxx> wrote:
>
> When I installed the November monthly security updates on my laptop
> something screwed up as I now get a BSOD every time I try to start it.
>
>
>
> I managed to use the setup DVD to edit the registry and get a
> complete memory dump. Feeding this into windbg gives me this:
>
>
>
> Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
>
> Machine Name:
>
> Kernel base = 0x82251000 PsLoadedModuleList = 0x82368c70 Debug
> session time: Mon Mar 9 06:09:22.369 2009 (GMT+13) System Uptime: 0
> days 0:01:02.119 Loading Kernel Symbols
> …
>
> …
>
> …
>
> Loading User Symbols
>
> …
>
> Loading unloaded module list
>
> …
>
> ***
>
> *
>
>
> * Bugcheck
> Analysis
>
> *
>
>
>

>
>
>
> Use !analyze -v to get detailed debugging information.
>
>
>
> BugCheck F4, {3, 80da1d90, 80da1edc, 8248f430}
>
>
>
> Probably caused by : wininit.exe
>
>
>
> Followup: MachineOwner
>
> ---------
>
>
>
> 1: kd> !analyze -v
>
> ***
>
> *
>
>
> * Bugcheck
> Analysis
>
> *
>
>
>

>
>
>
> CRITICAL_OBJECT_TERMINATION (f4)
>
> A process or thread crucial to system operation has unexpectedly
> exited or been terminated.
>
> 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.
>
> Arguments:
>
> Arg1: 00000003, Process
>
> Arg2: 80da1d90, Terminating object
>
> Arg3: 80da1edc, Process image file name
>
> Arg4: 8248f430, Explanatory message (ascii)
>
>
>
> Debugging Details:
>
> ------------------
>
>
>
> PROCESS_OBJECT: 80da1d90
>
>
>
> IMAGE_NAME: wininit.exe
>
>
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 47918db8
>
>
>
> MODULE_NAME: wininit
>
>
>
> FAULTING_MODULE: 00430000 wininit
>
>
>
> 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
>
>
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
>
>
> CURRENT_IRQL: 0
>
>
>
> STACK_TEXT:
>
> 8ed16ccc 824e6084 000000f4 00000003 80da1d90 nt!KeBugCheckEx+0x1e
> 8ed16cf0 82433da8 8248f430 80da1edc 80da1e10
> nt!PspCatchCriticalBreak+0x73 8ed16d20 82434141 80da1d90 80d7a360
> 000036b1 nt!PspTerminateAllThreads+0x2c
>
> 8ed16d54 822a8a1a 00000000 000036b1 0024fa08 nt!NtTerminateProcess+0x1c1
>
> 8ed16d54 76fe9a94 00000000 000036b1 0024fa08 nt!KiFastCallEntry+0x12a
>
> 0024f9e8 76fe9134 76fba830 00000000 000036b1
> ntdll!KiFastSystemCallRet 0024f9ec 76fba830 00000000 000036b1
> 00141ca8 ntdll!NtTerminateProcess+0xc
>
> 0024fa08 75ad3b68 000036b1 77e8f3b0 ffffffff
> ntdll!RtlExitUserProcess+0x39 0024fa1c 75a12072 000036b1 0024fa60
> 75a11fb4 kernel32!ExitProcess+0x12
>
> 0024fa28 75a11fb3 000036b1 ac09610c 004450f8
> msvcrt! __crtExitProcess+0x17 0024fa60 75a12051 000036b1 00000000
> 00000000 msvcrt!cinit+0xea
>
> 0024fa74 004398f6 000036b1 94fb450d 00000000 msvcrt!exit+0x11
>
> 0024faf8 75af4911 7ffd3000 0024fb44 76fce4b6 wininit!initterm_e+0x1ba
>
> 0024fb04 76fce4b6 7ffd3000 77215336 00000000
> kernel32!BaseThreadInitThunk+0xe
>
> 0024fb44 76fce489 0043634b 7ffd3000 00000000
> ntdll!
RtlUserThreadStart+0x23 0024fb5c 00000000 0043634b 7ffd3000
> 00000000 ntdll!_RtlUserThreadStart+0x1b
>
>
>
>
>
> STACK_COMMAND: kb
>
>
>
> FOLLOWUP_NAME: MachineOwner
>
>
>
> FAILURE_BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>
>
>
> BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>
>
>
> Followup: MachineOwner
>
> ---------
>
>
>
> Anyone know what I should now do to find what caused the “This
> application has failed to start because the application
> configuration is incorrect. Reinstalling the application may fix
> this problem.” exception?
>
>
>
> I would like to get my laptop working again without reinstalling
> windows and losing all of my programs and documents.
>
>
>
> Thanks,
>
> Leith Bade
>
> xxxxx@leithalweapon.geek.nz mailto:xxxxx
>
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
></mailto:xxxxx></mailto:xxxxx>

No, Actually you are correct. It is used in vista.

On Mon, Mar 9, 2009 at 9:07 AM, Martin O’Brien wrote:

> That article applies to Win95, et. c. and he is using Vista; are you sure
> that it’s relevant?
>
>
> mm
>
> Jim Donelson wrote:
>
>> Read this, it would seem you have a virus:
>>
>> http://support.microsoft.com/kb/299332
>>
>>
>> On Mon, Mar 9, 2009 at 4:01 AM, Leith Bade >> xxxxx@leithalweapon.geek.nz>> wrote:
>>
>> When I installed the November monthly security updates on my laptop
>> something screwed up as I now get a BSOD every time I try to start it.
>>
>>
>> I managed to use the setup DVD to edit the registry and get a
>> complete memory dump. Feeding this into windbg gives me this:
>>
>>
>> Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
>>
>> Machine Name:
>>
>> Kernel base = 0x82251000 PsLoadedModuleList = 0x82368c70 Debug
>> session time: Mon Mar 9 06:09:22.369 2009 (GMT+13) System Uptime: 0
>> days 0:01:02.119 Loading Kernel Symbols
>> …
>>
>> …
>>
>> …
>>
>> Loading User Symbols
>>
>> …
>>
>> Loading unloaded module list
>>
>> …
>>
>>
>> *****
>>
>>
>>
>>
>> * Bugcheck
>> Analysis
>>
>>
>>
>>
>>
>>

>>
>>
>> Use !analyze -v to get detailed debugging information.
>>
>>
>> BugCheck F4, {3, 80da1d90, 80da1edc, 8248f430}
>>
>>
>> Probably caused by : wininit.exe
>>
>>
>> Followup: MachineOwner
>>
>> ---------
>>
>>
>> 1: kd> !analyze -v
>>
>>
>> *****
>>
>>
>>
>>
>> * Bugcheck
>> Analysis
>>
>>
>>
>>
>>
>>

>>
>>
>> CRITICAL_OBJECT_TERMINATION (f4)
>>
>> A process or thread crucial to system operation has unexpectedly
>> exited or been terminated.
>>
>> 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.
>>
>> Arguments:
>>
>> Arg1: 00000003, Process
>>
>> Arg2: 80da1d90, Terminating object
>>
>> Arg3: 80da1edc, Process image file name
>>
>> Arg4: 8248f430, Explanatory message (ascii)
>>
>>
>> Debugging Details:
>>
>> ------------------
>>
>>
>> PROCESS_OBJECT: 80da1d90
>>
>>
>> IMAGE_NAME: wininit.exe
>>
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 47918db8
>>
>>
>> MODULE_NAME: wininit
>>
>>
>> FAULTING_MODULE: 00430000 wininit
>>
>>
>> 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
>>
>>
>> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>>
>>
>> CURRENT_IRQL: 0
>>
>>
>> STACK_TEXT:
>>
>> 8ed16ccc 824e6084 000000f4 00000003 80da1d90 nt!KeBugCheckEx+0x1e
>> 8ed16cf0 82433da8 8248f430 80da1edc 80da1e10
>> nt!PspCatchCriticalBreak+0x73 8ed16d20 82434141 80da1d90 80d7a360
>> 000036b1 nt!PspTerminateAllThreads+0x2c
>>
>> 8ed16d54 822a8a1a 00000000 000036b1 0024fa08
>> nt!NtTerminateProcess+0x1c1
>>
>> 8ed16d54 76fe9a94 00000000 000036b1 0024fa08 nt!KiFastCallEntry+0x12a
>>
>> 0024f9e8 76fe9134 76fba830 00000000 000036b1
>> ntdll!KiFastSystemCallRet 0024f9ec 76fba830 00000000 000036b1
>> 00141ca8 ntdll!NtTerminateProcess+0xc
>>
>> 0024fa08 75ad3b68 000036b1 77e8f3b0 ffffffff
>> ntdll!RtlExitUserProcess+0x39 0024fa1c 75a12072 000036b1 0024fa60
>> 75a11fb4 kernel32!ExitProcess+0x12
>>
>> 0024fa28 75a11fb3 000036b1 ac09610c 004450f8
>> msvcrt! __crtExitProcess+0x17 0024fa60 75a12051 000036b1 00000000
>> 00000000 msvcrt!cinit+0xea
>>
>> 0024fa74 004398f6 000036b1 94fb450d 00000000 msvcrt!exit+0x11
>>
>> 0024faf8 75af4911 7ffd3000 0024fb44 76fce4b6 wininit!initterm_e+0x1ba
>>
>> 0024fb04 76fce4b6 7ffd3000 77215336 00000000
>> kernel32!BaseThreadInitThunk+0xe
>>
>> 0024fb44 76fce489 0043634b 7ffd3000 00000000
>> ntdll!
RtlUserThreadStart+0x23 0024fb5c 00000000 0043634b 7ffd3000
>> 00000000 ntdll!_RtlUserThreadStart+0x1b
>>
>>
>>
>> STACK_COMMAND: kb
>>
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>>
>> FAILURE_BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>>
>>
>> BUCKET_ID: 0xF4_36B1_IMAGE_wininit.exe
>>
>>
>> Followup: MachineOwner
>>
>> ---------
>>
>>
>> Anyone know what I should now do to find what caused the ?This
>> application has failed to start because the application
>> configuration is incorrect. Reinstalling the application may fix
>> this problem.? exception?
>>
>>
>> I would like to get my laptop working again without reinstalling
>> windows and losing all of my programs and documents.
>>
>>
>> Thanks,
>>
>> Leith Bade
>>
>> xxxxx@leithalweapon.geek.nz mailto:xxxxx
>>
>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
> —
>
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
></mailto:xxxxx>