LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW Repetitive Crash

EXE crashes at initialisation and below dump file points to 3D graphs.

 

It's on Windows 7.  We have experienced this on multiple Windows 7 machines, however, it's been somewhat intermittent in that one machine now doesn't exhibit the issue.

 

These Windows 7 machines also have several apps (installers) written in different version of LV(RTE).

 

Could someone please advise asap.

 

####
#Date: Wed, 14 May 2014 1:39:32 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: XX
#Version: 13.0f2 32-bit
#AppKind: AppLib
#AppModDate: 02/03/2014 07:42 GMT
#LabVIEW Base Address: 0x30000000


starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3482883575.39945980, (13:39:35.399459839 2014:05:14)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3482883575.39945980, (13:39:35.399459839 2014:05:14)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3482883575.39945980, (13:39:35.399459839 2014:05:14)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3482883575.39945980, (13:39:35.399459839 2014:05:14)]

<DEBUG_OUTPUT>
14/05/2014 1:39:41.014 PM
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 34ce26f3-0b62-4295-ad68-27d9d3434580
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x307606D6 - lvrt <unknown> + 0
0x30760A5C - lvrt <unknown> + 0
0x711F50E3 - mscoreei <unknown> + 0
0x76EB0303 - kernel32 <unknown> + 0
0x777874FF - ntdll <unknown> + 0
0x77749F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x30000000 ***
GoDoit: VI "3D Scatter.xctl:Facade.vi" (C:\Program Files (x86)\XX\XX.exe\Facade.vi), HeapClass "FPHP", Act 55,
GoDoit: VI "3D Scatter.xctl:Facade.vi" (C:\Program Files (x86)\XX\XX.exe\Facade.vi), HeapClass "FPHP", Act 55,
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Facade.vi"
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Report_RESULTS.vi"
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Final Report.vi"
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Output_Main.vi"
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Main.vi"
#** Loading: "C:\Program Files (x86)\XX\XX.exe\Startup.vi"
*** End Dump ***

0 Kudos
Message 1 of 9
(3,231 Views)

battler,

 

Does this issue only appear in executables or in both the LabVIEW environment and executables?  Also, could you clarify your statement about the RTEs?  The version of the RTE has to match the version that the executable was built from.

Wayne T. | Application Engineer | National Instruments
0 Kudos
Message 2 of 9
(3,168 Views)

Hi Wayne,

 

The issue only appears in executables.

 

Regarding RTEs I mean that there are other applications installed on the machine which were built using different versions of LV and they were distributed with the correct RTE at the time.  This means that there could be different versions of the LV RTE installed onto these machines exhibiting the repetive crashes for LV 2013 exe.

0 Kudos
Message 3 of 9
(3,128 Views)

battler,

 

Have you tried to rebuild the executable?  Has it been tested on a clean computer?  I'm also thinking there could be a video issue, but still shying away from that one for the moment.

 

 

Wayne T. | Application Engineer | National Instruments
0 Kudos
Message 4 of 9
(3,089 Views)

This exe has been distributed to customers and was built in LV 2013 recently.

 

The same thing happened on a previous build of the same application on one of our PCs.

 

Both PCs are running Windows 7

0 Kudos
Message 5 of 9
(3,085 Views)

battler,

 

But have you tried to rebuild the executable after this problem's come up?  Has anything noteworthy been changed on the computers in question (i.e. periperal driver updates)?  What troubleshooting steps have you attempted?

Wayne T. | Application Engineer | National Instruments
0 Kudos
Message 6 of 9
(3,053 Views)

Hi battler,

 

This exe used to build and run correctly? 

 

When you get the crash dialog have you been submitting the reports? If you can send me the ID from the dialog when you submit the crash dialog I can take a look at that to see if there is more information there. That report includes the internal LabVIEW call stack and the exception, so there might be a bit more I can get from that.  

 

For the purpose of testing, if you remove the 3D Scatter graph from your front panel, does the exe run correctly? 

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect 

0 Kudos
Message 7 of 9
(3,040 Views)

@Jeff-P wrote:

 

This exe used to build and run correctly? 

 


Yes, it used to run perfectly for the customer.  Now it crashes upon loading.

 

We had the same thing happen with another Windows 7 PC.

 

I will try to send more log info if I can get it from the customer.

 

We can't rebuild without 3D graphs in order to experiment on the customers PC.

0 Kudos
Message 8 of 9
(3,029 Views)

What was the solution to this crash?

 

I get some similiar crashes in the development environment when mass compiling the project.

It says:

...

*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
GoDoit: VI "acq_loop.vi" (U:\LabView\101724 GasStation\trunk\GasSensor\acq\acq_loop.vi), HeapClass "FPHP", Act 55,
GoDoit: VI "acq_loop.vi" (U:\LabView\101724 GasStation\trunk\GasSensor\acq\acq_loop.vi), HeapClass "FPHP", Act 55,
#** Loading: "U:\LabView\101724 GasStation\trunk\GasSensor\acq\acq_loop.vi"
*** End Dump ***

0 Kudos
Message 9 of 9
(2,846 Views)