.NET Runtime 2.0 Error Reporting - mscorwks.dll failing

  • Thread starter Thread starter Florian Doyon
  • Start date Start date
F

Florian Doyon

Hello,

I am having issues with a .net 2.0 service randomly crashing on an 8
way machine running a 32bit .net server 2k3.

The event log contains an entry indicating that there's a fault in
mscorwks.dll, no stack trace attached, no dump, no drWatson, nothing.

I just configured the system to take a crash dump, but the mean time
to failure being 32 hours, I'd like to know where to look for my crash
before it occurs again (joys of random production issues).

The app uses a 3rd party mixed-mode dll, and relies heavily on
multithreading and async I/O, so there are too many area where it may
crash.

I did notice on thing in the two eventlog entries I got, is that the
faulting addresses are always the same. I let the app ran for 2 hours
before taking a memory snapshot, but I couldn't find the offending
method.

Thanks a lot guys!
--
Here's the event log :

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 11/02/2008
Time: 03:00:08
User: N/A
Computer: LONL00180036
Description:
Faulting application myapp.exe, version 2.0.3.8617, stamp 47af2a25,
faulting module mscorwks.dll, version 2.0.50727.832, stamp 461f2e2a,
debug? 0, fault address 0x000b5fa3.
0x79F25FA3
 
Hello,

I am having issues with a .net 2.0 service randomly crashing on an 8
way machine running a 32bit .net server 2k3.

The event log contains an entry indicating that there's a fault in
mscorwks.dll, no stack trace attached, no dump, no drWatson, nothing.

I just configured the system to take a crash dump,  but the mean time
to failure being 32 hours, I'd like to know where to look for my crash
before it occurs again (joys of random production issues).

The app uses a 3rd party mixed-mode dll, and relies heavily on
multithreading and async I/O, so there are too many area where it may
crash.

I did notice on thing in the two eventlog entries I got, is that the
faulting addresses are always the same. I let the app ran for 2 hours
before taking a memory snapshot, but I couldn't find the offending
method.

Thanks a lot guys!
--
Here's the event log :

Event Type:     Error
Event Source:   .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID:       1000
Date:           11/02/2008
Time:           03:00:08
User:           N/A
Computer:       LONL00180036
Description:
Faulting application myapp.exe, version 2.0.3.8617, stamp 47af2a25,
faulting module mscorwks.dll, version 2.0.50727.832, stamp 461f2e2a,
debug? 0, fault address 0x000b5fa3.
0x79F25FA3
Click to expand...

enable JIT http://msdn2.microsoft.com/en-us/library/2ac5yxx6(VS.80).aspx
and live debug it.
 
Back
Top