LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

System Crashes

I am using Labview 7.1. The application is running two Vi 's in parallel. the first is an ethernet communication. The second program communicates via the serial port. The vi's operate with no problems alone. When running at the same time I get the following error listing.
 
####
#Date: Sun, Aug 13, 2006 8:26:36 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS
 
D:\lvmerc\src\source\manager\memory.cpp(638) : DAbort:
$Id: //labview/branches/Mercury/dev/source/manager/memory.cpp#10 $
0x004650BD - LabVIEW <unknown> + 0
0x0067C2FB - LabVIEW <unknown> + 0
0x05929E8D - <unknown> <unknown> + 0
0x0589F41C - <unknown> <unknown> + 0
0x00A09110 - LabVIEW <unknown> + 0
0x8B535CEC - <unknown> <unknown> + 0
0 Kudos
Message 1 of 2
(2,555 Views)
Hello,
 
Thank you for reporting the error - we always want to know when users experience a crash so we can prevent it from happening in the future.  In order to investigate the issue, we'll need some additional information from you, specifically the two VI's that cause the crash (reduced to the smalled piece of code that still replicates the issue), the circumstances of the crash (i.e., does it happen every time, intermittently, does it matter which one is run first, etc), and a report from Measurement & Automation Explorer (MAX) of all the NI software installed on the computer.  You can generate this report in the more current versions by choosing the File>>Create Report menu choice.  On older versions, follow these steps:
 1) Open Measurement and Automation Explorer (MAX)
2) Go to Help->System Information and Support
3) Click on the System tab (this will generate a preview of the text file
that you are looking for)
4) Click the Report button and select Next after confirming/ignoring the
personal information fields
5) Select 'Simple Report' and click Finish
6) The desired text file will pop up and should already be saved to your
'My Documents' folder
 
With that information, I'll try and replicate the issue here.  It may be the case that VI's themselves are partially corrupted, or the installation of LabVIEW on your machine has been corrupted, in which case I may not see it on my end.
Cheers,

Matt Pollock
National Instruments
0 Kudos
Message 2 of 2
(2,532 Views)