non continuable exception 0xC0000025

[ByteLABS]

Hi, all

I've this problem when i close application in runtime engine (in labview development this not appear).

The labview runtime crash and notify this error, i attach the log file generated.

Any can help me for how i can see to avoid this ? Thanks

####
#Date: mer 30 apr 2014 15:48:27
#OSName: Windows 7 Home Premium Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: RPM_AMCA_001
#Version: 13.0f2 32-bit
#AppKind: AppLib
#AppModDate: 04/30/2014 13:18 GMT
#LabVIEW Base Address: 0x30000000

starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3481714108,94139720, (15:48:28,941397191 2014:04:30)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3481714108,94139720, (15:48:28,941397191 2014:04:30)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3481714108,94139720, (15:48:28,941397191 2014:04:30)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3481714108,94139720, (15:48:28,941397191 2014:04:30)]
starting LabVIEW Execution System x00000004 Thread 0 , capacity: 24 at [3481714130,06117200, (15:48:50,061172009 2014:04:30)]
starting LabVIEW Execution System x00000004 Thread 1 , capacity: 24 at [3481714130,06117200, (15:48:50,061172009 2014:04:30)]
starting LabVIEW Execution System x00000004 Thread 2 , capacity: 24 at [3481714130,06117200, (15:48:50,061172009 2014:04:30)]
starting LabVIEW Execution System x00000004 Thread 3 , capacity: 24 at [3481714130,06117200, (15:48:50,061172009 2014:04:30)]
starting LabVIEW Execution System x0000000c Thread 0 , capacity: 24 at [3481714130,22118090, (15:48:50,221180916 2014:04:30)]
starting LabVIEW Execution System x0000000c Thread 1 , capacity: 24 at [3481714130,22118090, (15:48:50,221180916 2014:04:30)]
starting LabVIEW Execution System x0000000c Thread 2 , capacity: 24 at [3481714130,22118090, (15:48:50,221180916 2014:04:30)]
starting LabVIEW Execution System x0000000c Thread 3 , capacity: 24 at [3481714130,22118090, (15:48:50,221180916 2014:04:30)]
starting LabVIEW Execution System x0000000e Thread 0 , capacity: 24 at [3481714130,22618150, (15:48:50,226181508 2014:04:30)]
starting LabVIEW Execution System x0000000e Thread 1 , capacity: 24 at [3481714130,22618150, (15:48:50,226181508 2014:04:30)]
starting LabVIEW Execution System x0000000e Thread 2 , capacity: 24 at [3481714130,22618150, (15:48:50,226181508 2014:04:30)]
starting LabVIEW Execution System x0000000e Thread 3 , capacity: 24 at [3481714130,22618150, (15:48:50,226181508 2014:04:30)]

<DEBUG_OUTPUT>
30/04/2014 15:50:28.915
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 8a13a5f6-640c-4db6-ab53-48f7dca11c20
ExceptionCode: 0xC0000025

</DEBUG_OUTPUT>
0x307606D6 - lvrt <unknown> + 0
0x30760D11 - lvrt <unknown> + 0
0x30992173 - lvrt <unknown> + 0
0x300D732C - lvrt <unknown> + 0
0x3013751A - lvrt <unknown> + 0
0x305FE1D9 - lvrt <unknown> + 0
0x30601B5D - lvrt <unknown> + 0
0x306031B2 - lvrt <unknown> + 0
0x307EE047 - lvrt <unknown> + 0
0x30888665 - lvrt <unknown> + 0
0x307FFE49 - lvrt <unknown> + 0
0x308002A2 - lvrt <unknown> + 0
0x759062FA - USER32 <unknown> + 0
0x75906D3A - USER32 <unknown> + 0
0x759077C4 - USER32 <unknown> + 0
0x7590788A - USER32 <unknown> + 0
0x308888ED - lvrt <unknown> + 0
0x30888D67 - lvrt <unknown> + 0
0x031E14D6 - QtManager452_2013 <unknown> + 0
0x670E7251 - NIQtCore_2013 <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

[muks]

Are you using any FPGA?

[ByteLABS]

No i use a cDAQ ethernet 

[ByteLABS]

To help answer,

The problem appear when i run two vi's with callbyreference.

[ByteLABS]

I continue to have this error, i tried also with asyncronous and wait asicnronous...but it appear again.

i don't know whats i can do to solve, please help me, thanks.

---

ByteLABS ha scritto:

To help answer,

The problem appear when i run two vi's with callbyreference.

---

[LiciaP]

Hi,

have you been able to develop a simple code reproducing this behaviour?

Is the crash reproducible on multiple machines?

Bye,

Licia

[Sam_Sharp]

Are you calling your VIs with a static reference on your block diagram or loading them dynamically? I wonder if it could be that it is missing dependencies or can't find them. Putting a static reference on your block diagram will ensure that the dependencies for the VI are included in the executable.

Just a thought...

[ByteLABS]

Thanks Sam,

it seems work with static reference, but the vi hold in memory and the behavior is similar of the vi called with subvi calls.

My problems needs the vi is recalled because i have some parts with  a "first call".

I attach the code try with call by reference.

Thanks for your help.