There are a couple of programs from Microsoft that monitor a program's activity as it runs. One of them might give you a clue; for example it might turn out that a certain DLL is used right before each crash.
The tools are:
Process Monitorhttp://technet.microsoft.com/en-us/sysi ... s/bb896645
Process Explorerhttp://technet.microsoft.com/en-us/sysi ... s/bb896653
The best thing, of course is to get the DipTrace developers to duplicate the problem. This may not be easy; I have been using DipTrace for months and have had exactly one crash on an early beta (Win XP).
Having to restart windows is an interesting clue. Does task manager show anything running before you try and fail to restart that isn't running after a reboot? If so, does killing that process allow a restart without rebooting?
Another thing you might try: run DipTrace under Linux using WINE. Does the problem go away? Does it still crash but with a better error message? Does the WINE Debugger ( http://www.winehq.org/docs/winedev-guide/wine-debugger
) tell you anything interesting?
-- 30 Oct 2011, 12:01 --
Two other things that might be worth a mention.
First, DipTrace is always quite responsive to bug reports, but they don't work on weekends, so you may get an official response sometime on Monday.
Second, if you do decide to test it on WINE, please report your experiences. Any glitches? Performance OK? Lots of folks would want to know that info.