LabVIEW 8.6 Crash

[tzantzai]

I’m getting this message lately:  “LabVIEW 8.6 Dev. Sys. has encountered a problem and needs to close. We are sorry for the inconvenience”. That is a crash and it happens at random: when a vi is running, when I edit the block diagram, when I stop a running vi or close the vi. Please advise.

[LV_Pro]

Well, there are a lot of things that can cause LabVIEW to crash unexpectedly, some are actually LabVIEW, some are not. Did you add a call to a .dll or some non-National Instruments instrument, board or driver?

In the Windows environment LabVIEW will attempt to create a crash log in the directory ..\My Documents\LabVIEW Data\lvfailurelog called something like lvlog06-21-11-21-11-00.txt, which gives the date and time of the file. This directory will probably have a lot of these files if you have crashed a lot. In this file there may be more evidence of what LabVIEW didn't like. I say "may" as about a year ago I was fighting a similar problem that turned out to be a badly written USB driver .dll (wrapped by even worse LabVIEW code). The error logs weren't too useful in that instance.

Tell us anything that you can think of that has changed, look at the latest error log, post if if you can and it isn't too long (my biggest was 31K, most around 4K)

[tzantzai]

Thanks Putnam,

Indeed I recently imported an old .dll driver for PXIT switch card. The .dll has been developed by PXIT Co. using NI LabWindows CVI 5.5. Plese see attached PXIT2000-105.zip for the LabVIEW wrapper of this driver.

Also attaced is the latest error log.

I notice that LabVIEW doesn’t create an error log every time it crashes.

[tzantzai]

I guess my question is: If this .dll is the problem, who can create a LabVIEW driver for this particular switch card PXIT2000-105. Basically all of my tests are developed using this legacy PXIT switch card.

[smercurio_fc]

Are you referring to these: http://www.home.agilent.com/agilent/product.jspx?cc=US&lc=eng&ckey=856050&nid=-35325.0.00&id=856050&...

A cursory look at that wrapper library doesn't show anything immediately apparent. I would have expected the calls to be "C" instead of stdcall, but the DLL may have simply been written that way. Did you create the wrapper VIs? Did you use the Import Shared Library wizard? Or did you get them from somewhere.

If the problem is with the DLL, it may be the way it's being used. What does your code look like?

Has LabVIEW crashed on you in other situations, or only when you've been programming with this DLL? Again, we're not sure it's the DLL here, but trying to see if we can isolate the general circumstances when LabVIEW crashes.