Labview 2014 Sp1 x64 is crashing all the time

[SunshineDesign]

I am working to develop a large test project in LabVIEW2014 SP1 x64 bit on a Windows 7 x64 bit OS. LabVIEW is crashing all the time at irregular intervals. I am seeing this with several different computers. I send in the crash reports regularily. I have been unable to prevent the crashing and am trying to work around it. I have not seen earlier version of labview x64 bit doing this. Anyone else having theis issue or have any suggestions? NI re told me LabVIEW 2014 SP1 x64 was pretty stable, but this is indicating otherwise. 

[Sam_Sharp]

Do you have any specific reason for using 64-bit LabVIEW? Unless you actually *need* to address more than 3GB of memory (e.g. manipulating huge amounts of data), there's no reason to use it over 32-bit LabVIEW. The downsides are that some toolkits aren't supported and you tend to be more limited in terms of interfacing with external code (e.g. DLLs, drivers etc.).

What NI (e.g. DAQmx, VISA, RIO?) and non-NI components (.NET, 3rd-party DLLs) does your application use?

Is there anything in your windows event logs or LabVIEW error logs that indicates the cause of the problem?

Is it crashing in the development environment, or when running your VIs? Do you have any toolkits installed? Do you have lots of classes in your project?

[Jacobson-ni]

When diagnosing a LabVIEW crash we really have to establish a cause and effect. On top of the questions Sam asked

1. How often do these crashes occur? It's hard to define when it's irregular but I would be interested if this is something that you would expect in a 1 hour to one day period or 1 week to one month type of period.

2. What is the exception code of the crash? Is it always the same? Attaching a couple of crash reports (the .zip that is created) would be helpful.

3. Using an application like perfmon, do you find that memory or CPU usage increases?

4. Do you see the same crash with all of your projects or just this one in particular?

I would also recommend calling in to get some additional help.

[SunshineDesign]

Labview 2014 Sp1 64 bit crashes nearly everytime I bring it up. It can crash after a while or right after I bring it up and don't even get to loading the project code. It is hard to look at perfmon during the crash as it is so random. I don't see much out of the ordinary when crash occurs. Crashes with any project or non-loaded yet. I attacheed one of the crash dumps. Doesn't seem to tell me much about the nature of the crash...

[SunshineDesign]

Project was built in 64 bit prior to my taking it over. I agree with your 64 bit labview assessment. But NI rep told me 64 bit labview was more accepted and stabole now. Obviously this is not correct. I have GPIB, PXI, TCP/IP and COM address devices connected. I have DAQmx, VISA, GPIB, NI-Switch, NI-Fgen and much more in the project. Does not seem to crash application after compilation, only when in development mode. I did not see anything in event log or elsewhere indicating the nature of problem. I posted the crash report in next thread input. No classes or toolkits in project.

[SunshineDesign]

One last note: I have installed LabVIEW2014 SP1 64 bit on a couple computers all standard installs and every one of the instllations is crashing consistantly at irregular intervals. The compiled version sof code seems to do OK, but the development environment is crashing all the time.

[Sam_Sharp]

Yeah, something is definitely wrong. It might be worth a call to your local NI technical support to see if they can help you troubleshoot the issue (e.g. perhaps a reinstall? perhaps some hardware incompatibility with your PC(s)? perhaps a dependency not working? perhaps you need to update some components).

I would expect 64-bit LabVIEW to be stable (but perhaps with a few more issues because it's a much smaller user base) - certainly not crashing constantly, especially if you haven't even loaded your project yet. It's mostly just that there is no real reason to use it over 32-bit LabVIEW unless you need the additional memory (e.g. performing huge amounts of number crunching / image processing) - and as I mentioned earlier, there are some downsides.