ASP.NET 2.0 Crash case study: Unhandled exceptions

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Paul Williams — Thu, 27 Apr 2006 17:35:52 GMT

Thank you for taking the time to write these articles. Before reading your side, I'd never really comprehended windbg. Your articles helped me use windbg to diagnose and solve some managed memory leaks in my code. In previous positions, I'd used Rational Purify to find them, but windbg seems better to me for finding leaks.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

HUgh — Thu, 27 Apr 2006 21:19:00 GMT

Your blog rocks! It's indeed much better than many debugging books out there. I really like the way you present the problem and how you approach it mostly with the help of windbg. Reading your blogs has given me very good perspectives on what's under the covers.

Please keep those coming.

Eyal’s Posts » ASP.NET 2.0, Unhandled Exceptions and Lucene.net

Eyal’s Posts » ASP.NET 2.0, Unhandled Exceptions and Lucene.net — Thu, 27 Apr 2006 23:17:01 GMT

PingBack from http://www.epocalipse.com/blog/2006/04/27/aspnet-20-unhandled-exceptions-and-lucenenet/

The 0xe0434f4d code

WWs Blog — Fri, 28 Apr 2006 11:40:00 GMT

Have you ever experienced the 0xe0434f4d exit code and thought, what the heck is that!
Tess has a nice...

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

WW — Sat, 29 Apr 2006 12:17:47 GMT

Tess, your blog is great. It has helped me out a lot, especially this post. Keep it going!

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

J. Michael Palermo IV — Sun, 30 Apr 2006 06:21:31 GMT

This is very cool. Thanks for your hard work putting this together!

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Ran Davidovitz — Mon, 01 May 2006 21:46:24 GMT

This is a basic article but never the less it seems that many ASP.NET programmer don't know issue like this.

Tess I really think that you are doing a great job in advancing the debugging operation made by ASP.NET developers.

ASP.NET developer have to understand that they must understand the concept of debugging because sooner or later they will come into the situation that they will face a problem that have to be debugged.

Thank you and keep the good job :)

What to do when the sky starts falling down

David Grey's Blog — Tue, 02 May 2006 16:21:27 GMT

I came across this post about dealing with unhandled ASP .NET exceptions on the blog of one of the Microsoft...

Programing Tools

Dan — Thu, 04 May 2006 23:04:02 GMT

TCPView

TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints...

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

rahulso — Fri, 05 May 2006 05:04:19 GMT

Awsome!!!!!!!!!!!!

Your's indeed is the best blog on debugging I have ever come across. Please keep them coming :o)

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

random — Mon, 08 May 2006 09:54:54 GMT

unintelligible

Блог баги и отладку

«XOR's Post» — Thu, 11 May 2006 12:56:29 GMT

Рекомендую почитать блог &laquo;If broken it is, fix it you should&raquo;. Детально рассматриваются различные...

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Andrew Cain — Thu, 11 May 2006 13:02:06 GMT

There is a better UnhandledExceptionHandler here: http://dotnettricks.com/blogs/andrewcainblog/archive/2006/04/18/ELMAH_for_ASPNET2_0.aspx

ASP.NET 2.0 Studium przypadku błędu: Unhandled exceptions

Lazy Developer - Ziemowit's weblog — Sat, 13 May 2006 02:12:00 GMT

Tłumaczenie rewelacyjnego tekstu Tess Ferrandez o radzeniu sobie z wyjątkami, które nie sa tak do końca oczywiste i co najgorsze są przed nami ukryte.

.NET Resources

mattonsoftware.com — Tue, 16 May 2006 15:57:18 GMT

The following links to .NET resources have been collated over time with the assistance of

colleagues.&nbsp;...

Debugging Unhandled Exceptions in ASP.NET

ScottGu's Blog — Mon, 22 May 2006 10:32:41 GMT

Tess really has the best blog I've seen that discusss how to investigate runtime issues with ASP.NET.&nbsp;...

If broken it is, fix it you should : ASP.NET 2.0 Crash case study

dotnetkicks.com — Wed, 07 Jun 2006 12:40:38 GMT

Trackback from dotnetkicks.com

Debugging Unhandled Exceptions in ASP.NET

ASP.Net — Thu, 15 Jun 2006 04:20:23 GMT

I came across a great article that discusses how to investigate runtime issues with ASP.NET.&nbsp; Tess&nbsp;is...

Programing Tools

Dan Hilderbrand — Fri, 07 Jul 2006 00:48:09 GMT

TCPView

TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints...

为什么应用程序池总是崩溃(Crash)

dudu — Wed, 12 Jul 2006 14:10:00 GMT

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

GB — Mon, 17 Jul 2006 18:08:11 GMT

Hi Tess, I've got a dump from an ASP.NET app that is not crashing, but it becomes extremely slow for apparently no reason. The # of connections to IIS grows, and the users get no response from the server, although CPU and memory comsumption are low, and things only get back to normal with an app pool restart. I've got the dump with IIS Debug&Diag Tools, and the report shows for several (24) threads that "this thread is blocked by an unhandled exception". !threads shows that of the 36 threads listed, 24 have Lock Count = 1 and Exception = "(Threadpool Worker) System.ArgumentException". I've located the exception for one of those threads with !dso and !do to use what you've shown in the post, but _remoteStackTraceString is 0x00000000. What does that mean? And how can a thread be blocked by an unhandled exception? The app is .NET 1.1 SP1. Shouldn't the framework "swallow" the exception as you said? One more thing that could be related: the app is sending e-mail messages to warn some people about unhandled exceptions, via the global ASP.NET exception handler, and this handler has been quite busy with the ThreadAbortExceptions generated by Response.Redirect. Thanks for any help on this....

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Tue, 18 Jul 2006 11:11:25 GMT

Hi GB,

