Faulting Application w3wp.exe

Faulting Application w3wp.exe

am 01.10.2004 16:17:41 von Richard Bond

My IIS keeps on crashing with the above error.
I have a windows 2003 server with IIS 6.0.
I installed IIS State and it produced the following log the last time IIS
crashed.
To my untrained eye the log does not seem to be telling me anything.
Please could somebody kindly tell me what is going on in this log?
And why does w3wp.exe keep on faulting?

Thanks in Advance
Prax

Opened log file 'C:\iisstate\output\IISState-1104.log'

***********************
Starting new log output
IISState version 3.3.1

Fri Oct 01 11:56:33 2004

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 1104

Note: Thread times are formatted as HH:MM:SS.ms

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


IIS has crashed...
Beginning Analysis
DLL (!FunctionName) that failed:




Thread ID: 18
System Thread ID: d68
Kernel Time: 0:0:0.46
User Time: 0:0:0.187
Thread Type: Idle ASP thread
# ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0260fcf0 77d0612f 0x38734bf9
01 0260fd1c 77d069a5 USER32!InternalCallWinProc+0x1b
02 0260fd94 77d080a0 USER32!UserCallWinProcCheckWow+0x151
03 0260fdf0 77d176d0 USER32!DispatchClientMessage+0xd9
04 0260fe20 77f43868 USER32!__fnINSTRINGNULL+0x35
05 0260fe64 77d073bf ntdll!KiUserCallbackDispatcher+0x13
06 0260fe90 77d07438 USER32!NtUserPeekMessage+0xc
07 0260febc 756336b6 USER32!PeekMessageW+0xa9
08 0260fef0 75633d91 comsvcs!CMessageWorkQueue::Empty+0x14
09 0260ff04 756341f2 comsvcs!CSTAThread::ProcessIdleVector+0x19
0a 0260ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x131
0b 0260ffb8 77e4a990 msvcrt!_endthreadex+0x95
0c 0260ffec 00000000 kernel32!BaseThreadStart+0x34
Closing open log file C:\iisstate\output\IISState-1104.log
Opened log file 'C:\iisstate\output\IISState-1104.log'

***********************
Starting new log output
IISState version 3.3.1

Fri Oct 01 11:56:34 2004

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 1104

Note: Thread times are formatted as HH:MM:SS.ms

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




Thread ID: 0
System Thread ID: b08
Kernel Time: 0:0:0.31
User Time: 0:0:0.140
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fe58 77f43741 SharedUserData!SystemCallStub+0x4
01 0006fe5c 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 0006fecc 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 0006fedc 5a3635ae kernel32!WaitForSingleObject+0xf
04 0006feec 5a364d7d w3dt!WP_CONTEXT::RunMainThreadLoop+0xe
05 0006fef4 5a3a1d98 w3dt!UlAtqStartListen+0x2d
06 0006ff00 5a3a5d54 w3core!W3_SERVER::StartListen+0x8e
07 0006ff0c 010017af w3core!UlW3Start+0xea
08 0006ff44 0100195e w3wp!wmain+0x236
09 0006ffc0 77e4f38c w3wp!wmainCRTStartup+0x12f
0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23




Thread ID: 1
System Thread ID: 98c
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 009fff9c 77f4262b SharedUserData!SystemCallStub+0x4
01 009fffa0 77f6b5b2 ntdll!NtDelayExecution+0xc
02 009fffb8 77e4a990 ntdll!RtlpTimerThread+0x45
03 009fffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 2
System Thread ID: 69c
Kernel Time: 0:0:0.156
User Time: 0:0:3.203
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 026efdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 026efdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 026efe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 026efed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 026efef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 026eff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 026effb8 77e4a990 msvcrt!_endthreadex+0x95
07 026effec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 3
System Thread ID: a18
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00a3ff70 77f430c7 SharedUserData!SystemCallStub+0x4
01 00a3ff74 77f7e6ae ntdll!ZwRemoveIoCompletion+0xc
02 00a3ffb8 77e4a990 ntdll!RtlpWorkerThread+0x3b
03 00a3ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 4
System Thread ID: 9b8
Kernel Time: 0:0:0.453
User Time: 0:0:0.515
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00caff28 77f430c7 SharedUserData!SystemCallStub+0x4
01 00caff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
02 00caff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
03 00caff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
04 00caffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
05 00caffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
06 00caffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 5
System Thread ID: 97c
Kernel Time: 0:0:0.250
User Time: 0:0:0.468
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00ceff28 77f430c7 SharedUserData!SystemCallStub+0x4
01 00ceff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
02 00ceff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
03 00ceff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
04 00ceffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
05 00ceffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
06 00ceffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 6
System Thread ID: c40
Kernel Time: 0:0:0.171
User Time: 0:0:0.375
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d2ff28 77f430c7 SharedUserData!SystemCallStub+0x4
01 00d2ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
02 00d2ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
03 00d2ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
04 00d2ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
05 00d2ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
06 00d2ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 7
System Thread ID: fc4
Kernel Time: 0:0:0.156
User Time: 0:0:0.218
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d6ff28 77f430c7 SharedUserData!SystemCallStub+0x4
01 00d6ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
02 00d6ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
03 00d6ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
04 00d6ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
05 00d6ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
06 00d6ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 8
System Thread ID: 8d4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00e2fcec 77f4372d SharedUserData!SystemCallStub+0x4
01 00e2fcf0 77f75297 ntdll!NtWaitForMultipleObjects+0xc
02 00e2ffb8 77e4a990 ntdll!RtlpWaitThread+0x158
03 00e2ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 9
System Thread ID: 79c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 016eff14 77f43741 SharedUserData!SystemCallStub+0x4
01 016eff18 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 016eff88 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 016eff98 5a3a51f7 kernel32!WaitForSingleObject+0xf
04 016effb8 77e4a990 w3core!HTTP_COMPRESSION::CompressionThread+0x85
05 016effc4 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 10
System Thread ID: aa0
Kernel Time: 0:0:0.140
User Time: 0:0:2.234
Thread Type: Jet DB Query. Possible ASP Page
Executing Page: M:\WORLDPANEL\WORLDPANEL\DBROWSERSECURE\TABLEDATA.ASP

# ChildEBP RetAddr
00 0395d340 04162888 msjet40!JetBeginSession+0x14e
WARNING: Frame IP not in any known module. Following frames may be wrong.
01 0395d4cc 00000053 0x4162888




