access violation

[samtrico]

We are experiencing application and/or Windows2000 crashes while running LabView and TestStand. The problem occurs randomnly. We have tried reinstalling the operating system and application software. DrWtsn.log shows access violations occuring mostly with LabView, although we have seen TestStand. Any ideas?

[swoboda]

My previous experience with LabVIEW access errors in Windows 2000 stemmed from user group settings. Are the errors consistently occurring with the same user, or does switching users change the outcome? Was an Administrator group member account used to create/install the code?

Regards,

Jason Swoboda

[JRA]

This Knowledge Base on NI's website talks a bit about access violations. You may want to take a look at it suggestions. Here are some of the main ideas it gives:

1. See if you can isolate a particular sequence of events that leads to the problem. For instance, is the problem associated with a particular VI or a particular feature in LabVIEW? Once you find the sequence, we can perhaps relate it to a known issue or track down a bug. We have to have more information in order to reproduce the problem and to see if this is a LabVIEW issue or a configuration issue.

2. See if the problem is related to an interaction with another process or application. Try disabling
any virus protection or other software that runs in the background and see if the problem goes away. One way to do so is to hit control-alt-delete and disable processes through the dialog that appears prior to starting LabVIEW. Most virus protection software includes the means to disable it, as well.

3. The problem might be related to your video card driver, because LabVIEW is graphically intensive.
a. If you are running Windows 9x, modify the acceleration setting to None. To do so, go to the Display Settings in the Control Panel and choose the Settings tab. Hit the Advanced button and move the slider to None.
b. If you are running Windows NT, try switching the video driver to the Microsoft standard VGA driver.

[samtrico]

Thanks. We are running under the Administrator login and yes the software was installed and application developed with Administrator login. I can try using a different user and see how that affects things.

[samtrico]

Thanks.

1. It doesn't appear to be caused by a particular VI or a particular step in TestStand. Sometimes just hitting F5 in Teststand will crash it. Other times it will crash anytime during execution of a VI. So, the randomness makes it more difficult.
2. It happens whether or not other applications are running at the same time. No anti-virus software is running or installed on this machine.
3. I will try switching to a standard video driver and see it that does anything. We are running Windows2000. We have similar systems running on NT with occassional crashes, but not even close to the Windows2000 systems.