Perhaps you can show the stack of one of the blocked threads, that would help determining why it is blocked (both !clrstack and kb, but you can mark out any proprietary information if you want with some suitable marker like ##### or something).

Member variables of exceptions (such as remotestacktracestring) are not always filled in, particularly the remote stack trace is not relevant to an ArgumentException, it is just an inherited member. There should be a _StackTraceString, but if you are in the middle of the exception it might not be filled out yet. If that is the case you can get the stack directly by doing !clrstack or !dumpstack

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

GB — Tue, 18 Jul 2006 17:34:53 GMT

Hi Tess!!!

Thanks for the atention. The stack is listed bellow:

0:051> kb
ChildEBP RetAddr Args to Child
06e0e4e8 7c931b34 7c916b24 ffffffff 79213ebe ntdll!KiFastSystemCallRet
06e0e4ec 7c916b24 ffffffff 79213ebe 00000000 ntdll!NtQueryVirtualMemory+0xc
06e0e54c 7c9240b3 79213ebe 00000000 1433329c ntdll!RtlIsValidHandler+0x82
06e0e5c0 7c93eda4 06e0a000 06e0e5d0 00010007 ntdll!RtlDispatchException+0x78
06e0e8a0 7c815dea 06e0e8b0 04961118 e0434f4d ntdll!RtlRaiseException+0x3d
06e0e900 79216aed e0434f4d 00000001 00000000 kernel32!RaiseException+0x53
06e0e958 7924c8d0 10824018 00000000 00000000 mscorsvr!RaiseTheException+0xa0
06e0e9c4 0434da75 06e0e9fc 1433329c 10823ed8 mscorsvr!JIT_Throw+0x4d
WARNING: Frame IP not in any known module. Following frames may be wrong.
06e0e9c8 06e0e9fc 1433329c 10823ed8 18671934 0x434da75
06e0e9cc 1433329c 10823ed8 18671934 03f3b330 0x6e0e9fc
06e0e9fc 03f3b178 06e0ea54 1c889210 18660d04 0x1433329c
06e0ea00 06e0ea54 1c889210 18660d04 18672bac 0x3f3b178
06e0ea04 1c889210 18660d04 18672bac 04759350 0x6e0ea54
06e0ea54 047592ae 0475a675 047580e0 06e0eb08 0x1c889210
06e0ea58 0475a675 047580e0 06e0eb08 108eb5e4 0x47592ae
06e0ea5c 047580e0 06e0eb08 108eb5e4 1078f7d8 0x475a675
06e0ea60 06e0eb08 108eb5e4 1078f7d8 1c72fa10 0x47580e0
06e0ea64 108eb5e4 1078f7d8 1c72fa10 00000001 0x6e0eb08
06e0ebcc 799a67a2 108e64d4 108e67d8 799b4168 0x108eb5e4
06e0ebd8 799b4168 00000002 00000000 020b480c mscorlib_79990000+0x167a2

0:051> !dumpstack -ee
Thread 51
Current frame:
ChildEBP RetAddr Caller,Callee
06e0e920 799a3ed5 (MethodDesc 0x79b96470 +0x115 System.Text.StringBuilder.Append)
06e0e9b4 0434df05 (MethodDesc 0x424e988 +0x55 System.Data.ExceptionBuilder.ColumnNotInTheTable)
06e0e9c4 0434da75 (MethodDesc 0x40abb70 +0x7d System.Data.DataRow.IsNull)
06e0e9d8 03f3b330 (MethodDesc 0x230e650 +0x20 SGI.Common.Library.getInt32)
06e0e9fc 03f3b178 (MethodDesc 0x230e570 +0x250 SGI.Common.Library.ValidTypeProperty)
06e0ea10 04759350 (MethodDesc 0x4741370 +0x88 SGI.Common.List.ReadProperties)
06e0ea24 03f3fa32 (MethodDesc 0x3fbf3b0 +0x62 SGI.BusinessObject.Coorporativo.UnidadeFuncional..ctor)
06e0ea44 0475d183 (MethodDesc 0x4748bb0 +0x4b SGI.BusinessObject.Academico.Turma..ctor)
06e0ea54 047592ae (MethodDesc 0x4741380 +0x6 SGI.Common.List.getNext)
06e0ea58 0475a675 (MethodDesc 0x4749df8 +0x5 SGI.BusinessObject.Academico.MatriculaInscritoList.SGI.Common.IObjectList.getNext)
06e0ea5c 047580e0 (MethodDesc 0x230be30 +0x1c8 SGI.UI.Matricula.matricula.BindGradeHoraria)
06e0ea8c 0475412a (MethodDesc 0x230bd30 +0x92 SGI.UI.Matricula.matricula.Page_Load)
06e0ea9c 03fc3c3c (MethodDesc 0x22efcf0 +0x44 System.Web.UI.Control.OnLoad)
06e0eab0 03fc3b84 (MethodDesc 0x22efd00 +0x24 System.Web.UI.Control.LoadRecursive)
06e0eac4 03f49a7f (MethodDesc 0x23814d8 +0x2ef System.Web.UI.Page.ProcessRequestMain)
06e0eaec 03f49547 (MethodDesc 0x2381368 +0x1f System.Web.UI.Page.set_FileDependencies)
06e0eaf8 03f30442 (MethodDesc 0x230c708 +0x32 ASP.matricula_aspx.FrameworkInitialize)
06e0eb08 03f472d7 (MethodDesc 0x2381498 +0x77 System.Web.UI.Page.ProcessRequest)
06e0eb44 03f46d3b (MethodDesc 0x2381488 +0x13 System.Web.UI.Page.ProcessRequest)
06e0eb4c 03f46d14 (MethodDesc 0x2387c50 +0xb4 System.Web.HttpApplication/CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute)
06e0eb5c 03df9838 (MethodDesc 0x217d730 +0x58 System.Web.HttpApplication.ExecuteStep)
06e0eba0 03df92a2 (MethodDesc 0x217d760 +0xfa System.Web.HttpApplication.ResumeSteps)
06e0ebcc 799a67a2 (MethodDesc 0x79bc5b08 +0x12 System.Runtime.InteropServices.GCHandle..ctor)
06e0ebd8 799b4168 (MethodDesc 0x79bc5b28 +0x10 System.Runtime.InteropServices.GCHandle.Alloc)
06e0ebec 03df9173 (MethodDesc 0x217d800 +0xe3 System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest)
06e0ec00 01fd68a7 (MethodDesc 0x1b59888 +0x1e7 System.Web.HttpRuntime.ProcessRequestInternal)
06e0ec44 01fd6458 (MethodDesc 0x1b59988 +0xb0 System.Web.HttpRuntime.ProcessRequest)
06e0ec50 01fd2fd5 (MethodDesc 0x1b584d0 +0x65 System.Web.Hosting.ISAPIRuntime.ProcessRequest)

The exception:

0:051> !do 0x10824018
Name: System.ArgumentException
MethodTable 0x79b9edec
EEClass 0x79b9ee74
Size 68(0x44) bytes
GC Generation: 0
mdToken: 0x0200003a (c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll)
FieldDesc*: 0x79b9eed8
MT Field Offset Type Attr Value Name
0x79b96824 0x400001d 0x4 CLASS instance 0x00000000 _className
0x79b96824 0x400001e 0x8 CLASS instance 0x00000000 _exceptionMethod
0x79b96824 0x400001f 0xc CLASS instance 0x00000000 _exceptionMethodString
0x79b96824 0x4000020 0x10 CLASS instance 0x10823f34 _message
0x79b96824 0x4000021 0x14 CLASS instance 0x00000000 _innerException
0x79b96824 0x4000022 0x18 CLASS instance 0x00000000 _helpURL
0x79b96824 0x4000023 0x1c CLASS instance 0x00000000 _stackTrace
0x79b96824 0x4000024 0x20 CLASS instance 0x00000000 _stackTraceString
0x79b96824 0x4000025 0x24 CLASS instance 0x00000000 _remoteStackTraceString
0x79b96824 0x4000026 0x2c System.Int32 instance 0 _remoteStackIndex
0x79b96824 0x4000027 0x30 System.Int32 instance -2147024809 _HResult
0x79b96824 0x4000028 0x28 CLASS instance 0x00000000 _source
0x79b96824 0x4000029 0x34 System.Int32 instance 0 _xptrs
0x79b96824 0x400002a 0x38 System.Int32 instance -532459699 _xcode
0x79b9edec 0x40000d7 0x3c CLASS instance 0x00000000 m_paramName
-----------------
Exception 10824018 in MT 79b9edec: System.ArgumentException
_message: A coluna 'idSituacaoCurso' não pertence à tabela Table.

[OBS1. the _message means "The column 'idSituacaoCurso' does not belong to table Table".]
[OBS2. I got the exception by running !dso and then !do on the only object listed by !dso that was an instance of Exception.]

The customer gave me a PST Outlook file with the messages that the site generates on each unhandled exception. There were 16.000 (sixteen THOUSAND) messages on a five-day interval. So I monitored ".NET CLR Exceptions\# of Exceps Thrown" and ".NET CLR Exceptions\# of Exceps Thrown/s" with perfmon. The # of exceps thrown/s was at an average of 447 on a 9h30min interval, with maximum at 5.700. PER SECOND!!!! So looking at the code I saw that the SGI.Common.List.ReadProperties() method is extremely likely to be the cause of such a high exception count. But could this count be the cause of the blocked threads? I'm proposing a code change that will avoid this high exception count, but just looking at the dump I have no "black & white" explanation to relate the high exception count to the hung threads.

Sorry to take advantage of your spare time like this.... It's the price one pays for being famous ;) - and kind enough to anwser the questions.

Thanks again

Gilberto

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Fri, 21 Jul 2006 19:45:26 GMT

To be honest, the thread doesnt really appear to be stuck, but perhaps that message you are getting is due to the shear amount of exceptions you are getting.

I think it is a fair assumption to make that this exception is probably common as the message seems to indicate that there is an error in the code (giving the wrong column name) which would occurr every time you go through this code path. But to get a better understanding of what exceptions you get, you can run !DumpAllExceptions or !DumpAllExceptions -v to see what types of exceptions you have gotten recently and how many.

An educated guess would be that without the high amount of exceptions you will not be hung. There is no other reason for the hung state on this thread.

Thanks Tess

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

GB — Mon, 24 Jul 2006 17:48:00 GMT

Ok Tess,

Thanks a lot. That's was my conclusion too, I'm writing it now on my report. Perhaps I could quote you on this?.....

;) just kidding

Thanks,

GB

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Wed, 26 Jul 2006 23:16:39 GMT

Feel free:)

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

TM — Fri, 11 Aug 2006 02:47:44 GMT

This helped us with part of our problem, but IIS keeps crashing over exception 0x00015dea. I have been trying to figure out what this exception refers to, but I can't find it.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Fri, 11 Aug 2006 09:02:29 GMT

Hi TM,

To be honest that looks more like an address than an exit code or an exception code. In fact that address often shows up as the faulting address in kernel32 during a fatal exception.

I would run adplus straight up in crash mode (without any config files to begin with) and look at the dump that gets generated when the process exits, as well as the log files to look for strange exceptions before the exit.

HTH

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

mash — Wed, 06 Sep 2006 00:27:12 GMT

I'm a WinDbg newbie and your blog's a life saver! Thanks!

I've got a question...when I open crash dumps and run the "!threads" command, I see a list of threads along with the one that caused the exception. But unlike the examples stated in this blog, I don't see the address of the function that caused the exception.

Here's the sample dump:

0:000> !threads
succeeded
Loaded Son of Strike data table version 5 from "C:\WINMD\Microsoft.NET\Framework\v1.1.4322\mscorsvr.dll"
ThreadCount: 7
UnstartedThread: 0
BackgroundThread: 5
PendingThread: 0
DeadThread: 2
PreEmptive GC Alloc Lock
ID ThreadOBJ State GC Context Domain Count APT Exception
XXX 0 0c9e0a20 1820 Enabled 00000000:00000000 000b0458 0 Ukn System.FormatException

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Wed, 06 Sep 2006 15:50:48 GMT

Hi Mash,

The exception address is only available in sos.dll for 2.0, and just in case you are debugging for the unhandled exception, that only happens in 2.0.

But... if you are interested in that format exception you should be able to find it using !dumpheap -type FormatException

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Arnaut — Tue, 19 Sep 2006 14:21:16 GMT

I'm getting the same error too. I'm also getting Thread aborts and a crashing IIS. I think the source is the .Redirect, because my application is logging this it's own log in a database.

Anyone found a solution for this?

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Tue, 19 Sep 2006 14:53:05 GMT

A redirect would occurr on an ASP.NET thread and thus it would not crash the process.

It is normal for redirect to throw threadabort exceptions as it has to abort the code execution on the current thread, and this is unharmful, since we are aborting ourselfs and thus we can not be in a part of code where we are executing anything that can not be aborted.

I think you need to look elsewhere for your crashing exception, a crash dump would probably be the best option.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Arnaut — Tue, 19 Sep 2006 15:00:23 GMT

Uhm, yes, your right. Saw that a couple of minutes ago. I've installed IIS diagnostics (max crash logging) and now it's waiting for the next crash.
Thanks for the quick reply!

ASP.NET 2.0 Debugging steps I should really know

Rob Gillen's WebLog — Thu, 09 Nov 2006 07:02:37 GMT

As part of my "not-my-real-job" time, I do a little website hosting - basically to keep my

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Howard — Tue, 14 Nov 2006 14:41:48 GMT

This is more a general question about HttpModules, all the documentation seems to suggest that when you add an HttpModule to your web.config file you only get one single instance of your HttpModule per HttpApplication, is this really true?

I've been running some load tests generating 1000s of requests and when I've windbg'd the worker process and done a dumpheap -type on my HttpModule class there's loads of 'em. But if we're only supposed to get one instance per HttpApplication, how's this possible?

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Howard — Wed, 15 Nov 2006 14:29:51 GMT