Thread ID: 11
System Thread ID: cec
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0176ff8c 77f4262b SharedUserData!SystemCallStub+0x4
01 0176ff90 77f6f0fc ntdll!NtDelayExecution+0xc
02 0176ffb8 77e4a990 ntdll!RtlpIOWorkerThread+0x3d
03 0176ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 12
System Thread ID: b40
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 0236ff14 77f43741 SharedUserData!SystemCallStub+0x4
01 0236ff18 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 0236ff88 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 0236ff98 70a05c99 kernel32!WaitForSingleObject+0xf
04 0236ffb4 70a0625a asp!CApplnCleanupMgr::ApplnCleanupDoWork+0x19
05 0236ffb8 77e4a990 asp!CApplnCleanupMgr::ApplnCleanupThread+0xa
06 0236ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 13
System Thread ID: 320
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 024afe1c 77f4372d SharedUserData!SystemCallStub+0x4
01 024afe20 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 024afec8 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 024aff24 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 024aff40 70a183cc USER32!MsgWaitForMultipleObjects+0x1d
05 024aff80 77bbb9c3 asp!CMTACallbackThread::Thread+0x4c
06 024aff8c 00000000 msvcrt!free+0xc8




Thread ID: 14
System Thread ID: c2c
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 024efefc 77f43741 SharedUserData!SystemCallStub+0x4
01 024eff00 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 024eff70 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 024eff80 709f4800 kernel32!WaitForSingleObject+0xf
04 024effb4 77f5cd6b asp!CViperReqManager::WatchThread+0x65




Thread ID: 15
System Thread ID: 478
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0254fef0 77f43741 SharedUserData!SystemCallStub+0x4
01 0254fef4 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 0254ff64 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 0254ff74 75630e16 kernel32!WaitForSingleObject+0xf
04 0254ff84 77bc91ed
comsvcs!CSTAThreadPool::LoadBalanceThreadControlLoop+0x25
05 0254ffb8 77e4a990 msvcrt!_endthreadex+0x95
06 0254ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 16
System Thread ID: f34
Kernel Time: 0:0:0.0
User Time: 0:0:0.15
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0258fee8 77f43741 SharedUserData!SystemCallStub+0x4
01 0258feec 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 0258ff5c 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 0258ff6c 756308f3 kernel32!WaitForSingleObject+0xf
04 0258ff84 77bc91ed comsvcs!CSTAThreadPool::KillThreadControlLoop+0x21
05 0258ffb8 77e4a990 msvcrt!_endthreadex+0x95
06 0258ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 17
System Thread ID: 4f4
Kernel Time: 0:0:0.62
User Time: 0:0:0.46
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 025cfdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 025cfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 025cfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 025cfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 025cfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 025cff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 025cffb8 77e4a990 msvcrt!_endthreadex+0x95
07 025cffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 18
System Thread ID: d68
Kernel Time: 0:0:0.46
User Time: 0:0:0.187
Thread Type: Idle ASP thread
# ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0260fcf0 77d0612f 0x38734bf9
01 0260fd1c 77d069a5 USER32!InternalCallWinProc+0x1b
02 0260fd94 77d080a0 USER32!UserCallWinProcCheckWow+0x151
03 0260fdf0 77d176d0 USER32!DispatchClientMessage+0xd9
04 0260fe20 77f43868 USER32!__fnINSTRINGNULL+0x35
05 0260fe64 77d073bf ntdll!KiUserCallbackDispatcher+0x13
06 0260fe90 77d07438 USER32!NtUserPeekMessage+0xc
07 0260febc 756336b6 USER32!PeekMessageW+0xa9
08 0260fef0 75633d91 comsvcs!CMessageWorkQueue::Empty+0x14
09 0260ff04 756341f2 comsvcs!CSTAThread::ProcessIdleVector+0x19
0a 0260ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x131
0b 0260ffb8 77e4a990 msvcrt!_endthreadex+0x95
0c 0260ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 19
System Thread ID: 6a8
Kernel Time: 0:0:0.15
User Time: 0:0:0.15
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0264fdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 0264fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 0264fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 0264fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 0264fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 0264ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 0264ffb8 77e4a990 msvcrt!_endthreadex+0x95
07 0264ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 20
System Thread ID: 954
Kernel Time: 0:0:0.31
User Time: 0:0:0.62
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0268fdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 0268fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 0268fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 0268fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 0268fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 0268ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 0268ffb8 77e4a990 msvcrt!_endthreadex+0x95
07 0268ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 21
System Thread ID: ae0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 02ccff10 77f43741 SharedUserData!SystemCallStub+0x4
01 02ccff14 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 02ccff84 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 02ccff94 02a038a9 kernel32!WaitForSingleObject+0xf
04 02ccffb8 77e4a990 oledb32!ReleaseResourceThread+0x54
05 02ccffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 22
System Thread ID: c04
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 02d0ff08 77f43741 SharedUserData!SystemCallStub+0x4
01 02d0ff0c 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 02d0ff7c 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 02d0ff8c 02a038b9 kernel32!WaitForSingleObject+0xf
04 02d0ffb8 77e4a990 oledb32!ResetResourceThread+0x84
05 02d0ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 23
System Thread ID: b44
Kernel Time: 0:0:0.31
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 02d4fd04 77f43741 SharedUserData!SystemCallStub+0x4
01 02d4fd08 77e41817 ntdll!ZwWaitForSingleObject+0xc
02 02d4fd78 77e4168f kernel32!WaitForSingleObjectEx+0xac
03 02d4fd88 7561065c kernel32!WaitForSingleObject+0xf
04 02d4ffb8 77e4a990 comsvcs!PingThread+0xea
05 02d4ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 24
System Thread ID: f68
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 02f5ff88 77f4372d SharedUserData!SystemCallStub+0x4
01 02f5ff8c 71c63620 ntdll!NtWaitForMultipleObjects+0xc
02 02f5ffb8 77e4a990 NETAPI32!NetbiosWaiter+0x71
03 02f5ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 25
System Thread ID: 904
Kernel Time: 0:0:0.234
User Time: 0:0:1.46
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0829fdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 0829fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 0829fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 0829fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 0829fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 0829ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 0829ffb8 77e4a990 msvcrt!_endthreadex+0x95
07 0829ffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 26
System Thread ID: b74
Kernel Time: 0:0:1.484
User Time: 0:0:8.93
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 082dfdcc 77f4372d SharedUserData!SystemCallStub+0x4
01 082dfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 082dfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
03 082dfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
04 082dfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
05 082dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
06 082dffb8 77e4a990 msvcrt!_endthreadex+0x95
07 082dffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 27
System Thread ID: 30c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
succeeded
Loaded Son of Strike data table version 5 from
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll"
Thread 27
Not a managed thread.


Begin System Thread Information

# ChildEBP RetAddr
00 0d4efe74 77f4372d SharedUserData!SystemCallStub+0x4
01 0d4efe78 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 0d4eff20 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a
03 0d4eff38 791d25d5 kernel32!WaitForMultipleObjects+0x17
04 0d4effa0 791d254c mscorwks!DebuggerRCThread::MainLoop+0x90
05 0d4effb0 791d4d50 mscorwks!DebuggerRCThread::ThreadProc+0x68
06 0d4effb8 77e4a990 mscorwks!DebuggerRCThread::ThreadProcStatic+0xb
07 0d4effec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 28
System Thread ID: eb0
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
Thread 28
ESP EIP


