Crash in application by using TestStand 4.0 and CVI labWindows 8.01

Question

Our application often crashes in two areas:
1) Often crash in the case:
    During running, if there is poop, like error message, you want to debug by opening other programs,like notepad. 
    It shows error signature:
    AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName  cvirte.dll
    ModVer: 8.1.0.271         Offset : 000b9c8a
2) Often crash at the end of test, when generating TSV file.
     AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName  msvcr80.dll
    ModVer: 8.0.40727.762         Offset : 00008a8c
We use TestStand 4.0 and CVI LabWindows 8.01. The program is running in our customized operator interface.
But I tried using the default TestStand operator interface, it crashed too.
Also we found it is related PC too. One PC in our lab crashed often, but it actually newer PC with bigger RAM. (Pentium(R) 4 CPU 3.2GHz), 3.19GHz, 0.99 GB of RAM)
The one crashed Less often is Pentium(R) 4 CPU 2.80GHz, 2.79 GHZ 504 MB of RAM.
Hope you can help us to find out root cause.
Thanks 

Answer 1

Hi Doug,
Thanks for your reply.
Answers to your queries:
1. We are not calling any DLLs from our sequences.
2. We are only using LabVIEW modules and the VIs are called under LabVIEW development environment and not using Run Time engine.
3.  In our case it is always seqedit.exe which crashes. LabVIEW never crashed. Hence I think its TestStand whose memory is getting corrupted.
We  are trying to narrow down the issue as suggested by you.
By the time, we have observed a strange thing while the sequence editor crashed.
In our sequence we call a thread which calls a VI to run continuously and collect the data from other modules.
What we observed is that, when the sequence editor crashed (the popup appeared), it was still executing the sequence (running a loop). I was able to break the execution and debug it. All the variables were also having proper values.
But the VI which was running in a separate thread was in surprising state. That VI was showing as executing but actually it was not running any of its code. I tried to put probes inside that VI but they were not updated (meaning that part of code was not runnning). I tried to stop the VI using the abort button but no help. It was not having any effect. I also clicked on the Pause button. The button turned red but the VI didn't halt at any part of code (actually the VI was not at all executing). An other VI which was called by another thread was working properly. I could see it by putting probes in that VI.
If your thought about the memory corruption is correct, is it possible that this VI is somehow corrupting the sequence editor memory?
I am not sure, but I think wherever the sequence execution may be, but the above mentioned VI is always in this state at the time of crash.
I tried to reproduce this scenario locally but it ran without problem for hours
Probably I am still not able to properly reproduce it. I'll work on it further and let you know the outcome.
Regarding your last question, We are using LabVIEW notifier. A VI is called which waits on LabVIEW notifier from another VI. That code is pretty simple it just obtains a notifier and waits on it indefinitely.
Please let me know your views on the above mentioned issue.
Thanks,
- Kaustubh