Actually it appears that ASP.NET creates a pool of HttpModules to handle multiple requests and the number created increases with load. I wonder what algorithm is used to determine how many instances of the HttpModule to create?

So this would mean that the HttpModule code from the kb article will only work for the first instance of that particular HttpModule.

Well, you learn something everyday day.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Wed, 15 Nov 2006 15:23:07 GMT

I am afraid I don't follow you at all...

What is the problem? If you get an unhandled exception, this module will handle it whether there is a pool of such handlers or only one. Are you seeing something different? I would be a bit surprised if you were...

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Howard — Wed, 15 Nov 2006 16:21:04 GMT

What I mean't was that in the kb article the code uses a static bool to determine whether the module has already been initialized and hence to hook up the event handlers or not in the Init() method.

So when any subsequent instances of the module class are created this bool flag is already set to true. Which means these instances will not have event handlers set up for them.

Well, thats what it seems like anyway, as a % of my requests don't get processed. The first x number do, then it goes hit & miss. This only happens under heavy load, ie when I've got a pool of these handlers created. Everytime I've had a request that hasn't been processed I've checked with !dumpheap -type and there's always multiple instances of the module class.

When I comment out the static bool flag all my requests get processed when it's under load.

Hope that makes sense.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Joe — Thu, 30 Nov 2006 20:29:16 GMT

Just in case anyone uses active reports, we ran across an issue where our application was terminating unexpectedly and it turned out to be related to a bug in their code.

http://www.datadynamics.com/forums/3/96793/ShowPost.aspx#96793

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Warrier — Sun, 21 Jan 2007 01:56:30 GMT

Hi Tess,

I cannot use a debugger to troubleshoot the issue in this case. The HttpModule you referred to works for a ASP.NET app. Can you give me some idea on how to do this for a Windows Service (in 2.0) that is doing some async operations for TCP Sockets?

Thanks,

Warrier

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Mon, 22 Jan 2007 11:44:44 GMT

Hi Warrier,

Unfortunately a windows service is not "hosted" the same way that an asp.net app is so as you mentioned you don't have the same harness of events, modules and handlers, so you would have to create a harness yourself which is not completely trivial (ok, understatement of the year:))

Where do you get the exceptions? Would it be possible to have exception handlers just around the code that makes the async operations?

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

manche — Thu, 22 Feb 2007 22:50:37 GMT

Hi Tess,

I'm new to WinDbg and you blog was very helpful!

I've got a question...When I run my application, the worker process crashes.. i started debugging using WinDbg..

when I open crash dumps, following exceptions is shown

In w3wp__PID__1368__Date__02_22_2007__Time_11_07_03AM__329__Second_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.CannotUnloadAppDomainException) on thread 14

This exception originated from mscorwks!RaiseTheExceptionInternalOnly+226.

Thread 14 - System ID 1568

Entry point mscorwks!ThreadpoolMgr::intermediateThreadProc

Create time 2/22/2007 10:56:57 AM

Time spent in user mode 0 Days 0:0:16.625

Time spent in kernel mode 0 Days 0:0:25.46

Function Arg 1 Arg 2 Arg 3 Source

kernel32!RaiseException+53 e0434f4d 00000001 00000001

mscorwks!RaiseTheExceptionInternalOnly+226 1d00e1d0 00000000 00000000

mscorwks!RaiseTheException+4c 1d00e1d0 00000000 019dfb68

mscorwks!RaiseTheException+be 00000000 000e1f00 b59aaf96

mscorwks!RealCOMPlusThrow+37 1d00e1d0 00000000 7a0e0701

mscorwks!RealCOMPlusThrow+a 1d00e1d0 b40c20e3 7a36a7d0

mscorwks!Thread::RaiseCrossContextException+63 00000000 019dfc18 019dfc88

mscorwks!Thread::DoADCallBack+26c 00000007 79f3a0a1 019dfd88

mscorwks!Thread::UserResumeThread+e1 019dfd88 019dfd34 79f93fe6

mscorwks!Thread::DoADCallBack+355 019dfd88 b40c26eb 00000001

mscorwks!Thread::DoADCallBack+541 019dfd88 00000007 00000000

mscorwks!Thread::DoADCallBack+575 00000007 7a07bd61 019dfdf8

mscorwks!ManagedThreadBase::ThreadPool+13 00000007 7a07bd61 019dfdf8

mscorwks!QueueUserWorkItemCallback+9d 00110a90 77e6bb9d 7a38e228

mscorwks!ThreadpoolMgr::ExecuteWorkRequest+40 08e67868 b40c2503 00000000

mscorwks!ThreadpoolMgr::WorkerThreadStart+1f2 00000000 00000000 00000000

mscorwks!ThreadpoolMgr::intermediateThreadProc+49 000c89a0 00000000 00000000

kernel32!BaseThreadStart+34 79f710dd 000c89a0 00000000

Using this information i am not able to figure out where the error is occured.

Also I am creating timer on thread in ASP.Net application and the timer is disposed in Application_End event.

Can you give me some idea where should i start looking inorder to resolve the issue?

Thanks

manche

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Fri, 23 Feb 2007 10:24:10 GMT

You can try to run !threads to see what the last exception was on that thread and run !pe on it, or run !dso to find the exception on the stack. It is definitely an unhandled .net exception but it is not possible from the stack you sent to see what the exception was.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

manche — Fri, 23 Feb 2007 21:43:41 GMT

Thanks for your response...

0:014> !threads

PDB symbol for mscorwks.dll not loaded

ThreadCount: 10

UnstartedThread: 0

BackgroundThread: 10

PendingThread: 0

DeadThread: 0

Hosted Runtime: no

PreEmptive GC Alloc Lock

ID OSID ThreadOBJ State GC Context Domain Count APT Exception

14 1 620 000e1f00 1808220 Enabled 00000000:00000000 000dee68 0 STA (Threadpool Worker) System.CannotUnloadAppDomainException (1d00e1d0)

16 2 630 000ee228 b220 Enabled 00000000:00000000 000dee68 0 MTA (Finalizer)

17 3 880 00101f60 80a220 Enabled 00000000:00000000 000dee68 0 MTA (Threadpool Completion Port)

18 4 884 00105340 1220 Enabled 00000000:00000000 000dee68 0 Ukn

12 5 1ec 05983130 880a220 Enabled 00000000:00000000 000dee68 0 MTA (Threadpool Completion Port)

20 6 7c4 00176e68 180b220 Enabled 00000000:00000000 000dee68 0 MTA (Threadpool Worker)

21 7 9c0 059def98 880b220 Enabled 00000000:00000000 000dee68 0 MTA (Threadpool Completion Port)

25 a e6c 08cf8f58 180b220 Enabled 00000000:00000000 109aedd0 1 MTA (Threadpool Worker)

26 b 78c 08d80370 880b220 Enabled 00000000:00000000 000dee68 0 MTA (Threadpool Completion Port)

28 c f38 108e8770 7221 Enabled 00000000:00000000 1090fd38 0 STA

0:014> !dso

OS Thread Id: 0x620 (14)

ESP/REG Object Name

019df9f8 1d00e1d0 System.CannotUnloadAppDomainException

019df9fc 1d00e1d0 System.CannotUnloadAppDomainException

019dfa44 1d00e1d0 System.CannotUnloadAppDomainException

019dfa58 1d00e1d0 System.CannotUnloadAppDomainException

019dfaac 1d00e1d0 System.CannotUnloadAppDomainException

019dfab8 1d00e1d0 System.CannotUnloadAppDomainException

019dfb54 1cfe9cb4 System.CannotUnloadAppDomainException

019dfb58 1d00cc54 System.Byte[]

019dfb84 1d00e1d0 System.CannotUnloadAppDomainException

019dfb88 1d00cc54 System.Byte[]

019dfb98 1d00cc54 System.Byte[]

019dfc24 022e5f28 System.Threading.ExecutionContext

0:014> !pe

Exception object: 1d00e1d0

Exception type: System.CannotUnloadAppDomainException

Message: Error while unloading appdomain. (Exception from HRESULT: 0x80131015)

InnerException: <none>

StackTrace (generated):

<none>

StackTraceString: <none>

HResult: 80131015

0:014> !do 1d00e1d0

Name: System.CannotUnloadAppDomainException

MethodTable: 7915d434

EEClass: 791e7ea4

Size: 72(0x48) bytes

(C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll)

Fields:

MT Field Offset Type VT Attr Value Name

790fa3e0 40000b5 4 System.String 0 instance 1d00f048 _className

79109208 40000b6 8 ...ection.MethodBase 0 instance 00000000 _exceptionMethod

790fa3e0 40000b7 c System.String 0 instance 1d00f7d8 _exceptionMethodString

790fa3e0 40000b8 10 System.String 0 instance 1d00f194 _message

79113dfc 40000b9 14 ...tions.IDictionary 0 instance 1d0104fc _data

790fa9e8 40000ba 18 System.Exception 0 instance 00000000 _innerException

790fa3e0 40000bb 1c System.String 0 instance 00000000 _helpURL

790f9c18 40000bc 20 System.Object 0 instance 00000000 _stackTrace

790fa3e0 40000bd 24 System.String 0 instance 00000000 _stackTraceString

790fa3e0 40000be 28 System.String 0 instance 1d011274 _remoteStackTraceString

790fed1c 40000bf 34 System.Int32 0 instance 0 _remoteStackIndex

790f9c18 40000c0 2c System.Object 0 instance 00000000 _dynamicMethods

790fed1c 40000c1 38 System.Int32 0 instance -2146234347 _HResult

790fa3e0 40000c2 30 System.String 0 instance 1d00fa2c _source

790fe160 40000c3 3c System.IntPtr 0 instance 0 _xptrs

790fed1c 40000c4 40 System.Int32 0 instance 0 _xcode

0:014> !do 1d00f048

Name: System.String