Begin System Thread Information

# ChildEBP RetAddr
00 0f5cfe90 77f4372d SharedUserData!SystemCallStub+0x4
01 0f5cfe94 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
02 0f5cff3c 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a
03 0f5cff54 79262a5f kernel32!WaitForMultipleObjects+0x17
04 0f5cff74 791bbea4 mscorwks!WaitForFinalizerEvent+0x5a
05 0f5cffb8 77e4a990 mscorwks!GCHeap::FinalizerThreadStart+0x96
06 0f5cffec 00000000 kernel32!BaseThreadStart+0x34




Thread ID: 29
System Thread ID: c64
Kernel Time: 0:0:0.15
User Time: 0:0:0.0

Re: Faulting Application w3wp.exe

am 01.10.2004 20:02:18 von patfilot

What is probably happening is a dll (COM dll) is unloading out from under
IIS and is causing the crash.

A dump could tell us the dll that caused it, but 2 that are known (and you
could check to see if they are installed - if so contact the vendor(s) and
see if there is an update available) are:
ASPIMAGE.dll
WebReGIF.dll

Or you could contact MS-Support for more guidance and they could tell you
which dll caused it.


Pat


"Richard Bond" wrote in message
news:O%23PRrF8pEHA.1296@TK2MSFTNGP12.phx.gbl...
> My IIS keeps on crashing with the above error.
> I have a windows 2003 server with IIS 6.0.
> I installed IIS State and it produced the following log the last time IIS
> crashed.
> To my untrained eye the log does not seem to be telling me anything.
> Please could somebody kindly tell me what is going on in this log?
> And why does w3wp.exe keep on faulting?
>
> Thanks in Advance
> Prax
>
> Opened log file 'C:\iisstate\output\IISState-1104.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Fri Oct 01 11:56:33 2004
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 1104
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
> IIS has crashed...
> Beginning Analysis
> DLL (!FunctionName) that failed:
>
>
>
>
> Thread ID: 18
> System Thread ID: d68
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.187
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 00 0260fcf0 77d0612f 0x38734bf9
> 01 0260fd1c 77d069a5 USER32!InternalCallWinProc+0x1b
> 02 0260fd94 77d080a0 USER32!UserCallWinProcCheckWow+0x151
> 03 0260fdf0 77d176d0 USER32!DispatchClientMessage+0xd9
> 04 0260fe20 77f43868 USER32!__fnINSTRINGNULL+0x35
> 05 0260fe64 77d073bf ntdll!KiUserCallbackDispatcher+0x13
> 06 0260fe90 77d07438 USER32!NtUserPeekMessage+0xc
> 07 0260febc 756336b6 USER32!PeekMessageW+0xa9
> 08 0260fef0 75633d91 comsvcs!CMessageWorkQueue::Empty+0x14
> 09 0260ff04 756341f2 comsvcs!CSTAThread::ProcessIdleVector+0x19
> 0a 0260ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x131
> 0b 0260ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 0c 0260ffec 00000000 kernel32!BaseThreadStart+0x34
> Closing open log file C:\iisstate\output\IISState-1104.log
> Opened log file 'C:\iisstate\output\IISState-1104.log'
>
> ***********************
> Starting new log output
> IISState version 3.3.1
>
> Fri Oct 01 11:56:34 2004
>
> OS = Windows 2003 Server
> Executable: w3wp.exe
> PID = 1104
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
>
>
>
>
> Thread ID: 0
> System Thread ID: b08
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.140
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 0006fe58 77f43741 SharedUserData!SystemCallStub+0x4
> 01 0006fe5c 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 0006fecc 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 0006fedc 5a3635ae kernel32!WaitForSingleObject+0xf
> 04 0006feec 5a364d7d w3dt!WP_CONTEXT::RunMainThreadLoop+0xe
> 05 0006fef4 5a3a1d98 w3dt!UlAtqStartListen+0x2d
> 06 0006ff00 5a3a5d54 w3core!W3_SERVER::StartListen+0x8e
> 07 0006ff0c 010017af w3core!UlW3Start+0xea
> 08 0006ff44 0100195e w3wp!wmain+0x236
> 09 0006ffc0 77e4f38c w3wp!wmainCRTStartup+0x12f
> 0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
>
>
>
> Thread ID: 1
> System Thread ID: 98c
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 009fff9c 77f4262b SharedUserData!SystemCallStub+0x4
> 01 009fffa0 77f6b5b2 ntdll!NtDelayExecution+0xc
> 02 009fffb8 77e4a990 ntdll!RtlpTimerThread+0x45
> 03 009fffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 2
> System Thread ID: 69c
> Kernel Time: 0:0:0.156
> User Time: 0:0:3.203
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 026efdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 026efdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 026efe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 026efed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 026efef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 026eff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 026effb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 026effec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 3
> System Thread ID: a18
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00a3ff70 77f430c7 SharedUserData!SystemCallStub+0x4
> 01 00a3ff74 77f7e6ae ntdll!ZwRemoveIoCompletion+0xc
> 02 00a3ffb8 77e4a990 ntdll!RtlpWorkerThread+0x3b
> 03 00a3ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 4
> System Thread ID: 9b8
> Kernel Time: 0:0:0.453
> User Time: 0:0:0.515
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00caff28 77f430c7 SharedUserData!SystemCallStub+0x4
> 01 00caff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
> 02 00caff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
> 03 00caff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
> 04 00caffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
> 05 00caffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
> 06 00caffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 5
> System Thread ID: 97c
> Kernel Time: 0:0:0.250
> User Time: 0:0:0.468
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00ceff28 77f430c7 SharedUserData!SystemCallStub+0x4
> 01 00ceff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
> 02 00ceff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
> 03 00ceff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
> 04 00ceffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
> 05 00ceffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
> 06 00ceffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 6
> System Thread ID: c40
> Kernel Time: 0:0:0.171
> User Time: 0:0:0.375
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d2ff28 77f430c7 SharedUserData!SystemCallStub+0x4
> 01 00d2ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
> 02 00d2ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
> 03 00d2ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
> 04 00d2ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
> 05 00d2ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
> 06 00d2ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 7
> System Thread ID: fc4
> Kernel Time: 0:0:0.156
> User Time: 0:0:0.218
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00d6ff28 77f430c7 SharedUserData!SystemCallStub+0x4
> 01 00d6ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
> 02 00d6ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
> 03 00d6ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
> 04 00d6ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
> 05 00d6ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
> 06 00d6ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 8
> System Thread ID: 8d4
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00e2fcec 77f4372d SharedUserData!SystemCallStub+0x4
> 01 00e2fcf0 77f75297 ntdll!NtWaitForMultipleObjects+0xc
> 02 00e2ffb8 77e4a990 ntdll!RtlpWaitThread+0x158
> 03 00e2ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 9
> System Thread ID: 79c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: HTTP Compression Thread
> # ChildEBP RetAddr
> 00 016eff14 77f43741 SharedUserData!SystemCallStub+0x4
> 01 016eff18 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 016eff88 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 016eff98 5a3a51f7 kernel32!WaitForSingleObject+0xf
> 04 016effb8 77e4a990 w3core!HTTP_COMPRESSION::CompressionThread+0x85
> 05 016effc4 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 10
> System Thread ID: aa0
> Kernel Time: 0:0:0.140
> User Time: 0:0:2.234
> Thread Type: Jet DB Query. Possible ASP Page
> Executing Page: M:\WORLDPANEL\WORLDPANEL\DBROWSERSECURE\TABLEDATA.ASP
>
> # ChildEBP RetAddr
> 00 0395d340 04162888 msjet40!JetBeginSession+0x14e
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 01 0395d4cc 00000053 0x4162888
>
>
>
>
> Thread ID: 11
> System Thread ID: cec
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0176ff8c 77f4262b SharedUserData!SystemCallStub+0x4
> 01 0176ff90 77f6f0fc ntdll!NtDelayExecution+0xc
> 02 0176ffb8 77e4a990 ntdll!RtlpIOWorkerThread+0x3d
> 03 0176ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 12
> System Thread ID: b40
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: ASP
> Executing Page: Unable to locate ASP page
>
> # ChildEBP RetAddr
> 00 0236ff14 77f43741 SharedUserData!SystemCallStub+0x4
> 01 0236ff18 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 0236ff88 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 0236ff98 70a05c99 kernel32!WaitForSingleObject+0xf
> 04 0236ffb4 70a0625a asp!CApplnCleanupMgr::ApplnCleanupDoWork+0x19
> 05 0236ffb8 77e4a990 asp!CApplnCleanupMgr::ApplnCleanupThread+0xa
> 06 0236ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 13
> System Thread ID: 320
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: ASP
> Executing Page: Unable to locate ASP page
>
> # ChildEBP RetAddr
> 00 024afe1c 77f4372d SharedUserData!SystemCallStub+0x4
> 01 024afe20 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 024afec8 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 024aff24 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 024aff40 70a183cc USER32!MsgWaitForMultipleObjects+0x1d
> 05 024aff80 77bbb9c3 asp!CMTACallbackThread::Thread+0x4c
> 06 024aff8c 00000000 msvcrt!free+0xc8
>
>
>
>
> Thread ID: 14
> System Thread ID: c2c
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Type: ASP
> Executing Page: Unable to locate ASP page
>
> # ChildEBP RetAddr
> 00 024efefc 77f43741 SharedUserData!SystemCallStub+0x4
> 01 024eff00 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 024eff70 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 024eff80 709f4800 kernel32!WaitForSingleObject+0xf
> 04 024effb4 77f5cd6b asp!CViperReqManager::WatchThread+0x65
>
>
>
>
> Thread ID: 15
> System Thread ID: 478
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0254fef0 77f43741 SharedUserData!SystemCallStub+0x4
> 01 0254fef4 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 0254ff64 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 0254ff74 75630e16 kernel32!WaitForSingleObject+0xf
> 04 0254ff84 77bc91ed
> comsvcs!CSTAThreadPool::LoadBalanceThreadControlLoop+0x25
> 05 0254ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 06 0254ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 16
> System Thread ID: f34
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.15
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0258fee8 77f43741 SharedUserData!SystemCallStub+0x4
> 01 0258feec 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 0258ff5c 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 0258ff6c 756308f3 kernel32!WaitForSingleObject+0xf
> 04 0258ff84 77bc91ed comsvcs!CSTAThreadPool::KillThreadControlLoop+0x21
> 05 0258ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 06 0258ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 17
> System Thread ID: 4f4
> Kernel Time: 0:0:0.62
> User Time: 0:0:0.46
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 025cfdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 025cfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 025cfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 025cfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 025cfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 025cff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 025cffb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 025cffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 18
> System Thread ID: d68
> Kernel Time: 0:0:0.46
> User Time: 0:0:0.187
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 00 0260fcf0 77d0612f 0x38734bf9
> 01 0260fd1c 77d069a5 USER32!InternalCallWinProc+0x1b
> 02 0260fd94 77d080a0 USER32!UserCallWinProcCheckWow+0x151
> 03 0260fdf0 77d176d0 USER32!DispatchClientMessage+0xd9
> 04 0260fe20 77f43868 USER32!__fnINSTRINGNULL+0x35
> 05 0260fe64 77d073bf ntdll!KiUserCallbackDispatcher+0x13
> 06 0260fe90 77d07438 USER32!NtUserPeekMessage+0xc
> 07 0260febc 756336b6 USER32!PeekMessageW+0xa9
> 08 0260fef0 75633d91 comsvcs!CMessageWorkQueue::Empty+0x14
> 09 0260ff04 756341f2 comsvcs!CSTAThread::ProcessIdleVector+0x19
> 0a 0260ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x131
> 0b 0260ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 0c 0260ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 19
> System Thread ID: 6a8
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.15
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0264fdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 0264fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 0264fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0264fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 0264fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 0264ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 0264ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 0264ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 20
> System Thread ID: 954
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.62
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0268fdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 0268fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 0268fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0268fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 0268fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 0268ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 0268ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 0268ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 21
> System Thread ID: ae0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 02ccff10 77f43741 SharedUserData!SystemCallStub+0x4
> 01 02ccff14 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 02ccff84 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 02ccff94 02a038a9 kernel32!WaitForSingleObject+0xf
> 04 02ccffb8 77e4a990 oledb32!ReleaseResourceThread+0x54
> 05 02ccffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 22
> System Thread ID: c04
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 02d0ff08 77f43741 SharedUserData!SystemCallStub+0x4
> 01 02d0ff0c 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 02d0ff7c 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 02d0ff8c 02a038b9 kernel32!WaitForSingleObject+0xf
> 04 02d0ffb8 77e4a990 oledb32!ResetResourceThread+0x84
> 05 02d0ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 23
> System Thread ID: b44
> Kernel Time: 0:0:0.31
> User Time: 0:0:0.0
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 02d4fd04 77f43741 SharedUserData!SystemCallStub+0x4
> 01 02d4fd08 77e41817 ntdll!ZwWaitForSingleObject+0xc
> 02 02d4fd78 77e4168f kernel32!WaitForSingleObjectEx+0xac
> 03 02d4fd88 7561065c kernel32!WaitForSingleObject+0xf
> 04 02d4ffb8 77e4a990 comsvcs!PingThread+0xea
> 05 02d4ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 24
> System Thread ID: f68
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 02f5ff88 77f4372d SharedUserData!SystemCallStub+0x4
> 01 02f5ff8c 71c63620 ntdll!NtWaitForMultipleObjects+0xc
> 02 02f5ffb8 77e4a990 NETAPI32!NetbiosWaiter+0x71
> 03 02f5ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 25
> System Thread ID: 904
> Kernel Time: 0:0:0.234
> User Time: 0:0:1.46
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 0829fdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 0829fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 0829fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0829fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 0829fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 0829ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 0829ffb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 0829ffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 26
> System Thread ID: b74
> Kernel Time: 0:0:1.484
> User Time: 0:0:8.93
> Thread Status: Thread is in a WAIT state.
> Thread Type: Idle ASP thread
> # ChildEBP RetAddr
> 00 082dfdcc 77f4372d SharedUserData!SystemCallStub+0x4
> 01 082dfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 082dfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 082dfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
> 04 082dfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
> 05 082dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
> 06 082dffb8 77e4a990 msvcrt!_endthreadex+0x95
> 07 082dffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 27
> System Thread ID: 30c
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
> succeeded
> Loaded Son of Strike data table version 5 from
> "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll"
> Thread 27
> Not a managed thread.
>
>
> Begin System Thread Information
>
> # ChildEBP RetAddr
> 00 0d4efe74 77f4372d SharedUserData!SystemCallStub+0x4
> 01 0d4efe78 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 0d4eff20 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0d4eff38 791d25d5 kernel32!WaitForMultipleObjects+0x17
> 04 0d4effa0 791d254c mscorwks!DebuggerRCThread::MainLoop+0x90
> 05 0d4effb0 791d4d50 mscorwks!DebuggerRCThread::ThreadProc+0x68
> 06 0d4effb8 77e4a990 mscorwks!DebuggerRCThread::ThreadProcStatic+0xb
> 07 0d4effec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 28
> System Thread ID: eb0
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
> Thread Status: Thread is in a WAIT state.
> Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
> Thread 28
> ESP EIP
>
>
> Begin System Thread Information
>
> # ChildEBP RetAddr
> 00 0f5cfe90 77f4372d SharedUserData!SystemCallStub+0x4
> 01 0f5cfe94 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
> 02 0f5cff3c 77e4b0e4 kernel32!WaitForMultipleObjectsEx+0x11a
> 03 0f5cff54 79262a5f kernel32!WaitForMultipleObjects+0x17
> 04 0f5cff74 791bbea4 mscorwks!WaitForFinalizerEvent+0x5a
> 05 0f5cffb8 77e4a990 mscorwks!GCHeap::FinalizerThreadStart+0x96
> 06 0f5cffec 00000000 kernel32!BaseThreadStart+0x34
>
>
>
>
> Thread ID: 29
> System Thread ID: c64
> Kernel Time: 0:0:0.15
> User Time: 0:0:0.0
>
>

