Crash/Hang IIS analysis help

Hi, we've recently upgraded to .NET 2.0 and started getting this weird
hangs/crashes, so I got debugdiag 1.1 and attached to the process, I'm
not really sure what the problem is but here is the dump analysis:

In
w3wp__PID__1636__Date__11_06_2007__Time_05_33_34PM__982__Sec ond_Chance_Exception_E0434F4D.dmp
the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS
\system32\kernel32.dll from Microsoft Corporation has caused a CLR
Exception of type (System.AccessViolationException) on thread 19

This exception originated from mscorwks!RaiseTheExceptionInternalOnly
+226.

(C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll)

Thread 19 - System ID 1948
Entry point mscorwks!Thread::intermediateThreadProc
Create time 06/11/2007 17:17:57
Time spent in user mode 0 Days 00:00:00.140
Time spent in kernel mode 0 Days 00:00:00.015

Function Source
kernel32!RaiseException+53
mscorwks!RaiseTheExceptionInternalOnly+226
mscorwks!RaiseTheException+4d
mscorwks!RaiseTheException+bf
mscorwks!RealCOMPlusThrow+38
mscorwks!RealCOMPlusThrow+b
mscorwks!Thread::RaiseCrossContextException+3ac
mscorwks!Thread::DoADCallBack+25a
mscorwks!Thread::UserResumeThread+f3
mscorwks!ManagedThreadBase::FinalizerAppDomain+26
mscorwks!SVR::CreateGCHeap+163
mscorwks!SVR::CreateGCHeap+204
mscorwks!SVR::GCHeap::FinalizerThreadWorker+e7
mscorwks!Thread::UserResumeThread+fb
mscorwks!Thread::DoADCallBack+355
mscorwks!Thread::DoADCallBack+541
mscorwks!ManagedThreadBase_NoADTransition+32
mscorwks!ManagedThreadBase::FinalizerBase+b
mscorwks!SVR::GCHeap::FinalizerThreadStart+bb
mscorwks!Thread::intermediateThreadProc+49
kernel32!BaseThreadStart+34

Thanks,
John.

Re: Crash/Hang IIS analysis help

It looks like the symbols are wrong, so the thread stack probably isn't
accurate - though it is accurate enough to point to an issue either in .Net
or your .Net code. Not enough information to tell beyond that. What are
you using to do the analysis?


wrote in message
news:1194371356.346614.300790@o80g2000hse.googlegroups.com.. .
> Hi, we've recently upgraded to .NET 2.0 and started getting this weird
> hangs/crashes, so I got debugdiag 1.1 and attached to the process, I'm
> not really sure what the problem is but here is the dump analysis:
>
> In
> w3wp__PID__1636__Date__11_06_2007__Time_05_33_34PM__982__Sec ond_Chance_Exception_E0434F4D.dmp
> the assembly instruction at kernel32!RaiseException+53 in C:\WINDOWS
> \system32\kernel32.dll from Microsoft Corporation has caused a CLR
> Exception of type (System.AccessViolationException) on thread 19
>
> This exception originated from mscorwks!RaiseTheExceptionInternalOnly
> +226.
>
> (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll)
>
> Thread 19 - System ID 1948
> Entry point mscorwks!Thread::intermediateThreadProc
> Create time 06/11/2007 17:17:57
> Time spent in user mode 0 Days 00:00:00.140
> Time spent in kernel mode 0 Days 00:00:00.015
>
> Function Source
> kernel32!RaiseException+53
> mscorwks!RaiseTheExceptionInternalOnly+226
> mscorwks!RaiseTheException+4d
> mscorwks!RaiseTheException+bf
> mscorwks!RealCOMPlusThrow+38
> mscorwks!RealCOMPlusThrow+b
> mscorwks!Thread::RaiseCrossContextException+3ac
> mscorwks!Thread::DoADCallBack+25a
> mscorwks!Thread::UserResumeThread+f3
> mscorwks!ManagedThreadBase::FinalizerAppDomain+26
> mscorwks!SVR::CreateGCHeap+163
> mscorwks!SVR::CreateGCHeap+204
> mscorwks!SVR::GCHeap::FinalizerThreadWorker+e7
> mscorwks!Thread::UserResumeThread+fb
> mscorwks!Thread::DoADCallBack+355
> mscorwks!Thread::DoADCallBack+541
> mscorwks!ManagedThreadBase_NoADTransition+32
> mscorwks!ManagedThreadBase::FinalizerBase+b
> mscorwks!SVR::GCHeap::FinalizerThreadStart+bb
> mscorwks!Thread::intermediateThreadProc+49
> kernel32!BaseThreadStart+34
>
> Thanks,
> John.
>