MethodTable: 790fa3e0

EEClass: 790fa340

Size: 92(0x5c) bytes

(C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll)

String: System.CannotUnloadAppDomainException

Fields:

MT Field Offset Type VT Attr Value Name

790fed1c 4000096 4 System.Int32 0 instance 38 m_arrayLength

790fed1c 4000097 8 System.Int32 0 instance 37 m_stringLength

790fbefc 4000098 c System.Char 0 instance 53 m_firstChar

790fa3e0 4000099 10 System.String 0 shared static Empty

>> Domain:Value 000dee68:790d6584 109aedd0:790d6584 05a4bf60:790d6584 08da9588:790d6584 08e39ef0:790d6584 108cb728:790d6584 1090fd38:790d6584 <<

79124670 400009a 14 System.Char[] 0 shared static WhitespaceChars

>> Domain:Value 000dee68:022d13b8 109aedd0:02ae15b0 05a4bf60:023d4778 08da9588:024d163c 08e39ef0:025a5a2c 108cb728:0268db34 1090fd38:026ea248 <<

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

manche — Fri, 23 Feb 2007 21:52:22 GMT

Opps I accidently clicked on submit button..

I have verified the code and all the threads are disposed. Can you find any details with the give information?

Once again thanks for all your help...

Thanks

manche

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Mon, 26 Feb 2007 09:56:50 GMT

Hi Manche,

Try dumping out all the other members of the exception as well to see if they give any additional info. If they don't you might want to open a request with support if you want to troubleshoot it further, but the way it looks is like this might be a problem at shutdown and if you run ~* kb and ~* e !clrstack you may see some threads sitting in a hung state.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Manche — Mon, 26 Feb 2007 16:47:30 GMT

Hi Tess

Thanks for your response.

As per the following info, it looks like the error is thrown from an unmanaged code. In our application we are using a third pary component and its that which is causing the problem....

0:014> ~*kb

0 Id: 558.55c Suspend: 1 Teb: 7ffdf000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0006fc7c 77e6ba42 00000154 ffffffff 00000000 ntdll!KiFastSystemCallRet

0006fc90 5a36467a 00000154 ffffffff 00000000 kernel32!WaitForSingleObject+0x12

0006ff0c 0100187c 00000007 00253a68 00000000 w3dt!IPM_MESSAGE_PIPE::operator=+0x1b31

0006ff44 01001a23 00000007 00253a68 002542e0 w3wp+0x187c

0006ffc0 77e523e5 00000000 00000000 7ffda000 w3wp+0x1a23

0006fff0 00000000 010018f8 00000000 78746341 kernel32!IsProcessorFeaturePresent+0x9e

1 Id: 558.5ac Suspend: 1 Teb: 7ffdd000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

009bffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

009bffec 00000000 7c81fddf 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

2 Id: 558.5c8 Suspend: 1 Teb: 7ffdc000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

009fffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

009fffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

3 Id: 558.5dc Suspend: 1 Teb: 7ffdb000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00a5ff84 77c5778f 00a5ffac 77c5f7dd 000a56e8 ntdll!KiFastSystemCallRet

00a5ff8c 77c5f7dd 000a56e8 00000000 00000000 rpcrt4!NdrOleFree+0x3c5

00a5ffac 77c5de88 0008fdc0 00a5ffec 77e6608b rpcrt4!I_RpcTransGetThreadEvent+0x188

00a5ffb8 77e6608b 000a5990 00000000 00000000 rpcrt4!I_RpcLogEvent+0xe92

00a5ffec 00000000 77c5de6d 000a5990 00000000 kernel32!GetModuleFileNameA+0xeb

4 Id: 558.5e0 Suspend: 1 Teb: 7ffd8000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00c5ff54 5a30249e 00000148 00c5ff7c 00c5ff80 ntdll!KiFastSystemCallRet

00c5ff8c 5a3026bc 00000000 00258310 5a300000 w3tp!THREAD_POOL::PostCompletion+0x89

00c5ffa0 5a301db9 00258238 00000000 00000000 w3tp!THREAD_POOL::~THREAD_POOL+0x153

00c5ffb8 77e6608b 00258310 00000000 00000000 w3tp+0x1db9

00c5ffec 00000000 5a301d80 00258310 00000000 kernel32!GetModuleFileNameA+0xeb

5 Id: 558.5e4 Suspend: 1 Teb: 7ffd7000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00c9ff54 5a30249e 00000148 00c9ff7c 00c9ff80 ntdll!KiFastSystemCallRet

00c9ff8c 5a3026bc 00000000 00258330 5a300000 w3tp!THREAD_POOL::PostCompletion+0x89

00c9ffa0 5a301db9 00258238 00000000 00000000 w3tp!THREAD_POOL::~THREAD_POOL+0x153

00c9ffb8 77e6608b 00258330 00000000 00000000 w3tp+0x1db9

00c9ffec 00000000 5a301d80 00258330 00000000 kernel32!GetModuleFileNameA+0xeb

6 Id: 558.5e8 Suspend: 1 Teb: 7ffd6000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00cdff54 5a30249e 00000148 00cdff7c 00cdff80 ntdll!KiFastSystemCallRet

00cdff8c 5a3026bc 00000000 00258350 5a300000 w3tp!THREAD_POOL::PostCompletion+0x89

00cdffa0 5a301db9 00258238 00000000 00000000 w3tp!THREAD_POOL::~THREAD_POOL+0x153

00cdffb8 77e6608b 00258350 00000000 00000000 w3tp+0x1db9

00cdffec 00000000 5a301d80 00258350 00000000 kernel32!GetModuleFileNameA+0xeb

7 Id: 558.5f0 Suspend: 1 Teb: 7ffd5000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00d1ff54 5a30249e 00000148 00d1ff7c 00d1ff80 ntdll!KiFastSystemCallRet

00d1ff8c 5a3026bc 00000000 00258370 5a300000 w3tp!THREAD_POOL::PostCompletion+0x89

00d1ffa0 5a301db9 00258238 00000000 00000000 w3tp!THREAD_POOL::~THREAD_POOL+0x153

00d1ffb8 77e6608b 00258370 00000000 00000000 w3tp+0x1db9

00d1ffec 00000000 5a301d80 00258370 00000000 kernel32!GetModuleFileNameA+0xeb

8 Id: 558.5f4 Suspend: 1 Teb: 7ffd4000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

00ddffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

00ddffec 00000000 7c83abb0 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

9 Id: 558.5fc Suspend: 1 Teb: 7ffaf000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

017bfaf8 77e6ba42 000001b4 ffffffff 00000000 ntdll!KiFastSystemCallRet

017bfb0c 5a3b8147 000001b4 ffffffff 00000000 kernel32!WaitForSingleObject+0x12

017bffb8 77e6608b 00000000 00000000 00000000 w3core!W3_FILE_INFO_CACHE::GetFileCache+0xd784

017bffec 00000000 5a3b8021 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

10 Id: 558.604 Suspend: 1 Teb: 7ffae000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

017fff84 77c5778f 017fffac 77c5f7dd 000a56e8 ntdll!KiFastSystemCallRet

017fff8c 77c5f7dd 000a56e8 00000000 00000000 rpcrt4!NdrOleFree+0x3c5

017fffac 77c5de88 0008fdc0 017fffec 77e6608b rpcrt4!I_RpcTransGetThreadEvent+0x188

017fffb8 77e6608b 000b6298 00000000 00000000 rpcrt4!I_RpcLogEvent+0xe92

017fffec 00000000 77c5de6d 000b6298 00000000 kernel32!GetModuleFileNameA+0xeb

11 Id: 558.554 Suspend: 1 Teb: 7ffad000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0183ffb8 77e6608b 000bd918 00000000 00000000 ntdll!KiFastSystemCallRet

0183ffec 00000000 7c815228 000bd918 00000000 kernel32!GetModuleFileNameA+0xeb

12 Id: 558.1ec Suspend: 1 Teb: 7ffac000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0195fea8 79f2f30a 00000228 0195feec 0195fee8 ntdll!KiFastSystemCallRet

0195ff14 79f71123 00000000 00000000 00000000 mscorwks!CreateAssemblyCache+0x2125c

00000000 00000000 00000000 00000000 00000000 mscorwks!CompareAssemblyIdentity+0xd4f4

13 Id: 558.208 Suspend: 1 Teb: 7ffab000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0199feb0 79f2c9f3 000001f4 00000000 b4082573 ntdll!KiFastSystemCallRet

0199fee4 79f2c9c3 000001f4 00000000 b408248f mscorwks!CreateAssemblyCache+0x1e945

0199ff18 79f758ec 000001f4 00000000 79f2c895 mscorwks!CreateAssemblyCache+0x1e915

0199ffb8 77e6608b 00000000 00000000 00000000 mscorwks!CompareAssemblyIdentity+0x11cbd

0199ffec 00000000 79f2c800 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

# 14 Id: 558.620 Suspend: 1 Teb: 7ffaa000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

019df9dc 79f97065 e0434f4d 00000001 00000001 kernel32!RaiseException+0x3c

019dfa3c 7a05b942 1d00e1d0 00000000 00000000 mscorwks!DllCanUnloadNowInternal+0x37a9

019dfa78 7a05b9eb 00000000 000e1f00 b59aaf96 mscorwks!GetAddrOfContractShutoffFlag+0xa7d7

019dfaa4 7a05b9f6 1d00e1d0 00000000 7a0e0701 mscorwks!GetAddrOfContractShutoffFlag+0xa880

019dfbc8 79f993a2 019a1000 019e0000 019dfc88 mscorwks!GetAddrOfContractShutoffFlag+0xa88b

00000000 00000000 00000000 00000000 00000000 mscorwks!DllCanUnloadNowInternal+0x5ae6

15 Id: 558.624 Suspend: 1 Teb: 7ffa9000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

01abfedc 77e6109d 00000003 01abff20 00000000 ntdll!KiFastSystemCallRet