Re: faulting application w3wp.exe

am 01.04.2008 14:18:04 von Beth

There are other Universities and other departments at ours that are using
this same filter version. If it's a bug, wouldn't we all be down? We'll
investigate this more. Thanks for the assistance.

"David Wang" wrote:

> Actually, it is that the filter has had the bug for all this time; it
> just started to show up now for some reason. Since you clearly cannot
> control when it shows up, you have to fix the bug.
>
> Another way to look at it. Suppose the filter has a line of code that
> looks like this:
>
> if today > 1/1/2009 then crash
>
>
> The filter will work for months without crashing, until midnight
> 1/1/2009, at which point it will always crash. Clearly, the bug has
> been there for months, will not appear until 1/1/2009, and the code
> logic is clearly undesirable.
>
> The amount of time that the code "works" has no correlation to whether
> the code is actually a bug or not. Some bugs take a long time to show
> up; others appear quickly. The only thing you can do is fix the code
> logic.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
> On Mar 20, 5:06 am, Beth wrote:
> > So even though this filter has worked for weeks...it can just get a bug now
> > and stop working?
> >
> > We will work on the filter.
> >
> >
> >
> > "David Wang" wrote:
> > > You have a third party product installed on the server which installed
> > > an ISAPI Filter named Cosign.dll. It has a bug that is crashing the
> > > w3wp.exe. Please contact support for that product to resolve the
> > > issue. Other than you stop using that third party product, no one else
> > > can help.
> >
> > > //David
> > >http://w3-4u.blogspot.com
> > >http://blogs.msdn.com/David.Wang
> > > //
> >
> > > On Mar 19, 1:38 pm, Beth wrote:
> > > > We are receiving this error: faulting application w3wp.exe , version
> > > > 6.0.3790.3959, faulting module ntdll.dll, version 5.2.3790.3959, fault
> > > > address 0x0002b65d.
> >
> > > > We also got the same error with inetinfo.exe but now they are just w3wp.dll.
> > > > I ran IISstate when we had the inetinfo errors but I can't get IIS state to
> > > > work with w3wp.exe errors.
> >
> > > > I'm not an experienced IIS user, so any help would be most appreciated.. Half
> > > > of our web-sites are down that use Cosign dll ISAPI filter.
> >
> > > > Prior IISState error:
> > > > Opened log file 'C:\iisstate\output\IISState-3816.log'
> >
> > > > ***********************
> > > > Starting new log output
> > > > IISState version 3.3.1
> >
> > > > Mon Mar 17 16:43:02 2008
> >
> > > > OS = Windows 2003 Server
> > > > Executable: inetinfo.exe
> > > > PID = 3816
> >
> > > > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > > > ***********************
> >
> > > > IIS has crashed...
> > > > Beginning Analysis
> > > > DLL (!FunctionName) that failed: ntdll!RtlpCoalesceFreeBlocks
> >
> > > > Thread ID: 8
> > > > System Thread ID: 1380
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> > > > C:\Program Files\IISCosign\Cosign.dll -
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 01a2a1b4 7c82a82b ntdll!RtlpCoalesceFreeBlocks+0x12a
> > > > 01 01a2a29c 10009fe5 ntdll!RtlFreeHeap+0x38e
> > > > WARNING: Stack unwind information not available. Following frames may be
> > > > wrong.
> > > > 02 01a2a2dc 10008740 Cosign!HttpFilterProc+0x2d95
> > > > 03 025741f4 02572500 Cosign!HttpFilterProc+0x14f0
> > > > 04 02574208 5aadba92 0x2572500
> > > > 05 071a0002 00000000 0x5aadba92
> > > > Closing open log file C:\iisstate\output\IISState-3816.log
> > > > Opened log file 'C:\iisstate\output\IISState-3816.log'
> >
> > > > ***********************
> > > > Starting new log output
> > > > IISState version 3.3.1
> >
> > > > Mon Mar 17 16:43:03 2008
> >
> > > > OS = Windows 2003 Server
> > > > Executable: inetinfo.exe
> > > > PID = 3816
> >
> > > > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > > > ***********************
> >
> > > > Thread ID: 0
> > > > System Thread ID: e70
> > > > Kernel Time: 0:0:0.15
> > > > User Time: 0:0:0.0
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 0006f99c 7c82776b ntdll!KiFastSystemCallRet
> > > > 01 0006f9a0 77e418b2 ntdll!NtReadFile+0xc
> > > > 02 0006fa08 77f65edb kernel32!ReadFile+0x16c
> > > > 03 0006fa34 77f65f82 ADVAPI32!ScGetPipeInput+0x2a
> > > > 04 0006faa8 77fb75af ADVAPI32!ScDispatcherLoop+0x51
> > > > 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
> > > > 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
> > > > 07 0006ff44 0100339d inetinfo!main+0x117
> > > > 08 0006ffc0 77e6f23b inetinfo!mainCRTStartup+0x12f
> > > > 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
> >
> > > > Thread ID: 1
> > > > System Thread ID: 1148
> > > > Kernel Time: 0:0:0.187
> > > > User Time: 0:0:0.0
> > > > Thread Status: Thread is in a WAIT state.
> > > > Thread Type: HTTP Compression Thread
> > > > # ChildEBP RetAddr
> > > > 00 0097fb3c 7c827d0b ntdll!KiFastSystemCallRet
> > > > 01 0097fb40 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > > 02 0097fbb0 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > > 03 0097fbc4 5a364662 kernel32!WaitForSingleObject+0x12
> > > > 04 0097fbd4 5a366e3f w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> > > > 05 0097fbdc 5a3af42d w3dt!UlAtqStartListen+0x2d
> > > > 06 0097fbec 5a3bc335 w3core!W3_SERVER::StartListen+0xbd
> > > > 07 0097fe40 01002c3c w3core!UlW3Start+0x26e
> > > > 08 0097fea4 01002ed7 inetinfo!LaunchWorkerProcess+0x159
> > > > 09 0097ffb8 77e64829 inetinfo!W3SVCThreadEntry+0x55
> > > > 0a 0097ffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 2
> > > > System Thread ID: f14
> > > > Kernel Time: 0:0:0.46
> > > > User Time: 0:0:0.125
> > > > Thread Status: Thread is in a WAIT state.
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 009bfcb8 7c827d0b ntdll!KiFastSystemCallRet
> > > > 01 009bfcbc 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > > 02 009bfd2c 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > > 03 009bfd40 649f2674 kernel32!WaitForSingleObject+0x12
> > > > 04 009bfd68 010024b3 iisadmin!ServiceEntry+0x28a
> > > > 05 009bffa4 77f65e91 inetinfo!InetinfoStartService+0x2cc
> > > > 06 009bffb8 77e64829 ADVAPI32!ScSvcctrlThreadW+0x21
> > > > 07 009bffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 3
> > > > System Thread ID: 1098
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 00bbff9c 7c826f4b ntdll!KiFastSystemCallRet
> > > > 01 00bbffa0 7c83d424 ntdll!NtDelayExecution+0xc
> > > > 02 00bbffb8 77e64829 ntdll!RtlpTimerThread+0x47
> > > > 03 00bbffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 4
> > > > System Thread ID: 1368
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Status: Thread is in a WAIT state.
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 00f9feac 7c827cfb ntdll!KiFastSystemCallRet
> > > > 01 00f9feb0 77e6202c ntdll!NtWaitForMultipleObjects+0xc
> > > > 02 00f9ff58 77e62fbe kernel32!WaitForMultipleObjectsEx+0x11a
> > > > 03 00f9ff74 56f951df kernel32!WaitForMultipleObjects+0x18
> > > > 04 00f9ffa0 56f969f6 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
> > > > 05 00f9ffb8 77e64829 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f
> > > > 06 00f9ffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 5
> > > > System Thread ID: 11c8
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.46
> > > > Thread Type: Possible ASP page. Possible DCOM activity
> > > > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > > > Continuing with other analysis.
> >
> > > > No remote call being made
> >
> > > > # ChildEBP RetAddr
> > > > 00 0192fe18 7c82783b ntdll!KiFastSystemCallRet
> > > > 01 0192fe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > > 02 0192ff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > > 03 0192ff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > > 04 0192ffac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > > 05 0192ffb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > > 06 0192ffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 6
> > > > System Thread ID: e00
> > > > Kernel Time: 0:0:0.31
> > > > User Time: 0:0:0.46
> > > > Thread Type: Possible ASP page. Possible DCOM activity
> > > > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > > > Continuing with other analysis.
> >
> > > > No remote call being made
> >
> > > > # ChildEBP RetAddr
> > > > 00 019afe18 7c82783b ntdll!KiFastSystemCallRet
> > > > 01 019afe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > > 02 019aff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > > 03 019aff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > > 04 019affac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > > 05 019affb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > > 06 019affec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 7
> > > > System Thread ID: 1384
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Status: Thread is in a WAIT state.
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 019efcec 7c827cfb ntdll!KiFastSystemCallRet
> > > > 01 019efcf0 7c83c78e ntdll!NtWaitForMultipleObjects+0xc
> > > > 02 019effb8 77e64829 ntdll!RtlpWaitThread+0x161
> > > > 03 019effec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 8
> > > > System Thread ID: 1380
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Type: Other
> > > > # ChildEBP RetAddr
> > > > 00 01a2a1b4 7c82a82b ntdll!RtlpCoalesceFreeBlocks+0x12a
> > > > 01 01a2a29c 10009fe5 ntdll!RtlFreeHeap+0x38e
> > > > WARNING: Stack unwind information not available. Following frames may be
> > > > wrong.
> > > > 02 01a2a2dc 10008740 Cosign!HttpFilterProc+0x2d95
> > > > 03 025741f4 02572500 Cosign!HttpFilterProc+0x14f0
> > > > 04 02574208 5aadba92 0x2572500
> > > > 05 071a0002 00000000 0x5aadba92
> >
> > > > Thread ID: 9
> > > > System Thread ID: 1378
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Type: HTTP Listener
> > > > # ChildEBP RetAddr
> > > > 00 01a6ff24 7c8277db ntdll!KiFastSystemCallRet
> > > > 01 01a6ff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > > 02 01a6ff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > > 03 01a6ff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > > 04 01a6ffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > > 05 01a6ffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > > 06 01a6ffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 10
> > > > System Thread ID: 102c
> > > > Kernel Time: 0:0:0.0
> > > > User Time: 0:0:0.0
> > > > Thread Type: HTTP Listener
> > > > # ChildEBP RetAddr
> > > > 00 01aaff24 7c8277db ntdll!KiFastSystemCallRet
> > > > 01 01aaff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > > 02 01aaff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > > 03 01aaff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > > 04 01aaffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > > 05 01aaffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > > 06 01aaffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > > > Thread ID: 11
> > > > System Thread ID: 1470
> > > > Kernel Time: 0:0:0.312
> > > > User Time: 0:0:0.796
> > > > Thread Type: HTTP Listener
> > > > # ChildEBP RetAddr
> > > > 00 01aeff24 7c8277db ntdll!KiFastSystemCallRet
> > > > 01 01aeff28 77e5bea2 ntdll!ZwRemoveIoCompletion+0xc
> > > > 02 01aeff54 5a30248e kernel32!GetQueuedCompletionStatus+0x29
> > > > 03 01aeff8c 5a3026ac W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x33
> > > > 04 01aeffa0 5a301da9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
> > > > 05 01aeffb8 77e64829 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
> > > > 06 01aeffec 00000000 kernel32!BaseThreadStart+0x34
> >
> > ...

