Best thing- obtain a mini-dump and we will analyze it (as long as you have captured the second-chance exception. Please let us know by mailing email@example.com
There are a few ways to do this but we have an effective way with minimal configuration needed:
You can download a small debugger from us if you don't have Windows debugging tools:
Extract all files to a directory,
Cscript adplus.vbs -crash -pn <name of process>
If more than one process exists by the same name, you can use -P <pid> instead of -pn (work out which process number to debug using Windows Task Manager)
This then dumps files to disk on a crash. If the files are very large, I can set up an FTP account so you can upload it to us.
Or you can often see the exception by loading the dump file in windbg.exe and running "!anaylyze - v")