01abfef8 79ed4b06 00000003 01abff20 00000000 kernel32!WaitForMultipleObjects+0x18

01abff58 79ed4a63 b43a241f 00000000 00000000 mscorwks!InitializeFusion+0x266e

01abff88 79ed49a6 b43a242f 00000000 00000000 mscorwks!InitializeFusion+0x25cb

01abffb8 77e6608b 00000000 00000000 00000000 mscorwks!InitializeFusion+0x250e

01abffec 00000000 79ed4960 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

16 Id: 558.630 Suspend: 1 Teb: 7ffa8000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

01bbfd78 77e6109d 00000002 7a381bb8 00000000 ntdll!KiFastSystemCallRet

01bbfd94 79f8d98a 00000002 7a381bb8 00000000 kernel32!WaitForMultipleObjects+0x18

01bbfdb4 79ea2e68 000ee1f8 01bbfe6c 01bbfeb4 mscorwks!StrongNameFreeBuffer+0x46b2

01bbfdc8 79ecb4a4 01bbfeb4 00000000 00000001 mscorwks!CreateAssemblyNameObject+0x7fc

00000000 00000000 00000000 00000000 00000000 mscorwks!CreateApplicationContext+0xc940

17 Id: 558.880 Suspend: 1 Teb: 7ffa7000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

01c6ff34 79f446b6 0000059e 00000001 01c6ffa4 ntdll!KiFastSystemCallRet

01c6ffb0 79f44647 00000000 77e6608b 019de77c mscorwks!GetMetaDataPublicInterfaceFromInternal+0xdf7

01c6ffec 00000000 79f445ef 019de77c 00000000 mscorwks!GetMetaDataPublicInterfaceFromInternal+0xd88

18 Id: 558.884 Suspend: 1 Teb: 7ffa6000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

01cafd2c 79e77fd1 000002c0 ffffffff 00000000 ntdll!KiFastSystemCallRet

01cafd70 79e77f9a 000002c0 ffffffff 00000000 mscorwks!DllUnregisterServerInternal+0x47b1

01cafdc0 79e77f50 ffffffff 00000000 00000000 mscorwks!DllUnregisterServerInternal+0x477a

01cafe50 79e7839d 01cafde4 01cafde4 00105810 mscorwks!DllUnregisterServerInternal+0x4730

01cafe60 79e782dc 00000000 00000001 00000001 mscorwks!DllUnregisterServerInternal+0x4b7d

01cafe94 79ecb00b 00105340 00000000 00000000 mscorwks!DllUnregisterServerInternal+0x4abc

01caffb8 77e6608b 00105810 00000000 00000000 mscorwks!CreateApplicationContext+0xc4a7

01caffec 00000000 79ecafc5 00105810 00000000 kernel32!GetModuleFileNameA+0xeb

19 Id: 558.ce0 Suspend: 1 Teb: 7ffa4000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

061cff6c 77e6109d 00000003 769cf34c 00000000 ntdll!KiFastSystemCallRet

061cff88 76928415 00000003 769cf34c 00000000 kernel32!WaitForMultipleObjects+0x18

061cffb8 77e6608b 00000000 00000000 00000000 userenv!GetProfilesDirectoryW+0x1de

061cffec 00000000 769283b9 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

20 Id: 558.7c4 Suspend: 1 Teb: 7ffa3000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

064efc7c 79e77fd1 0000021c 00009c40 00000000 ntdll!KiFastSystemCallRet

064efcc0 79e77f9a 0000021c 00009c40 00000000 mscorwks!DllUnregisterServerInternal+0x47b1

064efd10 79e77f50 00009c40 00000000 00000000 mscorwks!DllUnregisterServerInternal+0x477a

064efda0 7a1121c3 000bc898 00009c40 00000000 mscorwks!DllUnregisterServerInternal+0x4730

064efe14 79ecb00b 00000000 f72e1b10 809809f0 mscorwks!TranslateSecurityAttributes+0x277e6

064effb8 77e6608b 059c4218 00000000 00000000 mscorwks!CreateApplicationContext+0xc4a7

064effec 00000000 79ecafc5 059c4218 00000000 kernel32!GetModuleFileNameA+0xeb

21 Id: 558.9c0 Suspend: 1 Teb: 7ffa2000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0710fd28 79f2f30a 00000228 0710fd6c 0710fd68 ntdll!KiFastSystemCallRet

0710fd94 79ecb00b 00000000 00000000 00000000 mscorwks!CreateAssemblyCache+0x2125c

00000000 00000000 00000000 00000000 00000000 mscorwks!CreateApplicationContext+0xc4a7

22 Id: 558.2d8 Suspend: 1 Teb: 7ffa0000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0741ff34 77694ff1 0741ff58 00000000 00000000 ntdll!KiFastSystemCallRet

0741ff74 776cf35b 00007530 77e6ba50 059ee928 ole32!GetHGlobalFromStream+0x13c3

0741ff90 776cf2a3 0741ffb8 776b2307 77790438 ole32!OleDoAutoConvert+0x10ee

0741ff98 776b2307 77790438 00000000 059ee928 ole32!OleDoAutoConvert+0x1036

0741ffb8 77e6608b 059ee928 00000000 00000000 ole32!IsValidInterface+0x4db

0741ffec 00000000 776b2354 059ee928 00000000 kernel32!GetModuleFileNameA+0xeb

23 Id: 558.b34 Suspend: 1 Teb: 7ff3f000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

09bbfd74 77e6ba42 000009cc 00002710 00000000 ntdll!KiFastSystemCallRet

09bbfd88 75bb22b9 000009cc 00002710 00000000 kernel32!WaitForSingleObject+0x12

09bbffb8 77e6608b 059e3d10 00000000 00000000 comsvcs!DispManGetContext+0x24e

09bbffec 00000000 75bb21f1 059e3d10 00000000 kernel32!GetModuleFileNameA+0xeb

24 Id: 558.390 Suspend: 1 Teb: 7ffa5000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

0faefef4 7739cd08 00000002 0faeff1c 00000000 ntdll!KiFastSystemCallRet

0faeff50 7738e381 00000001 0faeffb0 ffffffff user32!PeekMessageW+0x244

0faeff6c 4dda6ad4 00000001 0faeffb0 00000000 user32!MsgWaitForMultipleObjects+0x1f

0faeffb8 77e6608b 00000000 00000000 00000000 GdiPlus!GdipCreateSolidFill+0x1fea

0faeffec 00000000 4dda6a7b 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

25 Id: 558.e6c Suspend: 1 Teb: 7ff3a000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1056e198 7c8302e7 05570748 1056e3cc 7c82fadf ntdll!ExpInterlockedPopEntrySListEnd+0x5

1056e1a4 7c82fadf 05570748 12ffc218 00000014 ntdll!RtlInitUnicodeStringEx+0xa0

1056e3cc 7c3416b3 05570000 00000000 00000014 ntdll!RtlAllocateHeap+0xe2

1056e40c 7c3416db 00000014 7c360947 00000014 msvcr71!_crtLCMapStringA+0x305

1056e44c 1200789d 00000014 0ebb0b68 1202d96c msvcr71!_crtLCMapStringA+0x32d

1056e474 12038153 00000001 215b9958 12ffca20 xerces_c_2_6!xercesc_2_6::XMemory::operator new+0x14

1056e5ec 12033a59 0ed76a58 00000003 12ffca20 xerces_c_2_6!xercesc_2_6::IGXMLScanner::buildAttList+0x4f0

1056e68c 12034595 1056e6b3 14f968f4 14f96878 xerces_c_2_6!xercesc_2_6::IGXMLScanner::scanStartTagNS+0xa9d

1056e6c4 12034800 0f626520 14f96878 00000000 xerces_c_2_6!xercesc_2_6::IGXMLScanner::scanContent+0xbf

1056e6f0 12045dfb 0f626520 14f96878 0ea936b0 xerces_c_2_6!xercesc_2_6::IGXMLScanner::scanDocument+0x5b

1056e76c 12045f01 0f626520 13539238 0eadbef8 xerces_c_2_6!xercesc_2_6::XMLScanner::scanDocument+0x143

1056e794 1205192b 0f6264d0 13539238 0000003e xerces_c_2_6!xercesc_2_6::XMLScanner::scanDocument+0x36

1056e7d8 05c0fe73 0f6264d0 1056ebbc 13539238 xerces_c_2_6!xercesc_2_6::AbstractDOMParser::parse+0x53

1056eb5c 05c1726d 1056eb98 01ce330e 1cfa8d70 GeoCalc!GeoCalc::DB::CDataSource::LoadDOM+0x163

1056eba8 79f98584 1e3b6415 00000010 b59aaf96 GeoCalc!GeoCalc::DB::CDataSource::LoadFile+0x1d

1056ec34 1e3b51d8 00000000 1056ecb8 1e3b511c mscorwks!DllCanUnloadNowInternal+0x4cc8

1056ec60 1e3b511c 155cec40 1cfa8670 1c91b07c 0x1e3b51d8

1056ecb8 1e3b278c 032ddc40 1c918904 1c918900 0x1e3b511c

1056ed6c 1930c442 155cec40 00000000 1c88e2d0 0x1e3b278c

1056edb4 1930c248 1556d8c0 155cec40 00000000 0x1930c442

26 Id: 558.78c Suspend: 1 Teb: 7ff36000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

197efba8 79f2f30a 00000228 197efbec 197efbe8 ntdll!KiFastSystemCallRet

197efc14 79ecb00b 00000000 00000000 197efcb8 mscorwks!CreateAssemblyCache+0x2125c

00000000 00000000 00000000 00000000 00000000 mscorwks!CreateApplicationContext+0xc4a7

27 Id: 558.d0 Suspend: 1 Teb: 7ff38000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1954ff84 77c5778f 1954ffac 77c5f7dd 000a56e8 ntdll!KiFastSystemCallRet