Re: faulting application w3wp.exe

am 01.04.2008 15:49:07 von David Wang

If the other Universities and departments match the circumstances that
trigger the bug, then yes, they would also be down. But, we don't know
what circumstances cause your bug, so we cannot answer why they are
not all down.

However, lack of answer does not mean this is not a real bug in the
3rd party ISAPI Filter. I suggest using tools from Microsoft.com like
Application Verifier (Heap Verifier) to catch memory corruption like
this.

I would not obsess over why you're unlucky and others don't seem to
hit the issue, or why it happens after weeks and not immediately.
Finding the cause will naturally answer all the questions and fix the
problem.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Apr 1, 5:18=A0am, Beth wrote:
> There are other Universities and other departments at ours that are using
> this same filter version. If it's a bug, wouldn't we all be down? We'll
> investigate this more. Thanks for the assistance.
>
>
>
> "David Wang" wrote:
> > Actually, it is that the filter has had the bug for all this time; it
> > just started to show up now for some reason. Since you clearly cannot
> > control when it shows up, you have to fix the bug.
>
> > Another way to look at it. Suppose the filter has a line of code that
> > looks like this:
>
> > if today > 1/1/2009 then crash
>
> > The filter will work for months without crashing, until midnight
> > 1/1/2009, at which point it will always crash. Clearly, the bug has
> > been there for months, will not appear until 1/1/2009, and the code
> > logic is clearly undesirable.
>
> > The amount of time that the code "works" has no correlation to whether
> > the code is actually a bug or not. Some bugs take a long time to show
> > up; others appear quickly. The only thing you can do is fix the code
> > logic.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> > On Mar 20, 5:06 am, Beth wrote:
> > > So even though this filter has worked for weeks...it can just get a bu=
g now
> > > and stop working?
>
> > > We will work on the filter.
>
> > > "David Wang" wrote:
> > > > You have a third party product installed on the server which install=
ed
> > > > an ISAPI Filter named Cosign.dll. It has a bug that is crashing the
> > > > w3wp.exe. Please contact support for that product to resolve the
> > > > issue. Other than you stop using that third party product, no one el=
se
> > > > can help.
>
> > > > //David
> > > >http://w3-4u.blogspot.com
> > > >http://blogs.msdn.com/David.Wang
> > > > //
>
> > > > On Mar 19, 1:38 pm, Beth wrote:
> > > > > We are receiving this error: faulting application w3wp.exe , versi=
on
> > > > > 6.0.3790.3959, faulting module ntdll.dll, version 5.2.3790.3959, f=
ault
> > > > > address 0x0002b65d.
>
> > > > > We also got the same error with inetinfo.exe but now they are just=
w3wp.dll.
> > > > > I ran IISstate when we had the inetinfo errors but I can't get IIS=
state to
> > > > > work with w3wp.exe errors. =A0
>
> > > > > I'm not an experienced IIS user, so any help would be most appreci=
ated.. Half
> > > > > of our web-sites are down that use Cosign dll ISAPI filter.
>
> > > > > Prior IISState error:
> > > > > Opened log file 'C:\iisstate\output\IISState-3816.log'
>
> > > > > ***********************
> > > > > Starting new log output
> > > > > IISState version 3.3.1
>
> > > > > Mon Mar 17 16:43:02 2008
>
> > > > > OS =3D Windows 2003 Server
> > > > > Executable: inetinfo.exe
> > > > > PID =3D =A03816
>
> > > > > Note: Thread times are formatted as HH:MM:SS.ms
>
> > > > > ***********************
>
> > > > > IIS has crashed...
> > > > > Beginning Analysis
> > > > > DLL (!FunctionName) that failed: ntdll!RtlpCoalesceFreeBlocks
>
> > > > > Thread ID: 8
> > > > > System Thread ID: 1380
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.0
> > > > > *** ERROR: Symbol file could not be found. =A0Defaulted to export =
symbols for
> > > > > C:\Program Files\IISCosign\Cosign.dll -
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 01a2a1b4 7c82a82b ntdll!RtlpCoalesceFreeBlocks+0x12a
> > > > > 01 01a2a29c 10009fe5 ntdll!RtlFreeHeap+0x38e
> > > > > WARNING: Stack unwind information not available. Following frames =
may be
> > > > > wrong.
> > > > > 02 01a2a2dc 10008740 Cosign!HttpFilterProc+0x2d95
> > > > > 03 025741f4 02572500 Cosign!HttpFilterProc+0x14f0
> > > > > 04 02574208 5aadba92 0x2572500
> > > > > 05 071a0002 00000000 0x5aadba92
> > > > > Closing open log file C:\iisstate\output\IISState-3816.log
> > > > > Opened log file 'C:\iisstate\output\IISState-3816.log'
>
> > > > > ***********************
> > > > > Starting new log output
> > > > > IISState version 3.3.1
>
> > > > > Mon Mar 17 16:43:03 2008
>
> > > > > OS =3D Windows 2003 Server
> > > > > Executable: inetinfo.exe
> > > > > PID =3D =A03816
>
> > > > > Note: Thread times are formatted as HH:MM:SS.ms
>
> > > > > ***********************
>
> > > > > Thread ID: 0
> > > > > System Thread ID: e70
> > > > > Kernel Time: 0:0:0.15
> > > > > User Time: 0:0:0.0
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 0006f99c 7c82776b ntdll!KiFastSystemCallRet
> > > > > 01 0006f9a0 77e418b2 ntdll!NtReadFile+0xc
> > > > > 02 0006fa08 77f65edb kernel32!ReadFile+0x16c
> > > > > 03 0006fa34 77f65f82 ADVAPI32!ScGetPipeInput+0x2a
> > > > > 04 0006faa8 77fb75af ADVAPI32!ScDispatcherLoop+0x51
> > > > > 05 0006fcec 010027be ADVAPI32!StartServiceCtrlDispatcherA+0x93
> > > > > 06 0006fe1c 01002969 inetinfo!StartDispatchTable+0x277
> > > > > 07 0006ff44 0100339d inetinfo!main+0x117
> > > > > 08 0006ffc0 77e6f23b inetinfo!mainCRTStartup+0x12f
> > > > > 09 0006fff0 00000000 kernel32!BaseProcessStart+0x23
>
> > > > > Thread ID: 1
> > > > > System Thread ID: 1148
> > > > > Kernel Time: 0:0:0.187
> > > > > User Time: 0:0:0.0
> > > > > Thread Status: Thread is in a WAIT state.
> > > > > Thread Type: HTTP Compression Thread
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 0097fb3c 7c827d0b ntdll!KiFastSystemCallRet
> > > > > 01 0097fb40 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > > > 02 0097fbb0 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > > > 03 0097fbc4 5a364662 kernel32!WaitForSingleObject+0x12
> > > > > 04 0097fbd4 5a366e3f w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
> > > > > 05 0097fbdc 5a3af42d w3dt!UlAtqStartListen+0x2d
> > > > > 06 0097fbec 5a3bc335 w3core!W3_SERVER::StartListen+0xbd
> > > > > 07 0097fe40 01002c3c w3core!UlW3Start+0x26e
> > > > > 08 0097fea4 01002ed7 inetinfo!LaunchWorkerProcess+0x159
> > > > > 09 0097ffb8 77e64829 inetinfo!W3SVCThreadEntry+0x55
> > > > > 0a 0097ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 2
> > > > > System Thread ID: f14
> > > > > Kernel Time: 0:0:0.46
> > > > > User Time: 0:0:0.125
> > > > > Thread Status: Thread is in a WAIT state.
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 009bfcb8 7c827d0b ntdll!KiFastSystemCallRet
> > > > > 01 009bfcbc 77e61d1e ntdll!NtWaitForSingleObject+0xc
> > > > > 02 009bfd2c 77e61c8d kernel32!WaitForSingleObjectEx+0xac
> > > > > 03 009bfd40 649f2674 kernel32!WaitForSingleObject+0x12
> > > > > 04 009bfd68 010024b3 iisadmin!ServiceEntry+0x28a
> > > > > 05 009bffa4 77f65e91 inetinfo!InetinfoStartService+0x2cc
> > > > > 06 009bffb8 77e64829 ADVAPI32!ScSvcctrlThreadW+0x21
> > > > > 07 009bffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 3
> > > > > System Thread ID: 1098
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.0
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 00bbff9c 7c826f4b ntdll!KiFastSystemCallRet
> > > > > 01 00bbffa0 7c83d424 ntdll!NtDelayExecution+0xc
> > > > > 02 00bbffb8 77e64829 ntdll!RtlpTimerThread+0x47
> > > > > 03 00bbffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 4
> > > > > System Thread ID: 1368
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.0
> > > > > Thread Status: Thread is in a WAIT state.
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 00f9feac 7c827cfb ntdll!KiFastSystemCallRet
> > > > > 01 00f9feb0 77e6202c ntdll!NtWaitForMultipleObjects+0xc
> > > > > 02 00f9ff58 77e62fbe kernel32!WaitForMultipleObjectsEx+0x11a
> > > > > 03 00f9ff74 56f951df kernel32!WaitForMultipleObjects+0x18
> > > > > 04 00f9ffa0 56f969f6 COADMIN!NOTIFY_CONTEXT::GetNextContext+0x67
> > > > > 05 00f9ffb8 77e64829 COADMIN!NOTIFY_CONTEXT::NotifyThreadProc+0x5f=

