Application causes Windows fault in lvrt.dll among others...

[JCFryman]

I have an application that will occasionally crash due with a Windows error.  It states that the error is in the lvrt.dll file.  It lists 80 different modules in the technical information area of the warning.  I have tried to reinstall all NI hardware and software and the error will still occur.  it always happens at the same point  in the software if it is goign to happen.  This occurs right after pushing the start button the first time through the software.  If I reboot the PC, the software will normally run fine for a while.  Does anyone know what may be causing this problem?  I have included the main application.  I am running this application as an executable on the PC in question.  The PC is Windows XP SP2, with a Pentium II 863 MHz and 512Mb of RAM.

         Thanks,

               Craig

[Jarrod_S.]

What version of LabVIEW and the LabVIEW run-time engine is your application using? Do you know approximately what functions are executing at the time of the crash (you say it always happens at the same time)? Can you try this executable on another machine?

[JCFryman]

Jarrod,

    I am running LabVIEW 8.0 with runtime engine 8.0.  I cannot easily transfer the hardware (internal card) that is intended for this application to another computer as it is on a PC and most of our computers here are laptops.  As for where it may be at when the error occurs, I know that the DAQmx stop and start tasks are running as I stop the task at then end of one phase and restart it in the next loop.  Immediately after that are the daqmx read function and some scaling functions.  Nothing very complicated. 

         Thanks for the help.

             Craig

[Jarrod_S.]

Does this error only happen when running the application as a built executable, or does this happen when running the VI in the development environment too? Is this occuring on the development machine, or is this a separate target machine with only the run-time engine and daqmx installed?

[JCFryman]

The error has never occured on the development PC.  This only happens intermittently on the target PC that has the exe and rt engine installed on it.  It does acquire scale and task information from MAX.  Another problem that I have noted on the target PC and not the development PC is that the graphs will stop scrollling properly after 10-20 seconds.  The time does not advance and the line graph almost starts to act as a column graph.  I don't think this is connected, but I'll throw it out there.  This problem occurs when the software does run properly in every other way and does not cause the windows fault.

Craig

[Sci-Mech]

I am getting a similar error with my application, the program only crashes once it is compiled (using application builder 7.1).  I am running labview version 7.1, but the runtime engine is 7.1.1 - do you think this could be a reason that the program crashes (intermittantly)?  Do you suggest that I upgrade to Labview version 7.1.1 and recompile.

Did you end up figuring out what caused your issue?

[JCFryman]

As of this time, I believe we were able to trace the problem back to corrupted Windows/PC.  Apparently, according to our IT department, the Dell PCs that we had (older models) had inferior components that would cause strainge corruptions to occur.  I have replaced the PC and reinstalled everything and I have not had the problem since.  I will say that it has only been a couple of weeks, but so far so good.  I'm not sure if this is the same problem you are having or not.

[JamesR]

Hi Sci-Mech,

Does the problem always occur (if it does) at the same point as was the case with JCFryman?  How about if you try the executable on a different computer?

[Sci-Mech]

James,

When the problem occurs, it happens at the same time, once you double click on the executable.  I was doing some testing last night, it seemed better once I reset the compact daq device in Max.  Do you think it has anything to do with the Daq device and how it sets up?  Is there a way of programatically reseting the the daq device at startup (right now daq (digital and analog) start right away once the program is executed).

I looked ath the error log file that was created and it points the ApplLib - don't know if this could help.  The system has just left to the customer for a "demo" but will be back in a few days.

Sci-Mech

[JCFryman]

for perspective, my app never crashed in the same spot twice.  If your's is crashing regularly (and it sounds like in a different .dll) then my fix will probably not help yours as it sounds like we have different problems..