The following assumes your crash is one that only happens when using Bug Validator.

Here's a few scenarios in which your program might crash:

•Third party DLLs are using system wide hooks

Some DLLs from third party vendors use system wide hooks and do not interact with Bug Validator and the target program very well.

If you can identify such DLLs, prevent them being hooked by adding the DLL name to the Hooked DLLs page of the global settings dialog as in the example below.

•Third party DLLs are using global hooks

A global hook DLL from a third party vendor could be adversely affecting Bug Validator when hooking your program.

Read about handling global hooks on the Global Hooks page of the settings dialog.

Judging by multiple independent error reports, we believe there may be an incompatibility between Bug Validator and the global hooks that come with the Matrox G400 and the Matrox Millenium II PCI video cards released in the late 1990's.

•There may be a bug in Bug Validator

It happens. We've tried to make Bug Validator as robust as possible, but bugs and new scenarios do occur.

First, ensure that the crash never happens if you are not using Bug Validator.

Second, check all the suggestions above.

Then drop us a line sending details of the error and we'll try to reproduce the crash with a view to fixing any bugs found in as timely a manner as possible.

The Bug Validator Unrecoverable Error dialog is displayed when an unexpected internal error means Bug Validator cannot continue to execute.

A stack trace and register dump is shown and you can Copy to Clipboard so that the data can be sent to us with a description of the activities that caused the error.

We'll aim to fix any problems in as timely manner as possible.

The data shown in the dialog is also written to c:\users\<username>\AppData\Roaming\Software Verify\Bug Validator\bvExceptionLogUI.txt

The picture below shows a stack overflow exception report (we created the crash for this topic).

bvExceptionLogUI.txt

bvExceptionLogUI.txt details a crash in the Bug Validator user interface.

bvExceptionLog.txt

bvExceptionLog.txt details a crash in the target program that Bug Validator was monitoring. The crash may be in the target program or in Bug Validator's monitoring code.

In the event of a crash, the file c:\users\<username>\AppData\Roaming\Software Verify\Bug Validator\bvExceptionLogUI.txt contains information that identifies where Bug Validator was executing when it crashed.

The file contains a stack trace and register dump and is the same information that is displayed in the Unrecoverable Error dialog when a crash occurred.

The file contains only the data for the most recent exception.