The FatalExecutionError managed debugging assistant (MDA) is activated when a fatal error in the common language runtime (CLR) has been detected. The process will be terminated.
Unexpected process termination. Other symptoms cannot be determined because a CLR failure can occur for a variety of reasons.
The CLR has been fatally corrupted. This is most often caused by data corruption, which can be caused by a number of problems, such as calls to malformed platform invoke functions and passing invalid data to the CLR.
Enabling additional MDAs might help identify the problem. The following MDAs can be particularly helpful in diagnosing the issue:
InvalidOverlappedToPInvoke
OverlappedFreeError
PInvokeStackImbalance
GcUnmanagedToManaged
GcManagedToUnmanaged
CallbackOnCollectedDelegate
ReportAVOnComRelease
InvalidVariant
InvalidIUnknownPointer
RaceOnRCWCleanup
InvalidFunctionPointerInDelegate
InvalidGCHandleCookie
This MDA has no effect on the runtime's behavior.
The address of the CLR function that caused the fatal error, the ID of the thread where the error occurred, and the error code.
<mdaConfig> <assistants> <fatalExecutionError /> </assistants> </mdaConfig>
<fatalExecutionEngineError/>