> > > > > 06 00f9ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 5
> > > > > System Thread ID: 11c8
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.46
> > > > > Thread Type: Possible ASP page. =A0Possible DCOM activity
> > > > > Executing Page: ASP.dll symbols not found. Unable to locate ASP pa=
ge.
> > > > > Continuing with other analysis.
>
> > > > > No remote call being made
>
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 0192fe18 7c82783b ntdll!KiFastSystemCallRet
> > > > > 01 0192fe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > > > 02 0192ff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > > > 03 0192ff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > > > 04 0192ffac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > > > 05 0192ffb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > > > 06 0192ffec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 6
> > > > > System Thread ID: e00
> > > > > Kernel Time: 0:0:0.31
> > > > > User Time: 0:0:0.46
> > > > > Thread Type: Possible ASP page. =A0Possible DCOM activity
> > > > > Executing Page: ASP.dll symbols not found. Unable to locate ASP pa=
ge.
> > > > > Continuing with other analysis.
>
> > > > > No remote call being made
>
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 019afe18 7c82783b ntdll!KiFastSystemCallRet
> > > > > 01 019afe1c 77c885ac ntdll!NtReplyWaitReceivePortEx+0xc
> > > > > 02 019aff84 77c88792 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x198
> > > > > 03 019aff8c 77c8872d RPCRT4!RecvLotsaCallsWrapper+0xd
> > > > > 04 019affac 77c7b110 RPCRT4!BaseCachedThreadRoutine+0x9d
> > > > > 05 019affb8 77e64829 RPCRT4!ThreadStartRoutine+0x1b
> > > > > 06 019affec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 7
> > > > > System Thread ID: 1384
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.0
> > > > > Thread Status: Thread is in a WAIT state.
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 019efcec 7c827cfb ntdll!KiFastSystemCallRet
> > > > > 01 019efcf0 7c83c78e ntdll!NtWaitForMultipleObjects+0xc
> > > > > 02 019effb8 77e64829 ntdll!RtlpWaitThread+0x161
> > > > > 03 019effec 00000000 kernel32!BaseThreadStart+0x34
>
> > > > > Thread ID: 8
> > > > > System Thread ID: 1380
> > > > > Kernel Time: 0:0:0.0
> > > > > User Time: 0:0:0.0
> > > > > Thread Type: Other
> > > > > =A0# ChildEBP RetAddr =A0
> > > > > 00 01a2a1b4 7c82a82b ntdll!RtlpCoalesceFreeBlocks+0x12a
> > > > > 01 01a2a29c 10009fe5 ntdll!RtlFreeHeap+0x38e
> > > > > WARNING: Stack unwind information not available. Following frames =
may be
> > > > > wrong.
> > > > > 02
>
> ...
>
> read more =BB- Hide quoted text -
>
> - Show quoted text -