0x0000005 at EIP (0x00C267F9)

[technojane]

I am using the following hardware: cDAQ 9188, Mod1: 9425,Mod2:9476,Mod3:9221.

Labview 2011, evaluation version

Program flow:

Login.vi: logs in the user with correct credentials.

Test Selection.vi : bunch of 5 combo boxes within a Timeout event of event structure and their respective RUN buttons. Each Value  change of  a RUN button, asynchronously calls a  program vi that is a component test. On exiting Test Selection vi , another new vi is called(asynchronously) that monitors the status of all programs via global variables.

Test panel.vi: This vi is called when above vi quits. It has a bunch of 5 strings displaying names of Tests that were selected in the earlier vi(combo boxes), their respective boolean indicators(indicating if the vi is running or not), string indicators(updating the cumulative test cycles/hours in the corresponding test in text format) and string indicators also for the start time. Alongwith them are View buttons.

This program is also within an event structure. the timeout section handles, updation of cycles status booleans through global variables inside a for loop. Whenever a View button infront of a test name is pressed, it simply opens the front panel of the test vi that was RUN in Test Selection.

(I cannot attach snapshots of the program, so I wrote the entire thing :P)

The error doesn't occur at any specific point.

Just a guess, could the asynchronous calls be causing this? I want several vis to be running in the background and their front panels opened when the user wants to see more than just the cumulative cycles being shown on the Test panel. Any suggestion how I could achieve  that without asynchronous calls?

there are some memory control APIs (Application Control palette eg Request deallocation), could those help?

[Akiel]

I had a similar error (EIP=0x3504f1b4) and it was related to reading more elements off a fifo from an fpga than the queue was set up for. So after a period of time labview fell over in a similar style. Not sure if its relevant to your application but may give you a pointer

[Akiel]

Just too follow up on the problem I was having, I have found the root cause of this problem. Changing the number of elements read from a FIFO just hid the problem, it didnt get rid of it. It was the result of a couple of errors. listed as follows:

Channels incorrectly defined in FPGA meaning i was reading more channels than i needed to

when i process the data I was processing too many channels so one of these was empty

When i wrote the empty channel to a tdms file it crashed

once i cleared these issues the code is now stable

Hope it helps