Automatic WERFault Handling and Error Logging

We have an issue where, after making a change to one of our applications-under-test, the application is crashing on shutdown.  We understand the nature of the crash, but it is due to a third-party component, and the time frame for correcting the issue will likely take a while.

This manifests in our TestComplete runs as an error entry in the logs:

Message:  The <processname.exe> process crashed.

Additional info:

Exception code: 0xC0000005.

Process identifier (PID): xxxxx.

Dump file: <file_name>.dmp.

The inclusion of this entry is completely out of our control, as it is generated by TestComplete directly.  The Windows Error Reporting Fault Dialog is also apparently automatically handled by TestComplete as well.

Normally, this would be fine.  But as this issue is known to us, and the fix for the crash is out of our control, we simply want to downgrade the error to a warning, and perhaps trap the error directly since we know the component associated with the known crash, and could search the WERFault details for this additional information.  Any errors detected in our TestComplete logs are used to fail builds, so not having control over this logging is going to be problematic for our build pipeline.

Is there any way we can control this behavior, either to allow us to control the crash handling directly, or to change the way in which TestComplete is reporting the process crash and convert the log priority to a warning?

If there isn’t, please add an entry in your issue tracking database to indicate that a user would like this level of control.

Any information is appreciated!

Jeff