From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

lvalarms.dll crash

Hi everybody

     I tried to find a solution for this problem .

When I use a Timeloop , the first time the VI work very well but the second time Labview crash.

This is the error message :

Description:

Stopped working

Problem signature:

Problem Event Name: APPCRASH

Application Name: LabVIEW.exe

Application Version: 12.0.1.4014

Application Timestamp: 522f27d1

Fault Module Name: lvalarms.dll

Fault Module Version: 5.0.0.49154

Fault Module Timestamp: 4fccee09

Exception Code: 80000003

Exception Offset: 00001779

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

 

I tried to change the processor (Timeloop paramters ) but I got the same error

This is the VI that I used

Thank you for you help

 

 

 

0 Kudos
Message 1 of 11
(3,716 Views)

@Ruroniko wrote:

 

 

This is the VI that I used

 

 

 


I don't see an attached VI, can you try it again?

 

Posting a code snippet should also work.

0 Kudos
Message 2 of 11
(3,711 Views)

sorry

 I trie again

 

0 Kudos
Message 3 of 11
(3,707 Views)

Still nothing.  Use the button shown:

 

Attach here.png

0 Kudos
Message 4 of 11
(3,699 Views)

I don't have the same buton

this is a picture

Capture.PNG

0 Kudos
Message 5 of 11
(3,691 Views)

I use a other account

sorry about that

 

0 Kudos
Message 6 of 11
(3,679 Views)

no body ?

0 Kudos
Message 7 of 11
(3,657 Views)

Can you try to right-click the timed structure inputs and select "Configure input node", then change the processor assignment to Manual, processor 0?

 

It worked for this guy.

0 Kudos
Message 8 of 11
(3,634 Views)

Hi

   thank you for the reply

 

So I changed the processor ( I put 0). But still not work Smiley Sad

0 Kudos
Message 9 of 11
(3,621 Views)

Is there a way you can create a VI that causes the problem but doesn't require any specific hardware to run?

 

I don't have whatever DAQ device you do so I can't test it.

0 Kudos
Message 10 of 11
(3,616 Views)