LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The instruction at "0x000000019" referenced memory at"0x000000019" . The memory could not be "read".

Hi,

this topic came up several times the last years, so it may not depend on the version of LabVIEW.

We are running LV7.0 (EXE) on WinXP. The application works several hours fine when this error occur:

The instruction at "0x000000019" referenced memory at"0x000000019" . The memory could not be "read".

Yes, we have re-installed the system with latest NiDAQmx driver and so on ..

No, we are not using DLL, CIN or something like this.

What can I do ? My custumer is not amused ...

Every hint is welcome

- Jochen -
0 Kudos
Message 1 of 3
(8,026 Views)
I'm not sure what is causing it, but since it happens after several hours it sounds like it might be a "memory leak" where an array allocation or something of that nature is growing, not being properly deallocated, and eventually hitting a memory boundary. Could you give us a little more detail what you are doing, also there are somethings that have caused that type of problems in the past. A search of previous posting, etc. for memory leak produces a number of threads. Also to look for this one might start the program and note the amount of memory LabVIEW is taking using the "Task Manager" in Windows. Then looking at the numbers a while later (an hour or so) should tell you pretty quickly if this is an issue.



Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 2 of 3
(8,015 Views)
The memory consumption is not an issue. We have checked the memory 12 hours after programm start and it was constant. But just some minutes later the application crashes again.

Here are some infos about the application. We have a big application (EXE, runs on 25 PCs) which gets measurement data from different hardware which is loaded dynamically (VI Server technology).

In this case we have 3 PCI-cards (6225) with 40 channels per card. The app gets 100 channels (in diff mode) with 100 (!) samples per second.
We are using NiDAQmx for the first time. In a similar project (same application !, but different hardware) we used the traditional DAQ and have had no problems.

System :
PC with 1GB memory
latest NiDAQmx driver
LabVIEW 7.0 Runtime

Any ideas what we can do ?
0 Kudos
Message 3 of 3
(7,942 Views)