Windows 2000 crashes when exiting LabVIEW (sometimes)

[Ron Norton]

Sometimes (maybe roughly 50% of the time) after I have been running some of our VIs under LabVIEW 7.0, Windows 2000 Professional crashes when I exit LabVIEW. It is getting annoying enough now that I thought I'd see if anyone had enough insight to help me figure out where to begin to try to fix things.

We are using several boards from different manufacturers, and so are making calls to several different third party drivers and/or libraries: IOTech DaqX.llb, Measurement Computing Das16.llb, Eagle Technology edrapi.dll, and Piezomechanik AHV_DLL.dll.

The VIs will run fine and quit without any apparent problems but then when I exit LabVIEW the system crashes. Unfortunately, until recently Windows 2000 was set to aut
omatically reboot on the crash so I wasn't getting any error messages. The first one I've gotten now is: "Process has locked pages".

I realize this might not be much to go on, but does anyone here have any ideas about what's happening and how to even begin to track down the problem?

Thanks a lot

[tbob]

Write a series of test vi's that make function calls to your DLLs, one DLL call per vi. I suspect one of your DLLs is misbehaving. After you find the offending one, contact its manufacturer for an update.

[Jeremy_L]

Most likely page locks are occurring from DLLs manipulating memory and then not releasing control of it. Another test would be to see if you can run your VI without making any of the DLL calls and see if LabVIEW crashes still. At least then you can verify that it's something with LabVIEW calling your DLLs and not just the development environment crashing. Then, definitely try tbob's idea to determine which is the offending DLL.

Jeremy L.
National Instruments

[Matt_F]

Ron Norton,

These types of issues are almost always the case of a bad DLL. These DLLs typically corrupt part of LabVIEW's or Windows' memory space and will eventually cause a crash.

During testing you may need to create test VIs with more than one call. Many DLLs will only exhibit problems with a series of calls.

Regards,
Matt F