We've found the problem, and it will be fixed in a future release. The crash occurs when you are suspended and have the variable display window open under the following conditions:
1) You have one or more ViSession variables, and
2) your program does not call viGetAttribute, and
3) the path to your EXE/DLL is somewhat long.
The easiest way to work around this issue is to add a call to viGetAttribute to your program. It does not need to do anything meaningful -- it just has to link. We're sorry for any trouble this has caused you. Let us know if you have further questions.
Mert A.
National Instruments
