Why would LabVIEW cause a Exception Access Violation 0xc0000005 in windows NT4.0

[TPD63]

I have adapted the advanced data logger VI to log a temperature profile and control a heater relay. The VI ran for almost 24 hours with no errors until the Dr. Watson for NT agent reported and error.

"Dr. Watson for NT
An application error has occured and an application error log is being generated.

Labview.exe

Exception access violation [0xc0000005]
Address:0x1f802bb8

What could cause this? The vi is written in labview 5.1, the DAQ is a PCI-MIO16E-4.

[Dennis_Knutson]

Make sure that if you open a reference, you also close it - i.e. either a file or VISA. I would also look at memory usage. Do you have arrays that keep getting bigger and bigger until there's no more memory left?

[Albert.Geven]

This is a bug inside Labview 5.1. It is not a known bug in a sense that I have a solution but I'm also suffering from it.
I'll have a much bigger program that also stops after almost exact 24 hours of datalogging after an oven controlling process has stopped. My version is LV5.1.1 and the operating sytem is NT 4.0 with service pack 4 and the same problem occurred on NT 4 service pack 5. (a test on another fresh machine !) I use fieldpoint and serial IO so we do have the same bug but not at all the same program.
I also noticed that memory is not the problem and that dangling closes of refnums are not present.
It looks like some internal overwite of memory that is not available or not claimed correctly.

[Albert.Geven]

Yesterday I tried to run the program in lv6.02
And guess it works already more than 24 hours.
So this bug either in build array or the graph and is not yet present in lv6

[Albert.Geven]

My previous post indicated that lv6.02 solved the problem. It only takes longer to crash. after approxmately 80 hours the same crash appeared.

[Camilo Chaves]

I have the same problem. Turned out it was the XY graph, I removed it leaving the rest of the code intact, and no error showed up. My xy graph uses shift registers and increasing arrays to simulate a history graph. The problem was in the component xy graph, not in the code. I will try to use other graph components to see if it the error shows up again.