RB
2006-03-09 17:11:33 UTC
Hello, we are having issues with web applications hanging frequently. We
eventually setup pools and split up the applications assuming they were
conflicting with each other. We are still experiencing hangs. Below are
excerpts from the dump of one of the hangs. Can someone please help in
analyzing what the cause may be. We are running IIS 6.0 on a Windows 2003
server.
Error In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__506__First
chance exception 0XC0000005.dmp the assembly instruction at 2d944ba which
does not correspond to any known native module in the process has caused an
access violation exception (0xC0000005) when trying to read from memory
location 0x00000000 on thread 16
If no further information can be obtained from the detailed stack analysis
below, please contact Microsoft Corporation for troubleshooting steps on
stack corruption
Error In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__959__First
chance exception 0XC0000005.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an access violation exception (0xC0000005) when trying
to read from memory location 0x00000000 on thread 16
Please follow up with the vendor Microsoft Corporation for
C:\WINDOWS\system32\kernel32.dll
Error In w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__640__First
chance exception 0XE0434F4D.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an unknown exception (0xe0434f4d) on thread 19
An exception thrown by Kernel32!RaiseException usually indicates a problem
with another module. Please review the stack for the faulting thread (19)
further to determine which module actually threw the exception raised by
Kernel32.dll.
Detailed stack corruption analysis for thread 16
Call stack with StackWalk
Index Return Address
1 2d944ba
2 2d943ef
3 143f9f88
Call stack - Heuristic
Index Stack Address Child EBP Return Address Destination
1 0x00000000 0x0199f864 2d944ba 0
2 0x0199f868 0x143f9fdc 2d943ef 2d94480
3 0x0199f878 0x1c3b0614 2d93ac4 2d943e0
4 0x0199f888 0x1c3b0614 2d93a04 2d93a60
5 0x0199f8a8 0x40590000 2d907d0 2d93928
6 0x0199f8b8 0x143f9f88 2d90666 2d906a0
7 0x0199f8d0 0x143f9f7c 2d9054c 2d905a8
8 0x0199f8e0 0x143f9c30 2d9040b 2d904f0
9 0x0199f8f4 0x1c3b0614 2d903a0 2d903b8
10 0x0199f900 0x182d300c 2d902af 2d90328
11 0x0199f90c 0x182d300c 2db9e26 0
12 0x0199f948 0x0199f9a0 2db98ab 2db9dd0
13 0x0199f950 0x14390804 2db9884 0
14 0x0199f960 0x14390aec 2d8a4c8 0
15 0x0199f9a4 0x0199f9ec 2d89f32 2d8a470
16 0x0199f9f0 0x0199fa44 2d89e03 2d89e38
17 0x0199fa04 0x18363f78 1ec68a7 0
18 0x0199fa48 0x0199fad4 1ec6458 1ec66c0
19 0x0199fa54 0x1c2d3a28 1ec2fd5 1ec63a8
20 0x0199fa64 0x01a881f3 mscorsvr!ComCallMLStubCache::CompileMLStub+429 0
21 0x0199fbc8 0x0199fca8 1a5a0bd
mscorsvr!ComCallMLStubCache::CompileMLStub+255
22 0x0199fc08 0xffffffff 19c3a04 1a5a06c
23 0x0199fc0c 0x019c3a04
aspnet_isapi!HttpCompletion::ProcessRequestInManagedCode+17e 0
24 0x0199fcbc 0x7c81b26f ntdll!ZwTestAlert+c 0
25 0x0199fd18 0x7c81b23f ntdll!ZwContinue+c 0
26 0x0199fd1c 0x7c8211b4 ntdll!KiUserApcDispatcher+3a ntdll!NtContinue
27 0x0199fdfc 0x00000000 ntdll!NtWaitForSingleObject+c 0
28 0x0199fe00 0x7c822124 kernel32!WaitForSingleObjectEx+ac
ntdll!ZwWaitForSingleObject
29 0x0199fe0c 0x00000000 kernel32!WaitForSingleObjectEx+dc
kernel32!_SEH_epilog
30 0x0199fe3c 0x00000000 aspnet_isapi!PerfDecrementCounter+1c
kernel32!InterlockedDecrement
31 0x0199fe44 0x01862810 aspnet_isapi!PerfDecrementGlobalCounter+f
aspnet_isapi!PerfDecrementCounter
32 0x0199fe60 0x79e8e231 aspnet_isapi!CorThreadPoolWorkitemCallback+13 0
33 0x0199fe74 0x00000000 mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+19 0
34 0x0199fe88 0x0199fea4 mscorsvr!ThreadpoolMgr::WorkerThreadStart+129
mscorsvr!ThreadpoolMgr::ExecuteWorkRequest
35 0x0199fea8 0x0199ffb8 mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 0
36 0x0199ffbc 0x0199ffec kernel32!BaseThreadStart+34 0
^ Memory access error in 'u 0x0000000c l1'
In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__506__First chance
exception 0XC0000005.dmp the assembly instruction at 2d944ba which does not
correspond to any known native module in the process has caused an access
violation exception (0xC0000005) when trying to read from memory location
0x00000000 on thread 16
Report for w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__233__First
chance exception 0XE0434F4D.dmp
Type of Analysis Performed Crash Analysis
Machine Name GPISV205
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 4
Process ID 4788
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 2 day(s) 20:38:19
Process Up-Time 0 day(s) 01:19:04
Thread 19 - System ID 8644
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 3/9/2006 9:42:21 AM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.46
Function Source
kernel32!RaiseException+53
mscorsvr!RaiseTheException+a0
mscorsvr!RealCOMPlusThrow+48
mscorsvr!RealCOMPlusThrow+d
mscorsvr!CEEInfo::findMethod+123
mscorjit!Compiler::eeFindMethod+23
mscorjit!Compiler::impImportBlockCode+1e80
mscorjit!Compiler::impImportBlock+222
mscorjit!Compiler::impImport+e8
mscorjit!Compiler::fgImport+41
mscorjit!Compiler::compCompile+b
mscorjit!Compiler::compCompile+1e8
mscorjit!jitNativeCode+95
mscorjit!CILJit::compileMethod+a2
mscorsvr!CallCompileMethodWithSEHWrapper+52
mscorsvr!JITFunction+2c7
mscorsvr!MakeJitWorker+2c0
mscorsvr!MethodDesc::DoPrestub+4d3
mscorsvr!PreStubWorker+42
19c2f76
mscorsvr!MethodDesc::CallDescr+155
mscorsvr!MethodDesc::Call+8e
mscorsvr!COMMember::CreateInstance+2fe
1fd12e9
2bf3dc5
2bf3c74
2bbdb53
2bbda60
2bb990a
2bb97db
1ec6458
mscorsvr!ComCallMLStubCache::CompileMLStub+1af
mscorsvr!Thread::DoADCallBack+5c
mscorsvr!ComCallMLStubCache::CompileMLStub+2ba
1a5a0bd
f3c28
In w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__233__First chance
exception 0XE0434F4D.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an unknown exception (0xe0434f4d) on thread 19
Thanks,
RB
eventually setup pools and split up the applications assuming they were
conflicting with each other. We are still experiencing hangs. Below are
excerpts from the dump of one of the hangs. Can someone please help in
analyzing what the cause may be. We are running IIS 6.0 on a Windows 2003
server.
Error In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__506__First
chance exception 0XC0000005.dmp the assembly instruction at 2d944ba which
does not correspond to any known native module in the process has caused an
access violation exception (0xC0000005) when trying to read from memory
location 0x00000000 on thread 16
If no further information can be obtained from the detailed stack analysis
below, please contact Microsoft Corporation for troubleshooting steps on
stack corruption
Error In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__959__First
chance exception 0XC0000005.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an access violation exception (0xC0000005) when trying
to read from memory location 0x00000000 on thread 16
Please follow up with the vendor Microsoft Corporation for
C:\WINDOWS\system32\kernel32.dll
Error In w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__640__First
chance exception 0XE0434F4D.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an unknown exception (0xe0434f4d) on thread 19
An exception thrown by Kernel32!RaiseException usually indicates a problem
with another module. Please review the stack for the faulting thread (19)
further to determine which module actually threw the exception raised by
Kernel32.dll.
Detailed stack corruption analysis for thread 16
Call stack with StackWalk
Index Return Address
1 2d944ba
2 2d943ef
3 143f9f88
Call stack - Heuristic
Index Stack Address Child EBP Return Address Destination
1 0x00000000 0x0199f864 2d944ba 0
2 0x0199f868 0x143f9fdc 2d943ef 2d94480
3 0x0199f878 0x1c3b0614 2d93ac4 2d943e0
4 0x0199f888 0x1c3b0614 2d93a04 2d93a60
5 0x0199f8a8 0x40590000 2d907d0 2d93928
6 0x0199f8b8 0x143f9f88 2d90666 2d906a0
7 0x0199f8d0 0x143f9f7c 2d9054c 2d905a8
8 0x0199f8e0 0x143f9c30 2d9040b 2d904f0
9 0x0199f8f4 0x1c3b0614 2d903a0 2d903b8
10 0x0199f900 0x182d300c 2d902af 2d90328
11 0x0199f90c 0x182d300c 2db9e26 0
12 0x0199f948 0x0199f9a0 2db98ab 2db9dd0
13 0x0199f950 0x14390804 2db9884 0
14 0x0199f960 0x14390aec 2d8a4c8 0
15 0x0199f9a4 0x0199f9ec 2d89f32 2d8a470
16 0x0199f9f0 0x0199fa44 2d89e03 2d89e38
17 0x0199fa04 0x18363f78 1ec68a7 0
18 0x0199fa48 0x0199fad4 1ec6458 1ec66c0
19 0x0199fa54 0x1c2d3a28 1ec2fd5 1ec63a8
20 0x0199fa64 0x01a881f3 mscorsvr!ComCallMLStubCache::CompileMLStub+429 0
21 0x0199fbc8 0x0199fca8 1a5a0bd
mscorsvr!ComCallMLStubCache::CompileMLStub+255
22 0x0199fc08 0xffffffff 19c3a04 1a5a06c
23 0x0199fc0c 0x019c3a04
aspnet_isapi!HttpCompletion::ProcessRequestInManagedCode+17e 0
24 0x0199fcbc 0x7c81b26f ntdll!ZwTestAlert+c 0
25 0x0199fd18 0x7c81b23f ntdll!ZwContinue+c 0
26 0x0199fd1c 0x7c8211b4 ntdll!KiUserApcDispatcher+3a ntdll!NtContinue
27 0x0199fdfc 0x00000000 ntdll!NtWaitForSingleObject+c 0
28 0x0199fe00 0x7c822124 kernel32!WaitForSingleObjectEx+ac
ntdll!ZwWaitForSingleObject
29 0x0199fe0c 0x00000000 kernel32!WaitForSingleObjectEx+dc
kernel32!_SEH_epilog
30 0x0199fe3c 0x00000000 aspnet_isapi!PerfDecrementCounter+1c
kernel32!InterlockedDecrement
31 0x0199fe44 0x01862810 aspnet_isapi!PerfDecrementGlobalCounter+f
aspnet_isapi!PerfDecrementCounter
32 0x0199fe60 0x79e8e231 aspnet_isapi!CorThreadPoolWorkitemCallback+13 0
33 0x0199fe74 0x00000000 mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+19 0
34 0x0199fe88 0x0199fea4 mscorsvr!ThreadpoolMgr::WorkerThreadStart+129
mscorsvr!ThreadpoolMgr::ExecuteWorkRequest
35 0x0199fea8 0x0199ffb8 mscorsvr!ThreadpoolMgr::intermediateThreadProc+44 0
36 0x0199ffbc 0x0199ffec kernel32!BaseThreadStart+34 0
^ Memory access error in 'u 0x0000000c l1'
In w3wp__PID__8496__Date__03_09_2006__Time_11_33_02AM__506__First chance
exception 0XC0000005.dmp the assembly instruction at 2d944ba which does not
correspond to any known native module in the process has caused an access
violation exception (0xC0000005) when trying to read from memory location
0x00000000 on thread 16
Report for w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__233__First
chance exception 0XE0434F4D.dmp
Type of Analysis Performed Crash Analysis
Machine Name GPISV205
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 4
Process ID 4788
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 2 day(s) 20:38:19
Process Up-Time 0 day(s) 01:19:04
Thread 19 - System ID 8644
Entry point mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time 3/9/2006 9:42:21 AM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.46
Function Source
kernel32!RaiseException+53
mscorsvr!RaiseTheException+a0
mscorsvr!RealCOMPlusThrow+48
mscorsvr!RealCOMPlusThrow+d
mscorsvr!CEEInfo::findMethod+123
mscorjit!Compiler::eeFindMethod+23
mscorjit!Compiler::impImportBlockCode+1e80
mscorjit!Compiler::impImportBlock+222
mscorjit!Compiler::impImport+e8
mscorjit!Compiler::fgImport+41
mscorjit!Compiler::compCompile+b
mscorjit!Compiler::compCompile+1e8
mscorjit!jitNativeCode+95
mscorjit!CILJit::compileMethod+a2
mscorsvr!CallCompileMethodWithSEHWrapper+52
mscorsvr!JITFunction+2c7
mscorsvr!MakeJitWorker+2c0
mscorsvr!MethodDesc::DoPrestub+4d3
mscorsvr!PreStubWorker+42
19c2f76
mscorsvr!MethodDesc::CallDescr+155
mscorsvr!MethodDesc::Call+8e
mscorsvr!COMMember::CreateInstance+2fe
1fd12e9
2bf3dc5
2bf3c74
2bbdb53
2bbda60
2bb990a
2bb97db
1ec6458
mscorsvr!ComCallMLStubCache::CompileMLStub+1af
mscorsvr!Thread::DoADCallBack+5c
mscorsvr!ComCallMLStubCache::CompileMLStub+2ba
1a5a0bd
f3c28
In w3wp__PID__4788__Date__03_09_2006__Time_11_01_24AM__233__First chance
exception 0XE0434F4D.dmp the assembly instruction at
kernel32!RaiseException+53 in C:\WINDOWS\system32\kernel32.dll from Microsoft
Corporation has caused an unknown exception (0xe0434f4d) on thread 19
Thanks,
RB