Help interpreting VeriStand crash report

[Damian_S]

If VeriStand 2014 is left running for a few days, it will eventually crash. I run VeriStand on other test stands and its very stable. Based on this, i'm sure that the crash is related to a unique piece of code (custom device, model, etc...) or setup for VeriStand on this test stand.

Attached is the error log. I need help to interpret the error log to narrow down the issue. Normally I would just remove a piece of the code and let run to see if it crashes, but this project is quite large it would take quite a bit of time to troubleshoot in this method.  

Going through the error log I did find this message, but i don't really understand how to fix it. 

C:\Users\Public\Documents\National Instruments\NI VeriStand 2014\Custom Devices\NHR Power Module Rack\Data\NHRDCPowerModule.dll

ExtFuncDWarnOnCorruption: connectorTDR is
TDR (1/2): @0x0000: 'NHRDCPowerModule_ReadArray': 8
@0x0000: 'return type':
@0x0004: 'Vi':
@0x0008: 'MeasurementsBufferSize':
@0x000C: 'Measurements': [V0]
@0x0000: '':
@0x0010: 'Method':
@0x0014: 'ValBuff
TDR (2/2): erSize':
@0x0018: 'Val': [V0]
@0x0000: '':
@0x001C: '':
@0x0000: 'ValActualSize':

Little bit of background for this project:

VeriStand deploys to windows target for NH Reseach Power Supply and it also deploys to cRIO9081 with 9144 EtherCAT chassis. The project contains multiple custom devices and models. 

[Guilherme_Correa · Accepted solution]

This kind of report should be sent to NI support. 

They might provide a solution for this, or at least be aware of this behavior. 

[Damian_S]

Hi Guilherme,

Thanks for the advice. I'll contact support regarding this issue.