我有一个IIS Web应用程序，在遇到一系列0xc000008异常后，每天都在崩溃。错误在发生5次后停止在事件查看器中记录，但是我确信在5次发生后它会停止，因为IIS App Pool的快速失败保护配置为在5次异常后启动。我进一步确信快速失败保护正在起作用，因为我不得不每天手动回收/重启App Pool。
我安装了DebugDiag来帮助跟踪事件查看器中看到的异常，但它与事件查看器中的错误一样模糊。在这一点上，我已经达到了我对IIS和ASP.NET非常有限的知识的边缘，不幸的是，我们无法尝试太多，因为我无法得到明智的错误信息。我已经在下面列出了每个来源的错误消息。任何帮助理解它们或知道从哪里开始都会非常感激。
这是一个使用在Windows Server 2012 R2上运行的.NET Framework 4.5.2在C＃中编写的MVC3 Web应用程序。已安装所有适用的Windows更新。
我启用了失败的请求跟踪功能，希望能够更深入地了解错误。
事件查看器错误
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: ntdll.dll, version: 6.3.9600.16502, time stamp: 0x52c359e8
Exception code: 0xc0000374
Fault offset: 0x00000000000f387c
Faulting process id: 0x1588
Faulting application start time: 0x01d239d9a9246e12
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 6dd5b05a-a5ce-11e6-80c5-005056bf6041
Faulting package full name:
Faulting package-relative application ID:
DebugDiag的错误分析
Report for w3wp__dataximg__PID__2168__Date__11_01_2016__Time_01_03_36PM__593__Second_Chance_Exception_C0000008.dmp
Type of Analysis Performed Combined Crash/Hang Analysis
Machine Name localhost
Operating System Windows Server 2012
Number Of Processors 2
Process ID 2168
Process Image c:\Windows\System32\inetsrv\w3wp.exe
Command Line c:\windows\system32\inetsrv\w3wp.exe -ap "dataximg" -v "v2.0" -l "webengine4.dll" -a \\.\pipe\iisipm21b77437-5c32-41dc-958b-556a03f34971 -h "C:\inetpub\temp\apppools\dataximg\dataximg.config" -w "" -m 0 -t 20 -ta 0
System Up-Time 35 day(s) 23:08:46
Process Up-Time 00:00:07
Processor Type X64
Process Bitness 64-Bit
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread
Thread ID: 0 Total CPU Time: 00:00:00.030 Entry Point for Thread: w3wp!wmainCRTStartup
Thread ID: 2 Total CPU Time: 00:00:00.015 Entry Point for Thread: ntdll!TppWorkerThread
Thread ID: 1 Total CPU Time: 00:00:00.000 Entry Point for Thread: nativerd!NOTIFICATION_THREAD::ThreadProc
Thread ID: 3 Total CPU Time: 00:00:00.000 Entry Point for Thread: ntdll!TppWorkerThread
Thread ID: 4 Total CPU Time: 00:00:00.000 Entry Point for Thread: w3tp!THREAD_MANAGER::ThreadManagerThread
Exception Information
In w3wp__appimg__PID__2168__Date__11_01_2016__Time_01_03_36PM__593__Second_Chance_Exception_C0000008.dmp the assembly instruction at ntdll!KiRaiseUserExceptionDispatcher+3a in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused an unknown exception (0xc0000008) on thread 1
Module Information
Image Name: C:\Windows\System32\ntdll.dll Symbol Type: PDB
Base address: 0x00000003`00905a4d Time Stamp: Tue Dec 31 18:57:28 2013
Checksum: 0x00000000`00000000 Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: NT Layer DLL
ISAPIFilter: False File Version: 6.3.9600.16502 (winblue_gdr.131231-1531)
Managed DLL: False Internal Name: ntdll.dll
VB DLL: False Legal Copyright:© Microsoft Corporation. All rights reserved.
Loaded Image Name: ntdll.dll Legal Trademarks:
Mapped Image Name: Original filename: ntdll.dll
Module name: ntdll Private Build:
Single Threaded: False Product Name: Microsoft® Windows® Operating System
Module Size: 1.66 MBytes Product Version: 6.3.9600.16502
Symbol File Name: c:\symbols\ntdll.pdb\A525CD5C71214238B761A6EFA0B3402D1\ntdll.pdb Special Build: &