LabVIEW 5.1 Application Crash 
Author Message
 LabVIEW 5.1 Application Crash


This type of crash is very difficult to narrow down. Some questions to

1. How occasionally is "ocassionally"? Is there any sort of
periodicity to the crash?
2. Does the software seem to be doing anything in particular when it
goes down?
3. Is this same software running on another computer?
4. Is it possible to run just certain portions of the code to narrow
down what's not playing well together? Personally, I'd be suspecious
of the FieldPoint and the two motion controller boards (in that
5. What is your memory consumption and cpu utilization doing around
the time of the crash? There could be a memory leak that is
culminating in the crash.
6. The drivers for the non-NI motion control boards, are they DLLs,
CINs or what? Improper DLL calls can cause sporatic crashes.
7. Is there anything else running on the computer that you don't
normally think about being there? Look for network-based automated
backups, virus scans, print servers anything that runs in the
8. Does the crash still happen when you have the thing on an isolated
network (i.e. no other network services running).

Sorry that this doesn't give you a solid answer, but as I said these
types of problems can be a bear to troubleshoot. Unfortunately you may
never know what is causing it--one day it will just stop doing it...


Sun, 15 Aug 2004 02:51:03 GMT  
 [ 1 post ] 

 Relevant Pages 

1. A custom built DLL crashes labview 5.1 in windows 2000 but worked fine in windows 98

2. Labview 5.1 crashes when inserting some sub vi's

3. LabVIEW 5.1 Application builder

4. LabView 5.1 <--> LabView 6i

5. Compiling in Labview 5.1 after installing Labview 6.0i

6. convert's labview 6.1 vi's to labview 5.1 vi's

7. labview application crashes with a Dr Watson Access...

8. Graphs in Reports of Labview 5.1

9. Labview 5.1 and GPIB

10. exponential window in Labview 5.1

11. renaming directory in Labview 5.1

12. Memory Management in Labview 5.1


Powered by phpBB® Forum Software