Why do I get a windows error every time I stop or close an executable?

[macolit]

Whenever I run an executable in any windows computer it runs fine but as soon as I stop or shut down the executable, I get and a windows error. The program that I have reads from compact Fieldpoints and processes those data. Once you close or stop the program, that is when I get the error. No other error is generated from LabVIEW, only windows error. I have been seeing this error since I upgraded to LabVIEW 2010. I never had this error before when I was using LabvIEW 7.1 or 9. I do not see the error when I am using the VI itself before the build, only when it becomes an executable is when it generates the error in windows.

If anybody knows anything about this pls. respond to this post. I have read somebody elses problem with the executable crashing but no one has posted a viable solution. It does not affect the functionality of the executable at all. It is just annoying that we keep getting the error/crash whenever we have to exit the program and new users keep asking about it.

Thank you all,

macolit

[Patricia B]

Hello,

Perhaps there is a driver or LabVIEW compatibility issue here. What version of the cFP drivers do you currenty have installed? The most recent release of the cFP driver is 6.0.8 and can be downloaded at ni.com/updates. I would also install LabVIEW 2010 SP1. From your post, it appears you only have LV 2010 installed. The LV update may also assist in resolving the issue you are having with the executables. LV 2010 SP1 can be downloaded at ni.com/src if you have a purchased copy and not a trial version. Otherwise you can locate the trial at ni.com/labview. Hope this helps.

Best,

[macolit]

Hi Patricia,

I'm currently using LV 2010 DS2 with cFP driver 6.0.7. I have just received LV 2011 DS1 and have not installed them yet. Maybe this will fix the problem but I have my doubts. 

Whether I press the stop, abort or close all, it does not matter, it even happens when I stop programmatically, I get the error no matter what. There's got to be a component of the build that is causing this problem.

Regards,

Macolit

[Patricia B]

Perhaps updating LV will resolve the error but typically LV should not cause other applications to crash. Do you happen to know what application LSTR_V1.0 from your screenshot might

Best,