What on earth caused my process to crash?

re: What on earth caused my process to crash?

Prasanna — Thu, 19 Feb 2009 15:50:29 GMT

I too get the same error

0:025> !threadpool

Failed to find runtime DLL (mscorwks.dll), 0x80004005

Extension commands need mscorwks.dll in order to have something to do.

Can you please provide a solution for this.

BTW, I'm trying to get the minidump of ASP.NET 2.0 application.

re: What on earth caused my process to crash?

Tess1 — Thu, 18 Oct 2007 16:54:29 GMT

addendum to last comment:)

try lmvm mscorwks to see if mscorwks.dll is loaded

you can also try lmvm mscor* to see what mscor dlls are loaded and what versions

re: What on earth caused my process to crash?

Tess1 — Thu, 18 Oct 2007 16:53:37 GMT

Sounds like you are either debugging an application that is not managed (.net) or that hasnt yet loaded mscorwks.dll alternatively that it is an 1.1 app and youre trying to debug with 2.0 sos

re: What on earth caused my process to crash?

Ravi — Thu, 18 Oct 2007 15:36:52 GMT

I get the following message when ever i try to do any thing after i load sos.dll

"Failed to find runtime DLL (mscorwks.dll), 0x80004005

Extension commands need mscorwks.dll in order to have something to do."

following is what i did,

1. Load a crash dump

2. .load c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\SOS.dll

3. !threads

"c:\dumps\" is the folder from where i loaded the crash dumps

"C:\Program Files\Debugging Tools for Windows\" is where the debugger is installed

re: What on earth caused my process to crash?

Tess1 — Tue, 04 Apr 2006 10:57:29 GMT

I have taken the liberty to change this post sligthly, renaming the GC Holes section to Managed Heap Corruption which is more correct.

Thanks to Rico (http://blogs.msdn.com/ricom) for pointing this out...

re: What on earth caused my process to crash?

Tess1 — Fri, 10 Feb 2006 10:04:54 GMT

Thanks for commenting on that John, I've changed it now...

That's what you get for trying to typ faster than the brain can manage:)

re: What on earth caused my process to crash?

John M. Dlugosz — Thu, 09 Feb 2006 23:35:56 GMT

"Fatal Excecution Engine" is a typo. I really don't care, but it won't show up in Google if one searches for "Fatal Execution Engine", and this page is well worth finding.

re: What on earth caused my process to crash?

Tess1 — Tue, 07 Feb 2006 16:28:10 GMT

Take a look at the log file that gets created in the hang or crash directory, somewhere near the bottom you should have an error message telling you the reason that it exited.

The most likely cause is that you don't have permissions to debug the process, i.e. that you are not an admin or otherwise priviledged to debug the process.

Another likely cause is that you are trying to debug in crash mode on a win2000 machine through terminal services. This will not work as you are not logged in to the same windows session as the service you are debugging. (non invasive i.e. hang mode works still because it doesnt actually break in to the process)

If this is the case, the easiest way to deal with it if possible is to log on to the actual machine. If that is not possible you have to follow the steps in this article to run in crash mode remotely

http://support.microsoft.com/default.aspx?scid=kb;en-us;286350#XSLTH4369121123120121120120

Hope this takes you closer to debugging your crash...

re: What on earth caused my process to crash?

RichB — Tue, 07 Feb 2006 16:14:45 GMT

Well, I have ASP.Net v2 crashing. So I'm trying to follow your instructions to debug it, but fail at the first hurdle. adplus says it has attached to aspnet_wp.exe, but then immediately exits and I get zero minimized command shells.

It's always annoying when you have to debug the debugger before you can debug the platform.

A .NET Crash: How not to write a global exception handler

If broken it is, fix it you should — Mon, 06 Feb 2006 14:29:44 GMT

I’ve written quite a few posts on memory issues because that is the type of problem we get most frequently...