Help analysing a .NET 2.0 Webservice application

Hi,

We're runing a .NET 2.0 application on IIS 6, and from time to time it
crashes in production, the problem isn't directly connected to a
single machine (we have two machines runing the same code, and both
crash) - however we haven't been able to understand the reason for the
crash (though we do believe it is in our code) and also have been
unable to reproduce it in the dev or test environment.

We are currently runing IISDebugDiag on the server with the Crash Rule
activated, however the reports generated by the tool are not really
helping us (the app is managed code, and the analyser apparently
doesn't know how to reach in to get meaningful information).

I would appriciate any help in setting up the machine to catch and
debug the error, I read a bit and figure that it would require using
WinDbg on the machine itself, but the tool is kinda complicated - and
I need some information about how to set it up to collect and analyse
the crash data.

attached below is the report generated by the DebugDiag currently

Analysis Summary
Type Description Recommendation
Error In
w3wp__PID__2976__Date__01_07_2008__Time_02_15_49PM__31__Seco nd_Chance_Except=
ion_E0434F4D.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 37



This exception originated from mscorwks!RaiseTheExceptionInternalOnly
+226. Review the faulting call stack for thread 37 to determine root
cause for the exception.


Please follow up with vendor Microsoft Corporation for problem
resolution concerning the following file: C:\WINDOWS\Microsoft.NET
\Framework\v2.0.50727\mscorwks.dll.
Information DebugDiag determined that this dump file
(w3wp__PID__2976__Date__01_07_2008__Time_02_15_49PM__31__Sec ond_Chance_Excep=
tion_E0434F4D.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__2976__Date__01_07_2008__Time_02_15_49PM__31__Seco nd_Chance_Except=
ion_E0434F4D.dmp

Faulting Thread

Faulting Module Information

Report for
w3wp__PID__2976__Date__01_07_2008__Time_02_15_49PM__31__Seco nd_Chance_Except=
ion_E0434F4D.dmp
Type of Analysis Performed Crash Analysis
Machine Name DPN-DEL2
Operating System Windows Server 2003 Service Pack 2
Number Of Processors 4
Process ID 2976
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 3 day(s) 23:08:35
Process Up-Time 0 day(s) 10:44:45


Thread 37 - System ID 2152
Entry point mscorwks!Thread::intermediateThreadProc
Create time 07/01/2008 14:15:18
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0


Function Arg 1 Arg 2 Arg 3 Source
kernel32!RaiseException+53 e0434f4d 00000001 00000001
mscorwks!RaiseTheExceptionInternalOnly+226 02847158
00000000 00000000
mscorwks!RaiseTheException+4d 02847158 00000000
1ba3fb28
mscorwks!RaiseTheException+bf 00000000 1a9a8c48
f0c6dd24
mscorwks!RealCOMPlusThrow+38 02847158 00000000
7a0e38fa
mscorwks!RealCOMPlusThrow+b 02847158 f9792bd5 7a36f194
mscorwks!Thread::RaiseCrossContextException+3ac 00000000
1ba3fbd8 1ba3fc48
mscorwks!Thread::DoADCallBack+26c 00000002 79f5e3aa
1ba3fd48
mscorwks!Thread::UserResumeThread+e1 1ba3fd48 1ba3fcf4
79f55262
mscorwks!Thread::DoADCallBack+355 1ba3fd48 f9792ddd
00000001
mscorwks!Thread::DoADCallBack+541 1ba3fd48 00000002
00000000
mscorwks!Thread::DoADCallBack+575 00000002 7a078575
1ba3fdd0
mscorwks!ManagedThreadBase::KickOff+13 00000002 7a078575
1ba3fdd0
mscorwks!ThreadNative::KickOffThread+230 1a96b9f8 ba55ab20
8083e55c
mscorwks!Thread::intermediateThreadProc+49 1a9d61e0
00000000 00000000
kernel32!BaseThreadStart+34 79ed8df0 1a9d61e0 00000000

In
w3wp__PID__2976__Date__01_07_2008__Time_02_15_49PM__31__Seco nd_Chance_Except=
ion_E0434F4D.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 37

This exception originated from mscorwks!RaiseTheExceptionInternalOnly
+226. Module Information
Image Name: C:\WINDOWS\system32\kernel32.dll Symbol Type: PDB
Base address: 0x77e40000 Time Stamp: Wed Apr 18 17:25:36 2007
Checksum: 0x001083fc Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: Windows NT BASE API Client
DLL
ISAPIFilter: False File Version: 5.2.3790.4062 (srv03_sp2_gdr.
070417-0203)
Managed DLL: False Internal Name: kernel32
VB DLL: False Legal Copyright: =A9 Microsoft Corporation. All rights
reserved.
Loaded Image Name: kernel32.dll Legal Trademarks:
Mapped Image Name: Original filename: kernel32
Module name: kernel32 Private Build:
Single Threaded: False Product Name: Microsoft=AE Windows=AE Operating
System
Module Size: 1.01 MBytes Product Version: 5.2.3790.4062
Symbol File Name: c:\symcache\kernel32.pdb
\7FD4C98964054C24B2C472948D829DF52\kernel32.pdb Special Build: &