PXI RT 8.6 crash with error lvrt.dll load address 0x1924000

[nicola_fabbri]

I have an application developed with LabView RT 8.6 that run 24h/day and randomly crash evry 3-10 day with this error:

LVRT.DLL load address 0x1924000. Attached I put log file available after restarting PXI.

I dont found any information on this error, and it's very hard to found the soluction... any idea?

[Scott_A]

Hi there,

It is possible there is a memory leak going on somewhere in the code.  Are there any references that are opened in loops?

Do you have multiple versions of labview on your computer or just 8.6?

I would start by making a debuggable executable if you can.  Instructions for doing so can be found at: Remotely Debugging Executables in LabVIEW  and Debugging Applications and Shared Libraries

Are you able to tell any differences in when it crashes after 3 days versus 10 days?

[nicola_fabbri]

Application was developed with LV 8.6, actually I have installed a LV 8.6.1 in my lap top where I develope the application. I attach some print screen of configuration of PXI.

Application running on PXI consist of several never-ending loop, one of this is a time-critical loop where I from CAN, DAQ, and I send data via CAN. There is other Hardware-timed loop that comunicate via TCP/IP with PLC and with host computer (but application on host is not developed with LV, use a client socket to comunicate with PXI for reading data).

Error Log show alwayis the same error, and for my opionon, there is no relation for when the event occur, can be in any moment.

Application in pxi has some VI that are published as web service for diagnostic only, but there is no any interaction with user, (no keyboard and no mouse), it's a silent application, that read some encoder, calculate speed and aceleration, generate some output and send all data acquired via tcp/ip... 24 h/day.

Strange is that error position is always at 0x1924000, in all the error log!

Unfortunatly system is used all the day, and it's very far from office, so debug can be done only at specific day, when production is off... and internet is unavailable...

Enabling the debug mode, It's possible to have more information about the problem without changing the performance of the system?

Thank's for you help!

Nicola

[Scott_A]

You shouldn't see a problem after making a debuggable executable unless you were already at maximum memory and cpu load.  The debuggable exe will let us see what is going on and see if the memory use is increasing over time.

We can also look at reformatting the hard drive in case of a corrupt location on disk.