kaiserft wrote:
"We are testing the Labview programs without Hijaak running now."
...
If the test demonstrate that the problem is indeed with LabVIEW, I suggest you should contact the testing engineer that develop it because the program need debugging.
If, on the other hand, the test demonstrate conflict between LabVIEW and Hijaak software, I'll recommend to request support to National Instruments to inform this at www.ni.com/ask. I am sure they will help you.
I suspected a (major) memory leak because the symtoms are similar. As you may already know, when the machine is rapidly becoming critically low in resources, is very little what you can do other than to reboot it. Under this circumstances is hard to trap the error, but you can s
ee it coming with tools for resource management. There is a company called LIUtilities (http://www.liutilities.com) that have a tool called WinTask that enables you to do resource management.
Regards;
Enrique
www.vartortech.com