Help understanding crash/error

  • Thread starter Thread starter Adam Clauss
  • Start date Start date
A

Adam Clauss

We have a Windows service written in C#. As of late, it has started
crashing after running for as little as 2 minutes. I have a handler for
AppDomain.UnhandledException which does NOT get called in case (it is setup
correctly - I have seen it called in other places). The only error
information I get is from Event Viewer:

Faulting application rtmsdriversvc.exe, version 2.2.2.0, stamp 45ed8d14,
faulting module kernel32.dll, version 5.2.3790.3959, stamp 45d70ad8, debug?
0, fault address 0x0000bee7.


This... has been less than useful to me, and I have no idea what to make of
it. This is running on a Windows Server 2003 Standard box if that makes a
difference.

Any thoughts/ideas?
 
Are you doing any sort of interop, particularly, any API functions in
kernel32?
 
Not for the most part...
Many of our applications use a wrapper library written in Managed C++
(calling into an unmanaged C++ library) that performs "heartbeating" to a
monitoring application. I do not know a lot of the details of it, but I
suppose it is possible that library is making some calls that involve
kernel32.

At the same time, most of our applications use this library and this is the
only one crashing like this. These applications are all running on the same
server as well.

--
Adam Clauss

Nicholas Paldino said:
Are you doing any sort of interop, particularly, any API functions in
kernel32?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Adam Clauss said:
We have a Windows service written in C#. As of late, it has started
crashing after running for as little as 2 minutes. I have a handler for
AppDomain.UnhandledException which does NOT get called in case (it is
setup correctly - I have seen it called in other places). The only error
information I get is from Event Viewer:

Faulting application rtmsdriversvc.exe, version 2.2.2.0, stamp 45ed8d14,
faulting module kernel32.dll, version 5.2.3790.3959, stamp 45d70ad8,
debug? 0, fault address 0x0000bee7.


This... has been less than useful to me, and I have no idea what to make
of it. This is running on a Windows Server 2003 Standard box if that
makes a difference.

Any thoughts/ideas?
Click to expand...
Click to expand...
 
My guess is that it is a call into the unmanaged code somewhere (not
kernel32, but your code) which is causing the problem. Are you able to
debug from the managed code to the unmanaged code? Or rather, have you
tried?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Adam Clauss said:
Not for the most part...
Many of our applications use a wrapper library written in Managed C++
(calling into an unmanaged C++ library) that performs "heartbeating" to a
monitoring application. I do not know a lot of the details of it, but I
suppose it is possible that library is making some calls that involve
kernel32.

At the same time, most of our applications use this library and this is
the only one crashing like this. These applications are all running on
the same server as well.

--
Adam Clauss

Nicholas Paldino said:
Are you doing any sort of interop, particularly, any API functions in
kernel32?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Adam Clauss said:
We have a Windows service written in C#. As of late, it has started
crashing after running for as little as 2 minutes. I have a handler for
AppDomain.UnhandledException which does NOT get called in case (it is
setup correctly - I have seen it called in other places). The only
error information I get is from Event Viewer:

Faulting application rtmsdriversvc.exe, version 2.2.2.0, stamp 45ed8d14,
faulting module kernel32.dll, version 5.2.3790.3959, stamp 45d70ad8,
debug? 0, fault address 0x0000bee7.


This... has been less than useful to me, and I have no idea what to make
of it. This is running on a Windows Server 2003 Standard box if that
makes a difference.

Any thoughts/ideas?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top