1954ff8c 77c5f7dd 000a56e8 00000000 00000000 rpcrt4!NdrOleFree+0x3c5

1954ffac 77c5de88 0008fdc0 1954ffec 77e6608b rpcrt4!I_RpcTransGetThreadEvent+0x188

1954ffb8 77e6608b 00162c38 00000000 00000000 rpcrt4!I_RpcLogEvent+0xe92

1954ffec 00000000 77c5de6d 00162c38 00000000 kernel32!GetModuleFileNameA+0xeb

28 Id: 558.f38 Suspend: 1 Teb: 7ff3d000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1b6eec94 01ce7d2f 1c9bae8c 00000000 00000000 ntdll!KiFastSystemCallRet

1b6eecbc 1d870428 1c9bae54 1c9bae88 00000000 0x1ce7d2f

1b6eecdc 1d870428 00000000 00000000 1b6eed2c vjslib_ni+0x20428

1b6eecf8 1d97a03e 00000000 00000000 1c9bae54 vjslib_ni+0x20428

1b6eed2c 1d8ea1d0 01ce7022 1b6ef19c b59aaf96 vjslib_ni+0x12a03e

1b6eed48 793d7a7b 00000000 1c9b8a7c 1b6eedac vjslib_ni+0x9a1d0

1b6eed80 79e88f63 00000000 00000000 1b6eee10 mscorlib_ni+0x317a7b

1b6eed90 79e88ee4 1b6eee60 00000000 1b6eee30 mscorwks!LogHelp_TerminateOnAssert+0x2f13

1b6eee10 79e88e31 1b6eee60 00000000 1b6eee30 mscorwks!LogHelp_TerminateOnAssert+0x2e94

1b6eef50 79e88d19 796902ac 1b6ef094 1b6eef9c mscorwks!LogHelp_TerminateOnAssert+0x2de1

1b6ef044 79e88805 79e816f7 1b6ef094 79e88888 mscorwks!LogHelp_TerminateOnAssert+0x2cc9

1b6ef048 79e816f7 1b6ef094 79e88888 1b6ef094 mscorwks!LogHelp_TerminateOnAssert+0x27b5

1b6ef050 79e88888 1b6ef094 79e88a0d 00000004 mscorwks!InstallCustomModule+0x2187

1b6ef148 79ef7fde 1b6ef1dc aeff2a6f 1b85100c mscorwks!LogHelp_TerminateOnAssert+0x2838

1b6ef190 79ef7f1e b59aaf96 79e72048 1b6ef454 mscorwks!IEE+0x20a92

1b6ef1f8 793684fb 1b6ef19c 1c9b8a7c 02932c28 mscorwks!IEE+0x209d2

1b6ef210 793683ee 153629bc 1b6ef240 1b6ef26c mscorlib_ni+0x2a84fb

1b6ef228 793d7b5c 1c9b8a7c 00000000 108e8770 mscorlib_ni+0x2a83ee

1b6ef240 79e88f63 00000000 00000000 1b6ef2d0 mscorlib_ni+0x317b5c

1b6ef250 79e88ee4 1b6ef320 00000000 1b6ef2f0 mscorwks!LogHelp_TerminateOnAssert+0x2f13

29 Id: 558.904 Suspend: 1 Teb: 7ff37000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1b79fb14 71b23a52 000014f0 000014f4 00000000 ntdll!KiFastSystemCallRet

1b79fc04 71c0470c 00000001 1b79fe84 1b79fc7c mswsock+0x3a52

1b79fc54 77215d7a 00000001 1b79fe84 1b79fc7c ws2_32!select+0xa1

1b79ffb0 7721d925 1b79ffec 77e6608b 10ac89d0 wininet!InternetCanonicalizeUrlW+0x191

1b79ffb8 77e6608b 10ac89d0 00000000 00000000 wininet!UnlockUrlCacheEntryFileA+0x31c

1b79ffec 00000000 7721d918 10ac89d0 00000000 kernel32!GetModuleFileNameA+0xeb

30 Id: 558.f48 Suspend: 1 Teb: 7ff35000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1b7dffb8 77e6608b 71b268c0 00000000 00000000 ntdll!KiFastSystemCallRet

1b7dffec 00000000 71b23e4b 10adebc8 00000000 kernel32!GetModuleFileNameA+0xeb

31 Id: 558.de8 Suspend: 1 Teb: 7ff34000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e1affb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e1affec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

32 Id: 558.b60 Suspend: 1 Teb: 7ffa1000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

192aff7c 77e424c1 0000ea60 00000000 192affb8 ntdll!KiFastSystemCallRet

192aff8c 776b22a0 0000ea60 10adb0d8 776b2307 kernel32!Sleep+0xf

192affb8 77e6608b 10adb0d8 00000000 00000000 ole32!IsValidInterface+0x474

192affec 00000000 776b2354 10adb0d8 00000000 kernel32!GetModuleFileNameA+0xeb

33 Id: 558.348 Suspend: 1 Teb: 7ffde000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e20ff90 761ba048 00000001 10b88190 00000000 ntdll!KiFastSystemCallRet

1e20ffb8 77e6608b 00000001 00000000 00000000 crypt32!RegSetValueExU+0x2b9

1e20ffec 00000000 761ba01d 10b88188 00000000 kernel32!GetModuleFileNameA+0xeb

34 Id: 558.d24 Suspend: 1 Teb: 7ffd9000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e42ffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e42ffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

35 Id: 558.fc4 Suspend: 1 Teb: 7ff3e000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e46ffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e46ffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

36 Id: 558.fcc Suspend: 1 Teb: 7ff3c000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e4affb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e4affec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

37 Id: 558.470 Suspend: 1 Teb: 7ff3b000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e4effb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e4effec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

38 Id: 558.c64 Suspend: 1 Teb: 7ff39000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e52ffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e52ffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

39 Id: 558.12c Suspend: 1 Teb: 7ff33000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

1e56ffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

1e56ffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

40 Id: 558.27c Suspend: 1 Teb: 7ff32000 Unfrozen

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

23b4ffb8 77e6608b 00000000 00000000 00000000 ntdll!KiFastSystemCallRet

23b4ffec 00000000 7c83ad38 00000000 00000000 kernel32!GetModuleFileNameA+0xeb

0:014> ~* e !clrstack

OS Thread Id: 0x55c (0)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5ac (1)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5c8 (2)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5dc (3)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5e0 (4)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5e4 (5)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5e8 (6)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5f0 (7)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5f4 (8)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x5fc (9)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x604 (10)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x554 (11)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x1ec (12)

Failed to start stack walk: 80004005

OS Thread Id: 0x208 (13)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x620 (14)

ESP EIP

019dfa8c 77e55e02 [GCFrame: 019dfa8c]

019dfaf4 77e55e02 [GCFrame: 019dfaf4]

OS Thread Id: 0x624 (15)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x630 (16)

Failed to start stack walk: 80004005

OS Thread Id: 0x880 (17)

Failed to start stack walk: 80004005

OS Thread Id: 0x884 (18)

Failed to start stack walk: 80004005

OS Thread Id: 0xce0 (19)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x7c4 (20)

Failed to start stack walk: 80004005

OS Thread Id: 0x9c0 (21)

Failed to start stack walk: 80004005

OS Thread Id: 0x2d8 (22)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xb34 (23)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x390 (24)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xe6c (25)

ESP EIP

1056eb98 7c8224b9 [NDirectMethodFrameStandalone: 1056eb98] <Module>.GeoCalc.DB.CDataSource.LoadFile(GeoCalc.DB.CDataSource*, UInt16*)

1056eba8 1e3b645c GeoCalcNET.DataSourceComponent.LoadFile(System.String)

1056ec3c 1e3b51d8 BMGCoordinateTransformerProvider.BMGCoordinateTransformer.LoadDataSource(System.String, LoggingFramework.ILog)

1056ec6c 1e3b511c BMGCoordinateTransformerProvider.BMGCoordinateTransformer.Initialize(CoreFramework.IPropertySet, System.String, LoggingFramework.ILog)

1056ec80 1e3b2d58 MappingFramework.Utils.MFUtils.LoadProjectionSystem(System.String, System.Xml.XmlNode, XMLFramework.DocParser, LoggingFramework.ILog, Boolean, Boolean, MappingFramework.Projections.CoordSysLookup ByRef, MappingFramework.Projections.DatumTransformationLookup ByRef, MappingFramework.Projections.ICoordinateTransformer ByRef)

1056ecdc 1e3b278c OnPointFramework.Application.Component.MapComponent.LoadProjectionSystem(OnPointFramework.Application.AppConfiguration, LicenseUtils.LicenseContext, Boolean)

1056ed14 1e3b2530 OnPointFramework.Application.Component.MapComponent.Configure(System.Xml.XmlNode, LicenseUtils.LicenseContext, OnPointFramework.Application.AppConfiguration)

1056ed30 1930df1e OnPointFramework.Application.AppManager.LoadComponent(System.Xml.XmlNode, System.Xml.XmlNode, XMLFramework.DocParser, System.Xml.XmlNode, OnPointFramework.Application.AppConfiguration, Boolean, LoggingFramework.ILog)

1056ed88 1930c442 OnPointFramework.Application.AppManager.LoadComponents(OnPointFramework.Application.AppConfiguration ByRef, XMLFramework.DocParser, XMLFramework.DocParser, Boolean, LoggingFramework.ILog, System.Web.Security.MembershipProvider)

1056edcc 1930c248 OnPointFramework.Application.AppManager.LoadComponents(OnPointFramework.Application.AppConfiguration ByRef, System.String, System.String, LoggingFramework.ILog, System.Web.Security.MembershipProvider)

1056edec 19309480 AppUtils.GetNewConfiguration(System.Web.HttpContext, System.Web.Security.MembershipProvider)

