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

[DanceWiz]

Hi,

I installed Labview 7.1 a few months ago on a new pc (windows xp) and kept getting this error message a number of times in the first few weeks (can't remember what I was doing when the message would come up). 

Since yesterday, Labview kept crashing while I was working on a vi's block diagram (the vi was not running, I was just adding a wire or etc.).  It would say "Labview has encountered a problem and needs to shut down" or something to that effect.  I decided to uninstall and reinstall Labview again.  As it was uninstalling, it gave me the old message again, i.e. "The instruction at "0x7c91..."". 

So, just in case it starts giving me the same problem once it is installed again (which is doing it as I am typing this), I would like to know if anyone has ran into this problem and knows a bit more about it, and how to fix it...

Thanks

[Ray.R]

Have a look at this thread.

It's been seen on a newer version of LabVIEW and may somewhat be related.

[Ray.R]

Also have a look at this thread

Did you install 3rd party drivers or working with DLL's in your program?

Message Edited by Ray.R on 07-30-2009 05:16 PM

[DanceWiz]

Hi Ray.R

Thanks for answering.  The only drivers that I have are the DAQ Legacy and DAQmx.  As for the DLL's, I am not calling any directly, but I think that some of labview's own vi's from the "Functions" palette which I am using in the program, e.g. Median.vi (All Functions<Analyze<Mathematics<Probability and Statistics), are using some DLLs.  But the thing is that I was not running the program, I was just editing it!  I have quickly read through the threads that you have linked to.  I am not sure if they are helpful for this situation, but I will post again when/if this problem occurs again or when I have some more information.

[Ray.R]

If it crashes suddently, you may want to look at LabVIEW's debug log.  You can also have a look at this thread and possible use what DFGrey offered in this post.

[Charlie_P]

Good Morning DanceWiz,

Does this problem occur with a specific VI (or group of VIs)?  If so, it is possible that the file(s) is(are) corrupt.  In this case, copy/paste your Block Diagram to a new, Blank VI and continue editing from there.  If the problem persists, we will know it is a system level issue instead of a VI issue.

In any event, that is an important piece of information to have to properly troubleshoot something like a bug that repeatedly occurs while not running the VI.

[DanceWiz]

Hi Charlie,

Sorry for the late reply.  I think I have narrowed down the problem today.  It must have to do with the express vi "simulate an arbitrary signal".  I had not used this vi in a long time (probably since about the last time I had this problem) until today. I dropped it on my program and loaded the .lvm file into it (10000 points); everything ok so far.  Next, I dropped a second "simulate an arbitrary signal.vi" on the program and the problems started.  The pointer of the mouse flickers very rapidly between "normal" and "busy", i.e. the arrow and the sand clock, and the page goes blank for a few seconds while the top says "not responding" and then it comes back again and this happens over and over again while I am just trying to edit the program.  I closed the file on the desktop computer (LV 7.1, Windows XP (apparently with Vista also loaded)) and moved it to the laptop (LV 7.1 and LV 8.5 Student Edition, Windows XP) and had the same problem with both versions of Labview.  The problem persisted until I deleted the "Simulate an aribtrary signal.vi".  It happened again when I tried it again.

I have also tried the same with smaller files (i.e. 1000 and 5000 points) with same results.  A lot of the times it gets hung up in the "Define Signal" window: it loads the file under "Data Points X Y" without a problem, but it does not recognize the "dx" (and hence the "Number of Points") under "Timing" correctly.  When I change the "dx" manually, it does not update the "Number of Points".  It seems to me like the problem stems from here.  

This is the same behavior for LV 7.1 and LV 8.5 Student Edition.  Perhaps the files I am loading are "too big", i.e. too many points???

[Charlie_P]

Good Afternoon DanceWhiz,

After reading the first paragraph, I was going to suggest trying a smaller set but you beat me to that in the second paragraph.  Can you post your .lvm and .vi files?