我们的应用程序池突然崩溃，我已禁用快速失败 - 失败保护，因此我们的网站没有关闭，但这不是找到错误的方法。
事件日志是fileld，其错误如下： 为应用程序池（名称）提供服务的进程与Windows进程激活服务发生致命的通信错误。流程ID为＆＃39; 8480＆＃39;数据字段包含错误编号。
我已经对它何时崩溃进行了DebugDialog分析，但是这没有告诉我什么？
Thread 1 - System ID 9060
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtRemoveIoCompletion+c
KERNELBASE!GetQueuedCompletionStatus+2a
nativerd!NOTIFICATION_THREAD::ThreadProc+4f
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 2 - System ID 3372
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.093
Time spent in kernel mode 0 Days 00:00:00.031
.NET Call Stack
Function
Full Call Stack
Function Source
ntdll!NtWaitForWorkViaWorkerFactory+c
ntdll!TppWorkerThread+259
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 3 - System ID 8928
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.015
.NET Call Stack
Function
Full Call Stack
Function Source
ntdll!NtWaitForWorkViaWorkerFactory+c
ntdll!TppWorkerThread+259
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 4 - System ID 8396
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.531
Time spent in kernel mode 0 Days 00:00:00.078
Function Source
ntdll!NtRemoveIoCompletion+c
KERNELBASE!GetQueuedCompletionStatus+2a
w3tp!THREAD_POOL_DATA::ThreadPoolThread+36
w3tp!THREAD_POOL_DATA::ThreadPoolThread+2b
w3tp!THREAD_MANAGER::ThreadManagerThread+4d
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 5 - System ID 2884
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.156
Time spent in kernel mode 0 Days 00:00:00.015
Function Source
ntdll!NtRemoveIoCompletion+c
KERNELBASE!GetQueuedCompletionStatus+2a
w3tp!THREAD_POOL_DATA::ThreadPoolThread+36
w3tp!THREAD_POOL_DATA::ThreadPoolThread+2b
w3tp!THREAD_MANAGER::ThreadManagerThread+18
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 6 - System ID 8136
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.312
Time spent in kernel mode 0 Days 00:00:00.015
Function Source
ntdll!NtRemoveIoCompletion+c
KERNELBASE!GetQueuedCompletionStatus+2a
w3tp!THREAD_POOL_DATA::ThreadPoolThread+36
w3tp!THREAD_POOL_DATA::ThreadPoolThread+2b
w3tp!THREAD_MANAGER::ThreadManagerThread+18
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 7 - System ID 1516
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.734
Time spent in kernel mode 0 Days 00:00:02.281
.NET Call Stack
Function
Full Call Stack
Function Source
ntdll!NtRemoveIoCompletion+c
KERNELBASE!GetQueuedCompletionStatus+2a
w3tp!THREAD_POOL_DATA::ThreadPoolThread+36
w3tp!THREAD_POOL_DATA::ThreadPoolThread+2b
w3tp!THREAD_MANAGER::ThreadManagerThread+4d
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 8 - System ID 5912
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtWaitForWorkViaWorkerFactory+c
ntdll!TppWorkerThread+259
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 9 - System ID 1512
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtWaitForMultipleObjects+c
KERNELBASE!WaitForMultipleObjectsEx+cc
kernel32!WaitForMultipleObjects+19
iisfreb!LOSSY_QUEUE::WaitForDequeue+51
iisfreb!FREB_LOG_FILE_MANAGER::WriterThread+b9
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 10 - System ID 7856
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtWaitForMultipleObjects+c
KERNELBASE!WaitForMultipleObjectsEx+cc
clr!DebuggerRCThread::MainLoop+98
clr!DebuggerRCThread::ThreadProc+cb
clr!DebuggerRCThread::ThreadProcStatic+b9
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 11 - System ID 8432
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:01.437
Time spent in kernel mode 0 Days 00:00:00.062
Function Source
ntdll!NtWaitForSingleObject+c
KERNELBASE!WaitForSingleObjectEx+99
clr!CLREventBase::Reset+145
clr!CLREventBase::Reset+18d
clr!CLREventBase::WaitEx+152
clr!CLREventBase::Wait+1a
clr!SVR::gc_heap::gc_thread_function+5d
clr!SVR::gc_heap::gc_thread_stub+71
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 12 - System ID 7740
Entry point 0x00000000
Create time 01-11-2016 13:32:06
Time spent in user mode 0 Days 00:00:01.125
Time spent in kernel mode 0 Days 00:00:00.062
Function Source
ntdll!NtWaitForSingleObject+c
KERNELBASE!WaitForSingleObjectEx+99
clr!CLREventBase::Reset+145
clr!CLREventBase::Reset+18d
clr!CLREventBase::WaitEx+152
clr!CLREventBase::Wait+1a
clr!SVR::gc_heap::gc_thread_function+129
clr!SVR::gc_heap::gc_thread_stub+71
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
很多线程看起来像这样，但在线程37中更多：
Thread 37 - System ID 4880
Entry point 0x00000000
Create time 01-11-2016 13:44:54
Time spent in user mode 0 Days 00:00:02.984
Time spent in kernel mode 0 Days 00:00:00.062
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
.NET Call Stack
Function
System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, System.Web.RequestNotificationStatus ByRef)
Full Call Stack
Function Source
ntdll!NtTerminateProcess
KERNELBASE!TerminateProcess+23
clr!EEPolicy::HandleFatalStackOverflow+1b5
clr!EEPolicy::HandleStackOverflow+1b0
clr!COMPlusFrameHandler+9b
ntdll!ExecuteHandler2+26
ntdll!ExecuteHandler+24
ntdll!KiUserExceptionDispatcher+f
clr!_EH_prolog3_catch+1e
clr!ArrayNative::ArrayCopy+c
mscorlib_ni+3af760
clr!CallDescrWorkerInternal+34
clr!CallDescrWorkerWithHandler+6b
clr!CallDescrWorkerReflectionWrapper+55
clr!RuntimeMethodHandle::InvokeMethod+7eb
mscorlib_ni+3a22ed
mscorlib_ni+3a1e76
System_Data_SqlXml_ni+1223c7
System_Data_SqlXml_ni+121df8
0x21c51279
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c51cb2
0x21c6945d
0x21c67322
System_Data_SqlXml_ni+11f0fc
System_Data_SqlXml_ni+11f00d
System_Xml_ni+4ee44a
System_Xml_ni+4edcd3
0x1a60d177
0x1a60ce3b
0x1a60c584
0x1a60ac71
0x1a609b81
0x1a608780
System_Web_ni+1ebc0d
System_Web_ni+1ea54c
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1ea5f9
System_Web_ni+1f3785
System_Web_ni+1f2ff3
System_Web_ni+1f2f29
System_Web_ni+1f2ed7
System_Web_ni+1f2ebb
System_Web_ni+1f5ead
System_Web_ni+1cfce2
System_Web_ni+1de623
System_Web_ni+1d0630
System_Web_ni+1dd182
System_Web_ni+1d1490
System_Web_ni+1d117f
webengine4!W3_MGD_HANDLER::ProcessNotification+5a
webengine4!W3_MGD_HANDLER::DoWork+2cc
webengine4!RequestDoWork+2ea
webengine4!CMgdEngHttpModule::OnExecuteRequestHandler+18
iiscore!NOTIFICATION_CONTEXT::RequestDoWork+17b
iiscore!NOTIFICATION_CONTEXT::CallModulesInternal+3d7
iiscore!NOTIFICATION_CONTEXT::CallModules+2b
iiscore!NOTIFICATION_MAIN::DoStateRequestExecuteHandler+40
iiscore!NOTIFICATION_MAIN::DoWork+11a
iiscore!W3_CONTEXT_BASE::ContinueNotificationLoop+1d
iiscore!W3_CONTEXT_BASE::IndicateCompletion+8c
webengine4!W3_MGD_HANDLER::IndicateCompletion+38
webengine4!MgdIndicateCompletion+22
System_Web_ni+22510d
System_Web_ni+1d1633
System_Web_ni+1d117f
clr!UM2MThunk_WrapperHelper+10
clr!UM2MThunk_Wrapper+76
clr!Thread::DoADCallBack+b3
clr!UM2MDoADCallBack+92
0x022fd9af
webengine4!W3_MGD_HANDLER::ProcessNotification+5a
webengine4!ProcessNotificationCallback+32
clr!UnManagedPerAppDomainTPCount::DispatchWorkItem+1ce
clr!ThreadpoolMgr::ExecuteWorkRequest+42
clr!ThreadpoolMgr::WorkerThreadStart+390
clr!Thread::intermediateThreadProc+4d
kernel32!BaseThreadInitThunk+24
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
答案 0 :(得分：0)
我发现了如何获得更详细的堆栈跟踪。 我下载了Windows软件开发工具包中的Windbg：https://developer.microsoft.com/da-dk/windows/hardware/windows-driver-kit
在Windbg中打开崩溃转储文件并运行以下命令：
.loadby sos.dll clr
!clrstack
这将为您提供更详细的问题堆栈跟踪。 在这种情况下，它是一个反复调用的函数。