1056eeb4 193000d8 ASP.global_asax.Application_Start(System.Object, System.EventArgs)

1056f188 79e88f63 [CustomGCFrame: 1056f188]

1056f16c 79e88f63 [GCFrame: 1056f16c]

1056f150 79e88f63 [GCFrame: 1056f150]

1056f358 79e88f63 [HelperMethodFrame_1OBJ: 1056f358] System.RuntimeMethodHandle._InvokeMethodFast(System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeTypeHandle)

1056f3c8 793cf629 System.RuntimeMethodHandle.InvokeMethodFast(System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeTypeHandle)

1056f414 794012bf System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)

1056f450 7940114a System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)

1056f470 65fe8494 System.Web.HttpApplication.ProcessSpecialRequest(System.Web.HttpContext, System.Reflection.MethodInfo, Int32, System.Object, System.EventArgs, System.Web.SessionState.HttpSessionState)

1056f4c0 66306638 System.Web.HttpApplicationFactory.FireApplicationOnStart(System.Web.HttpContext)

1056f4d0 65fc3f76 System.Web.HttpApplicationFactory.EnsureAppStartCalled(System.Web.HttpContext)

1056f504 65fc3d38 System.Web.HttpApplicationFactory.GetApplicationInstance(System.Web.HttpContext)

1056f510 65fbe1ee System.Web.HttpRuntime.ProcessRequestInternal(System.Web.HttpWorkerRequest)

1056f544 65fbde92 System.Web.HttpRuntime.ProcessRequestNoDemand(System.Web.HttpWorkerRequest)

1056f550 65fbc567 System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr, Int32)

1056f700 79f1ef33 [ContextTransitionFrame: 1056f700]

1056f750 79f1ef33 [GCFrame: 1056f750]

1056f8a8 79f1ef33 [ComMethodFrame: 1056f8a8]

OS Thread Id: 0x78c (26)

Failed to start stack walk: 80004005

OS Thread Id: 0xd0 (27)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xf38 (28)

ESP EIP

1b6eecd4 7c82ed54 [NDirectMethodFrameStandalone: 1b6eecd4] com.ms.vjsharp.windowing.win32.UnsafeWin32Calls.intGetMessage<PInvokeHelper>vjsnativ(MSGHelper, Int32, Int32, Int32)

1b6eecec 1d870428 com.ms.vjsharp.windowing.win32.UnsafeWin32Calls.intGetMessage(com.ms.vjsharp.win32.MSG, Int32, Int32, Int32)

1b6eed08 1d97a03e com.ms.vjsharp.windowing.win32.Win32Toolkit.run()

1b6eed34 1d8ea1d0 java.lang.Thread.run()

1b6eed60 01ce7022 [MulticastFrame: 1b6eed60] System.Threading.ThreadStart.Invoke()

1b6eed70 793d7a7b System.Threading.ThreadHelper.ThreadStart_Context(System.Object)

1b6eed78 793685af System.Threading.ExecutionContext.runTryCode(System.Object)

1b6ef19c 79e88f63 [HelperMethodFrame_PROTECTOBJ: 1b6ef19c] System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)

1b6ef204 793684fb System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

1b6ef21c 793683ee System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

1b6ef234 793d7b5c System.Threading.ThreadHelper.ThreadStart()

1b6ef454 79e88f63 [GCFrame: 1b6ef454]

1b6ef758 79e88f63 [ContextTransitionFrame: 1b6ef758]

OS Thread Id: 0x904 (29)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xf48 (30)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xde8 (31)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xb60 (32)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x348 (33)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xd24 (34)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xfc4 (35)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xfcc (36)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x470 (37)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0xc64 (38)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x12c (39)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

OS Thread Id: 0x27c (40)

Unable to walk the managed stack. The current thread is likely not a

managed thread. You can run !threads to get a list of managed threads in

the process

Do correct if i am wrong? If yes, then i can report the error to third party component provider.

In between where can i find the list of command which can be run of Windbg ( i tried googling and going thru the help but was not successful)?

Thanks in advance

-Manche

Still looking at my tummy

Yoda's Blog — Fri, 27 Apr 2007 06:09:16 GMT

Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Fábio Batista — Sun, 03 Jun 2007 06:59:19 GMT

Very instructive post, thank you!

I have a crash to Manche's (don't worry, I won't post a comment that size here :)). It's also related to a third-party component, developed in J#. The presence of com.ms.vjsharp.windowing.win32.Win32Toolkit.run() in the call stack is the part that scares me.

There might be some problem related to VJ# exception handling. Looks like it's trying to report the exception to a win32 window, or something like that.

I'm debugging the crash. In Visual Studio, it shows, on the call stack of the offending thread:

[Managed to Native Transition]

> vjslib.dll!com.ms.vjsharp.windowing.win32.Win32Toolkit.run() + 0x52 bytes

vjslib.dll!java.lang.Thread.run() + 0x10 bytes

[Native to Managed Transition]

[Managed to Native Transition]

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x3b bytes

mscorlib.dll!System.Threading.ExecutionContext.runTryCode(object userData) + 0x43 bytes

[Native to Managed Transition]

[Managed to Native Transition]

mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0xa7 bytes

mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x92 bytes

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40 bytes

[Appdomain Transition]

top 10 windbg.exe usage articles

roy ashbrook — Mon, 25 Jun 2007 00:10:02 GMT

These are the articles (in no particular order) that I felt best showed a thorough use of the windbg

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Brad — Fri, 10 Aug 2007 09:48:13 GMT

I cannot use a debugger to troubleshoot the issue in this case. The HttpModule you referred to works for a ASP.NET app.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Neil — Tue, 09 Oct 2007 18:45:05 GMT

Hi Tess,

Was hoping if you can give us some direction to look towards based on this output we got from windbg.

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(ec.117c): CLR exception - code e0434f4d (first/second chance not available)

eax=1bd7f64c ebx=1b1352d8 ecx=00000000 edx=00000024 esi=1bd7f6d8 edi=e0434f4d

eip=77e4bee7 esp=1bd7f648 ebp=1bd7f69c iopl=0 nv up ei pl nz na po nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202

kernel32!RaiseException+0x53:

77e4bee7 5e pop esi

0:033> !anlyze -v

No export anlyze found

0:033> !analyze -v

*******************************************************************************

* *

* Exception Analysis *

* *

*******************************************************************************

*** WARNING: Unable to verify checksum for System.Web.ni.dll

*** WARNING: Unable to verify checksum for mscorlib.ni.dll

*** WARNING: Unable to verify checksum for System.ni.dll

FAULTING_IP:

kernel32!RaiseException+53

77e4bee7 5e pop esi

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)

ExceptionAddress: 77e4bee7 (kernel32!RaiseException+0x00000053)

ExceptionCode: e0434f4d (CLR exception)

ExceptionFlags: 00000001

NumberParameters: 1

Parameter[0]: 80131509

DEFAULT_BUCKET_ID: CLR_EXCEPTION

PROCESS_NAME: w3wp.exe

ERROR_CODE: (NTSTATUS) 0xe0434f4d - <Unable to get error code text>

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

MANAGED_STACK:

ChildEBP RetAddr Caller,Callee

EXCEPTION_OBJECT: !pe 28098d0

Exception object: 028098d0

Exception type: System.Net.WebException

Message: The operation has timed out

InnerException: <none>

StackTrace (generated):

<none>

StackTraceString: <none>

HResult: 80131509

MANAGED_OBJECT: !dumpobj 280c0d00280aba4

Name: System.String

MethodTable: 790f9244

EEClass: 790f91a4

Size: 72(0x48) bytes

(C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll)

String: The operation has timed out

Fields:

MT Field Offset Type VT Attr Value Name

790fdb60 4000096 4 System.Int32 0 instance 28 m_arrayLength

790fdb60 4000097 8 System.Int32 0 instance 27 m_stringLength

790fad38 4000098 c System.Char 0 instance 54 m_firstChar

790f9244 4000099 10 System.String 0 shared static Empty

>> Domain:Value 000dfa00:790d57b4 00117138:790d57b4 <<

79122994 400009a 14 System.Char[] 0 shared static WhitespaceChars

>> Domain:Value 000dfa00:027203f0 00117138:027244a4 <<

EXCEPTION_MESSAGE: The operation has timed out

LAST_CONTROL_TRANSFER: from 79f55b05 to 77e4bee7

STACK_TEXT:

1bd7f69c 79f55b05 e0434f4d 00000001 00000001 kernel32!RaiseException+0x53

1bd7f6fc 7a056a79 028098d0 00000000 00000000 mscorwks!RaiseTheExceptionInternalOnly+0x226

1bd7f710 7a056af2 028098d0 00000000 1bd7f828 mscorwks!RaiseTheException+0x4d

1bd7f738 7a056b30 00000000 1b1352d8 db9b9274 mscorwks!RaiseTheException+0xbf

1bd7f764 7a056b41 028098d0 00000000 7a0e38fa mscorwks!RealCOMPlusThrow+0x38

1bd7f770 7a0e38fa 028098d0 1e66c88c 7a36f194 mscorwks!RealCOMPlusThrow+0xb

1bd7f8a0 7a0e4b97 00000000 1bd7f8d8 1bd7f948 mscorwks!Thread::RaiseCrossContextException+0x3ac

1bd7f954 7a0e5a07 00000002 79f5e3aa 1bd7fa48 mscorwks!Thread::DoADCallBack+0x26c

1bd7f96c 79ed89ca 1bd7fa48 1bd7f9f4 79f55262 mscorwks!Thread::UserResumeThread+0xe1

1bd7fa00 79ed88f1 1bd7fa48 1e66ca84 00000001 mscorwks!Thread::DoADCallBack+0x355

1bd7fa3c 7a0e4d96 1bd7fa48 00000002 00000000 mscorwks!Thread::DoADCallBack+0x541

1bd7fa64 7a0e4dad 00000002 7a078575 1bd7fad0 mscorwks!Thread::DoADCallBack+0x575

