LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

access violation causes crash

I have a very interesting case of this access violation crashing problem.  I looked around but none of the other discussions on the same topic suggested a solution that has worked.  

I have a LabVIEW 2013 exe that runs great in a couple of systems (both XP and Windows 7).  I recently got a new Lenovo PC Windows 7 64-bit and I installed this application in it.  Every time I open the application on this new PC, almost immediately it crashes (sometimes it takes a minute or for me to click on a button before it crashes).  The error is an access violation (see attached).  The lvlog file is also attached.  I must re-iterate this application works fine in other systems.  Does any one have any idea what could be going on?  Why is this new PC saying LabVIEW causes and access violation when is never been a problem before?  Has anyone run into something like this?

 

lvlog content:

 

####
#Date: Tue, Nov 03, 2015 1:37:13 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: DSCD_TESTSET
#Version: 13.0.1 32-bit
#AppKind: AppLib
#AppModDate: 10/13/2015 21:05 GMT
#LabVIEW Base Address: 0x30000000


starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3529420635.71337320, (13:37:15.713373185 2015:11:03)]

0 Kudos
Message 1 of 5
(3,286 Views)

@nelg87 wrote:
...

 a new Lenovo PC Windows 7 64-bit...

 

lvlog content:

 

####
...
#Version: 13.0.1 32-bit
...


?

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 5
(3,268 Views)

So my program is compiled for 32 bit and doesn't run on 64 bit?  How do I compile my program for 64 bit??  I should add my development environment for this application is on a windows 7 64 bit PC.  I build an exe on my development PC and is currently running on a Windows XP... Actually I just checked and my other computer that I'm running this with (not Lenovo) is running Windows 7 64-bit and there is no crash issue.

0 Kudos
Message 3 of 5
(3,256 Views)

I guess I'd start with, "What's the nature of the application?"  (Can you reveal anything?) 

 

What kinds of devices is the application interfacing with?

 

Could it be a driver incompatibility? Is it calling a DLL that isn't compatible somehow?

Could it be a hardware difference leading to incompatibility?

 

I've seen crashes in the past related to mismatched drivers or incompatible hardware.

 

This'll probably sound obvious, but the question really is, "What's different about this particular Lenovo PC?"

0 Kudos
Message 4 of 5
(3,235 Views)

@nelg87 wrote:

So my program is compiled for 32 bit and doesn't run on 64 bit?  How do I compile my program for 64 bit??  I should add my development environment for this application is on a windows 7 64 bit PC.  I build an exe on my development PC and is currently running on a Windows XP... Actually I just checked and my other computer that I'm running this with (not Lenovo) is running Windows 7 64-bit and there is no crash issue.


There is no problem running 32bit LabVIEW on a 64 bit machine. This is actually the recommended setup.

(32bit LabVIEW has access to more RAM (full 4GB)  if the OS is 64bit (details), while LabVIEW 64bit still has limited support for addons).

 

Let's assume that you have installed all drivers and run time engines correctly.

 

Obviously, there is something that interferes or is incompatible, and it might not be LabVIEW.

 

  • What is the exact name of the CPU? How many cores does it have?
  • Is there any lenovo bloatware that you can disable?
  • Are you running any unusual antivirus or security software?
  • Did you try to repair the installation?
  • Did all required files transfer correctly to the new machine?
  • Is there anything interesting in the windows log?
  • Have you done all the windows updates?
  • Does your program interface with DAQ hardware or is using any third party drivers?
0 Kudos
Message 5 of 5
(3,220 Views)