Brief introduction
CLRDBG_NOTIFICATION_EXCEPTION_CODE, is 0x0x04242420. This exception during startup path 4.0 .CLR trigger, sending a notification message to the debugger when CLR4.0 version after commissioning services. Personally I think that this should be thrown only when the debugger is attached.
Detailed description
This is actually an undocumented anomalies (CLRDBG_NOTIFICATION_exception_CODE), it is clearly a complement to the IPC protocol 4.0clr hosted debugger used. Ignore it should be completely safe.
This particular anomaly does not indicate an error, but rather CLR is trying to send a message to the debugger. The most likely scenario is that you see anomalies corresponding to start running event, which is a message indicating that CLR is initialized enough to allow the Enlightenment began to interact with the debugger. If VS managed debugging is enabled, it will understand the message and inform the commissioning personnel continue to generate these messages in the future. Of course, smart debugger does not display them as the original exception that will decode their meaning, but is updated in-house, such as "loaded with a new application domain" or "issued just created a reflection in memory The new type. " Or, if there is no managed code debugger, it will not recognize this exception in any particular case there is no particular response. If there is no response, the CLR is assumed that the debugger does not provide services for managed code, and should not send any further message (abnormality).
Abnormal filling structure
ExceptionAddress: 762819b2 (! KERNELBASE RaiseException + 0x00000062) // Throws address
ExceptionCode: 04242420 // exception code
ExceptionFlags: 00000000
NumberParameters:. 3 the number of // parameters, typically 3
Parameter [0]: 31415927 // is a constant, I do not know What do you mean
the Parameter [1]: 721a0000
the Parameter [2]: 00bef768