corrupted LabVIEW's memory?

[tonitpp]

Hello,

I'm acquiring data continuously from probes but after a long time I get the following error message:

LabVIEW: An exception ocurred within the external
code called by a Call Library Node. This might have
corrupted LabVIEW's memory. Save any work to a new
location and restart LabVIEW.

VI "AcquireAIData.vi" was stopped at node 0x19E4 of
subVI "DAQmx Start Task.vi".

What's happening?

Thanks everybody,

ToNi.

[Cristobal]

Hello,

I would try to repair DAQmx driver and if it doesn't work, I would unsintall and reinstall it again.

Moreover, are you trying with the latest version of DAQmx? If not, try with it.

Do you have the same problem in another PC?

Regards

crisR

[tonitpp]

Hi,

Thanks, I solved this problem time ago but now I'm getting a similar one.  After time executing my data acquisition application, after 50 minutes approximately, I get the following error:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LabVIEW: An exception occurred within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW.

VI "AcquireAIData.vi" was stopped at node 0xA10 of subVI "DAQmx Create DO Channel (sub).vi".
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I think DAQmx Driver is not working again very well, Do you know if it is the problem? If it is, why DAQmx Driver crashes from time to time?
I'm not using the latest version of DAQmx Driver and I use LV 7.0 Express but It always have worked well for me despite sometimes DAQmx Driver crashes.

But.... this error only ocurrs in the Industrial PC but not in my PC at home, so as you said, maybe the problem is that DAQmx Driver has crashed again and I need to repair, and if it doesn't work, uninstall and reinstall the DAQmx Driver would be the best solution to solve this problem.

I'll try it and I'll tell you something,

Many thanks for your help,

Best regards,

Toni.

[tonitpp]

Hi,

I reinstalled the NI drivers but the problem persists, I don't know what is the problem.... Could you help me please?

Thanks,

ToNi.

[tonitpp]

Hi,

The problem was that I created a virtual channel every time inside the loop and then the memory got wrong because of it. I corrected it by creating the virtual channel once with DAQmx create virtual channel and DAQmx start task nodes outside the loop and then calling the DAQmx Write or Read node every time inside the loop.

Thanks,

ToNi.