Hello mrb,
We have called thousands of CVI DLLs from both Visual Basic and LabVIEW without them crashing, so this is not a widespread issue. First, you might try calling your DLL on another computer to determine if the issue is specific to your development machine. Next I would try building a very simple DLL (possibly \samples\dll\basic\cvidll.prj) and test again to determine if the issue is specific to your DLL or if it occurs with all CVI DLLs built on your development machine. Also, if you are using the DLL in VB, make sure that the calling convention of your exported DLL functions is __stdcall (make sure that LV's calling convention matches whatever the DLL is using). Does the DLL call any other libraries (GPIB, VISA, VXI, IMAQ, and so forth) and l
eave a handle/reference open? If this does not help, then we will require additional information in order to help further. What versions of CVI, LV, and VB are you using? What does the DLL do? You may consider contacting us directly at http://www.ni.com/ask >> E-Mail NI Engineers.
Jeremiah Cox
Applications Engineer
National Instruments
http://www.ni.com/ask