Troubleshooting VeriStand™ Crashes

Issue Details

• VeriStand keeps crashing on my PC. How can I resolve this?
• VeriStand is crashing and reports the error below. What troubleshooting steps can I take?

• I see the screen below when VeriStand crashes on my PC. What could be causing this?

• When VeriStand crashes, I don't see any error report. How can I troubleshoot the problem?

Solution

• Software corruption.
• Problems within Models or Custom Devices.
• Problems with the operating system.

Initial Troubleshooting Steps

1. If a crash report is generated after VeriStand crashes, send the report to NI.
2. Determine whether or not the crash is reproduceable.
   • This can be done by running VeriStand in different environments and conditions.
   • If possible, test the behaviour in different: operating system versions, software versions and VeriStand projects.
3. Verify whether the same behaviour is observed when deploying the VeriStand Engine Demo project.
   • This can be found on the main splash screen after launching VeriStand.
4. Eliminate the possibility of software corruption by removing and reinstalling it from NI Package Manager.
   • Instructions on how to do this can be found in Installing, Updating, Repairing, and Removing NI Software.
5. If the VeriStand project consists of Custom Devices and Models, test the project after removing them from the System Definition.
   • Often times, VeriStand crashes can be caused by unreleased references or model import values.
   • Refer to Troubleshooting Issues in Models and Troubleshooting NI VeriStand Custom Devices for more information.

Further Troubleshooting Steps

1. Locate VeriStand's error log files on the host.
   • Depending on whether a previous version of VeriStand was installed on the PC before, these may be stored in different locations.
   • Check C:\Users\<username>\AppData\Local\National Instruments\VeriStand <version>\ErrorReports and C:\Users\<username>\Documents\LabVIEW Data\LVInternalReports\VeriStand Project Explorer\
2. On Windows PCs, ensure that the operating system has been configured to generate dump files.
   • To do this, go to Control Panel and select System and Security >> System.
   • From the left hand side of the System window, select Advanced system settings.
   • In the System Properties window, click on Settings in the Startup and Recovery section.
   • From the pop-up window, ensure that Write an event to the system log  is enabled.
   • Under the Write debugging information setting, select Kernel memory dump or Complete memory dump.
   • Restart the PC.
3. After this, reproduce the crash and send the most updated dump files and error logs to NI Support for further troubleshooting.