IIS Crashing

I am having trouble with IIS crashing. The debug report is below.

This is the event log.

A process serving application pool 'LabDepot' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '4024'. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any help would be appriciated, this is a fully patched windows 2003 server.


Analysis Summary
Type Description Recommendation
Error In w3wp__PID__2276__Date__08_21_2006__Time_01_24_59PM __984__Second_Chance_Exception_C0000005.dmp the assembly instruction at ntdll!_SEH_prolog+1a in C:\WINDOWS\system32\ntdll.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x021a0f64 on thread 13
Please follow up with the vendor Microsoft Corporation for C:\WINDOWS\system32\ntdll.dll

Information DebugDiag determined that this dump file (w3wp__PID__2276__Date__08_21_2006__Time_01_24_59P M__984__Second_Chance_Exception_C0000005.dmp) is a crash dump and did not perform any hang analysis. If you wish to enable combined crash and hang analysis for crash dumps, edit the IISAnalysis.asp script (located in the DebugDiag\Scripts folder) and set the g_DoCombinedAnalysis constant to True.





Analysis Details
Table Of Contents
w3wp__PID__2276__Date__08_21_2006__Time_01_24_59PM __984__Second_Chance_Exception_C0000005.dmp

Faulting Thread

Faulting Module Information




Report for w3wp__PID__2276__Date__08_21_2006__Time_01_24_59PM __984__Second_Chance_Exception_C0000005.dmp
Type of Analysis Performed Crash Analysis
Machine Name LABDEPOT
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 1
Process ID 2276
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 5 day(s) 22:12:34
Process Up-Time 0 day(s) 02:40:00


Thread 13 - System ID 4436
Entry point mscorwks!ThreadpoolMgr::intermediateThreadProc
Create time 8/21/2006 10:45:01 AM
Time spent in user mode 0 Days 0:1:19.937
Time spent in kernel mode 0 Days 0:0:14.593






Function Arg 1 Arg 2 Arg 3 Source
ntdll!_SEH_prolog+1a 00000001 021a12a4 021a1280
ntdll!RtlDosPathNameToRelativeNtPathName_Ustr+18 021a12a4 021a1280 00000000
ntdll!RtlDoesFileExists_UstrEx+1c 021a12a4 00000001 021a140c
ntdll!LdrpSearchPath+76 021a1320 021a142c 021a1334
ntdll!LdrpCheckForLoadedDll+dc 0546e248 021a140c 00000000
ntdll!LdrpLoadDll+1b3 00000000 0546e248 021a1928
ntdll!LdrLoadDll+198 0546e248 021a1928 021a1908
kernel32!LoadLibraryExW+1b2 021a2974 00000000 00000002
version!GetFileVersionInfoSizeW+31 021a2974 021a19b4 00000004
faultrep!IsMicrosoftApp+5e 021a2974 00000000 00000000
faultrep!CPFFaultClientCfg::ShouldCollect+12a 021a2974 021a1da4 00000000
faultrep!ReportFault+250 021a2c2c 00000000 021a2c2c
comsvcs!CosReportFault+71 021a2c2c 00000000 02664708
comsvcs!UserCodeExceptionFilter+36 021a2c2c 75bb2ae0 02664708
comsvcs!ComSvcsExceptionFilter+30 021a2c2c 75bb2ae0 02664708
comsvcs!CHolder::SafeDispenserDriver::CreateResour ce+3e 021a2c34 00000000 021a2c34
msvcrt!_except_handler3+61 021a2d18 021a54bc 021a2d34
ntdll!ExecuteHandler2+26 021a2d18 021a54bc 021a2d34
ntdll!ExecuteHandler+24 021a1000 021a2d34 021a2d18
ntdll!KiUserExceptionDispatcher+e 021a1000 021a2d34 021a2d18
ntdll!RtlAllocateHeapSlowly+f9 01420000 00010000 00000048
ntdll!RtlAllocateHeap+e9f 01420000 00010000 00000048
dnsapi!Dns_HeapAllocEx+1f 76ef3c80 00000000 00000048
dnsapi!Dns_HeapAlloc+15 00000048 021a3a00 021a3608
rpcrt4!NdrSafeAllocate+7c 021a3608 00000038 021a3a00
rpcrt4!NdrComplexStructUnmarshall+134 001a3608 021a3a00 76ed3064
rpcrt4!NdrpPointerUnmarshall+216 00000000 76ed305c 021a3a00
rpcrt4!NdrPointerUnmarshall+30 021a3608 021a3a00 76ed2f28
rpcrt4!NdrpPointerUnmarshall+216 00000000 76ed2f28 021a3a00
rpcrt4!NdrPointerUnmarshall+30 021a3608 021a39d8 76ed2f24
rpcrt4!NdrpClientUnMarshal+122 021a3608 021a3708 00000000
rpcrt4!NdrClientCall2+2dd 76ed2e60 76ed2d2c 021a39c8
dnsapi!R_ResolverQuery+1c 00000000 01421f5c 00000001
dnsapi!Query_PrivateExW+187 01421f5c 00000001 14000040
dnsapi!dnsrslvr_bhandle <PERF> (dnsapi+0x2612a) 01421f5c 00000001 14000040
mswsock!SaBlob_Query+2d 01421f5c 00000001 14000040
mswsock!Rnr_DoDnsLookup+f0 00000000 054f1bf0 054f1bd8
mswsock!Dns_NSPLookupServiceNext+24b 01421ef8 00000000 021a3e00
ws2_32!NSPROVIDER::NSPLookupServiceNext+17 000bf340 01421ef8 00000000
ws2_32!NSPROVIDERSTATE::LookupServiceNext+1c 05440b60 00000000 021a3e00
ws2_32!NSQUERY::LookupServiceNext+ae 054f1bf0 00000000 021a3e00
ws2_32!WSALookupServiceNextW+78 054f1bd8 00000000 021a3e00
ws2_32!WSALookupServiceNextA+63 054f1bd8 00000000 0000013c
ws2_32!getxyDataEnt+a1 021a3e4c 0000013c 05197240
ws2_32!gethostbyname+b4 05197240 05197240 04fcdb06
myodbc3!SQLTransact+c5a0 00000000 00000000 00000000




NTDLL!_SEH_PROLOG+1AIn w3wp__PID__2276__Date__08_21_2006__Time_01_24_59PM __984__Second_Chance_Exception_C0000005.dmp the assembly instruction at ntdll!_SEH_prolog+1a in C:\WINDOWS\system32\ntdll.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x021a0f64 on thread 13

Module Information
Image Name: C:\WINDOWS\system32\ntdll.dll Symbol Type: PDB
Base address: 0x7c800000 Time Stamp: Thu Mar 24 21:30:42 2005
Checksum: 0x000c90bf Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: NT Layer DLL
ISAPIFilter: False File Version: 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)
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: 768.00 KBytes Product Version: 5.2.3790.1830
Symbol File Name: c:\symcache\ntdll.pdb\DCE823FCF71A4BF5AA489994520E A18F2\ntdll.pdb Special Build: &

app pool errors can be a number of thinks.

have a look in the log to find out what was happening b4 it crashed.

r u running ur webserver as a DC as it could be a permissions problem

also sometimes IIS has issues when running websites outside the directory of wwwroot

have a look at the folowing link for tools to check the pool

http://support.microsoft.com/?id=919789