1bd7fa78 7a07a99e 00000002 7a078575 1bd7fad0 mscorwks!ManagedThreadBase::KickOff+0x13

1bd7fb14 79ed8e36 1b174e60 1bd7fb50 00000000 mscorwks!ThreadNative::KickOffThread+0x230

1bd7ffb8 77e64829 1b16d2a0 00000000 00000000 mscorwks!Thread::intermediateThreadProc+0x49

1bd7ffec 00000000 79ed8df0 1b16d2a0 00000000 kernel32!BaseThreadStart+0x34

FOLLOWUP_IP:

mscorwks!RaiseTheExceptionInternalOnly+226

79f55b05 c745fcfeffffff mov dword ptr [ebp-4],0FFFFFFFEh

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mscorwks

IMAGE_NAME: mscorwks.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 461f2e2a

FAULTING_THREAD: 0000117c

PRIMARY_PROBLEM_CLASS: CLR_EXCEPTION

BUGCHECK_STR: APPLICATION_FAULT_CLR_EXCEPTION

SYMBOL_NAME: mscorwks!RaiseTheExceptionInternalOnly+226

STACK_COMMAND: ~33s; .ecxr ; kb

FAILURE_BUCKET_ID: APPLICATION_FAULT_CLR_EXCEPTION_System.Net.WebException_mscorwks!RaiseTheExceptionInternalOnly+226

BUCKET_ID: APPLICATION_FAULT_CLR_EXCEPTION_System.Net.WebException_mscorwks!RaiseTheExceptionInternalOnly+226

Followup: MachineOwner

---------

Thanks,

Neil

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Wed, 10 Oct 2007 14:27:16 GMT

I would start of with !clrstack on the current thread (the one that throws the exception) and ~* e !clrstack to see what all threads are doing to get an idea of why its timing out.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Ben Wagenaar — Wed, 17 Oct 2007 18:36:42 GMT

Hi Tess,

Great article! Just one thing - you mention the following when creating Microsoft's UnhandledExceptionModule.dll from their KB article:

"You don’t actually need to strong name it and add it to the GAC, however if you plan it in multiple applications you should to avoid for the dll being loaded multiple times."

I've produced this DLL and using the instructions on Microsoft's article, it installs correctly in the GAC via my development PC, but in our UAT and Production systems here, we don't have these tools to complete it. I can add it successfully to the GAC for .NET 2.0 components, but the web.config reference throws an error saying that the "codebase cannot be found".

My question is, how would I install this DLL into my web app to enable unhandled exceptions to be caught?

Thanks in advance,

Ben

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Thu, 18 Oct 2007 10:31:22 GMT

Hi Ben,

Sounds like it is not matching up the right version/key in the GAC. Is that the exact message you get (i.e. "codebase cannot be found")?

You might want to read through this regarding how the probing is done as it might help you figure out why it fails.

http://en.csharp-online.net/.NET_CLR_Components%E2%80%94Resolving_Names_to_Locations

On a separate note, although it is best practice to store it in the GAC and i wouldn't recommend creating copies in the bin directory for all dlls, this dll is extremely small so removing the strong name and storing this one in the GAC wont really cause any noticeable memory changes, assuming that you dont have hundreds of different applications.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Ben Wagenaar — Thu, 18 Oct 2007 10:58:00 GMT

Thanks Tess - you're right, the "codebase cannot be found" message is the one I see.

How could I add this to the GAC (without a strong name) and reference it in my web.config file, inside the httpModules tag? This entry appears to require a strong name and this is where my error message originates from.

Apologies for all the questions - although I've been coding in .NET for a while, I've had little experience in deploying these apps.

Thanks again,

Ben

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Thu, 18 Oct 2007 11:08:47 GMT

To my knowledge you cant add an assembly that is not strongnamed to the GAC so if it is not strong named it would have to reside in the bin.

If someone knows differently, please correct me:)

ASP.NET Crash: System.Security.Cryptography.CryptographicException

If broken it is, fix it you should — Wed, 31 Oct 2007 17:20:11 GMT

This has been a busy month for blogging for me, I'm up to a whopping 8 posts this month including this

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

enrique.prados@a-e.es — Wed, 14 Nov 2007 10:58:41 GMT

Hi misters,

is it possible use AppDomain.Currentdomain. UnhandledException event en ASP.NET 2.0 ??

I have this code:

protected override void OnInit(EventArgs e)

{

base.OnInit(e);

PantallaControlIULogging.TrazarDebug("Principal. OnInit.");

PantallaControlIULogging.TrazarWarning("Principal. CurrentDomain_UnhandledException. ");

AppDomain.CurrentDomain.UnhandledException -= new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

}

and

protected void Page_Load(object sender, EventArgs e)

{

PantallaControlIULogging.TrazarWarning("Principal. CurrentDomain_UnhandledException. ");

AppDomain.CurrentDomain.UnhandledException -= new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

...

I don't get fire that event when throw an error

protected void b2click(object sender, EventArgs e)

{

// Forzar error

throw new

Excepciones.BloqueoTareaExcepcion("ERROR BloqueoTareaExcepcion!!!");

I want to get the error and show it using javascript (alert).

By other reasons, I cannot access to global.asax and I cannot use HttpApplication_Error event.

Any help will be appreciated, and I'll be very grateful. Thanks in advance.

Greetings, regards.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Lee — Thu, 15 Nov 2007 03:00:06 GMT

Thank you, thank you, thank you, thank you. This helped me solve a major roadblock at work.

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Daniel — Wed, 02 Apr 2008 16:51:09 GMT

wow. finally an easy to understand walkthrough on debugging! What I like is that it's not just the fix but the process of determining what caused the error in the first place and what all the little bits mean.

Thank you very much!

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

mattc — Thu, 17 Apr 2008 06:06:59 GMT

hey Tess

I have this problem so am looking to implement your handler..

I built it OK..

I actually moved the dll to a development web server and registered it in the GAC etc fine.

Except when I run the web app I get an error.

"The given assembly name or codebase was invalid. "

This is what I have in my web.config:

</httpModules>

any help greatly appreciated, I'm sure it will help once I get it working!

Matt

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Thu, 17 Apr 2008 10:14:26 GMT

It looks right assuming that the strong name is correct, except for that the name should probably be UnhandledExceptionModule rather than UnhandledExceptionMonitor unless you changed the name, in which case it should probably also be changed in the type

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

matt — Wed, 23 Apr 2008 00:24:59 GMT

Hi Tess.

hmm was getting tired! Changed that but still doesn't work. I will have another look at it.

assuming once I've compiled the dll I can move it between machines, thats not the problem..?

Thanks, Matt

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Andras Vass — Sat, 03 May 2008 00:16:13 GMT

Thank you, this article was very useful.

I had the same issues carrying out the KB instructions on a production system as Ben Wagenaar mentioned in a previous comment.

More about this on:

http://andrasvass.blogspot.com/2008/05/aspnet-20-unhandled-exceptions-aka.html

I ended up creating installers for the module - you can find them on Codeplex:

https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=unhandledexception

Perhaps it may help Matt solve his deployment problems (if he hasn't already...)

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

TSW — Fri, 30 May 2008 22:39:58 GMT

Matt, I had the same problem as you. The issue (aside from what Tess mentioned), you're not forming the strong name correctly. You have:

type="WebMonitor.UnhandledExceptionModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b30ebd417a518934, processorArchitecture=MSIL"

What you want is this:

type="WebMonitor.UnhandledExceptionModule, UnhandledExceptionModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b30ebd417a518934, processorArchitecture=MSIL"

Notice the extra "UnhandledExceptionModule, " after the initial class name...

Also, Tess, up above (http://blogs.msdn.com/tess/archive/2006/04/27/asp-net-2-0-crash-case-study-unhandled-exceptions.aspx#1081135) Howard brings up a potentially good point. Is he right?

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Deniz — Fri, 05 Dec 2008 18:07:34 GMT

I received this error while coding a shared office Add-In. I had put some code in the Finalize-Method. Moving the code to the applications "close" event helped.

Lesson learned: Don't mess around with finalize if you dont have to!

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Abhishek — Fri, 12 Dec 2008 09:02:00 GMT

Just one word to describe my thoughts on this article...Enlightened :)

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

JanIvan Qian — Mon, 29 Dec 2008 12:18:16 GMT

Hi Tess, it's really a good post for debuging crash. The two methods are both practical. Thanks very much for your great tech and expirence. Thanks for sharing! I'm your fan now :)

Keep moving!

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

i.nconspicuo.us — Fri, 16 Jan 2009 00:53:13 GMT

I get this error only when running the application through Task Scheduler. If I start the application manually, it runs fine. WTF???

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Tess — Fri, 16 Jan 2009 10:20:43 GMT

could be a lot of things, like running in a different user context etc.

I would just get a dump and see what the exception is if you dont get that already from the eventlog entry, and from that try to figure out why it happens.

Something is obviously different when you run it in task scheduler vs. manually

How to Handle .NET Unhandled Exceptions Gracefully

Half Blood Programmer, MSFT Chapter — Mon, 09 Feb 2009 09:18:31 GMT

I know there were already lots of discussions about this topic, but as a .NET developer and support engineer,

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Sergey P. — Sat, 14 Feb 2009 02:58:51 GMT

Thanks! Your article helped me a lot!

How to Handle .NET Unhandled Exceptions Gracefully

Half Blood Programmer, MSFT Chapter — Tue, 28 Apr 2009 10:11:04 GMT

I know there were already lots of discussions about this topic, but as a .NET developer and support engineer,

re: ASP.NET 2.0 Crash case study: Unhandled exceptions

Red Dog — Sun, 26 Jul 2009 18:47:45 GMT

OK, got the error message on a laptop and I've read all of the above. My question(s) is... What does any of it mean? Can't I just re-install summink to get rid of the error?