LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Crash

My labview keeps crashing. Previously i had 2021 version but later i updated it to 2026 Q3. I am running a very small program that reads data serially. Issue is not in the code as i have tried other simple programs as well.

 

Anyone knows what the possible reason is ? I am using labview 2021 since 2022. During this period, i installed and uninstalled other versions as well.

 

I have Dell PC with 12th gen i7-12700, 2100 Mhz, 12 cores, 20 logical processors with 128 gb RAM.

 

Task manager shows that only less than 10% CPU and RAM is used when labview is running.

 

I bought it 3 years ago. Do you think i need to buy new pc or it requires resetting ?

 

0 Kudos
Message 1 of 10
(354 Views)

Do you get any error messages or crash reports?

Define "crash". (during editing? During running? program disappears? Program locks up? etc.)

I assume you also tried with a simple program that does not communicate with external hardware, right?

Do you run any unusual antivirus or other security software?

0 Kudos
Message 2 of 10
(277 Views)

For labview 2021, i was getting crash report that i have attached. For labview 2026, i dont get any report when it crashes.

 

Definition of crash is in which labview disappears no matter whether a program is running or not.

 

No anti-virus is used.

0 Kudos
Message 3 of 10
(238 Views)

There are a few "curiosities" in your system that seems "unusual" to me, and might explain where a "crash" might arise.  

  • LabVIEW 2026 Q3 requires Windows 11.  You are running Windows 10.  This might cause a significant "problem".  Did your code work before you installed LabVIEW 2026 (which affects earlier installations of LabVIEW)?
  • You have an astounding amount of memory on your PC.  Does your software require that large a memory space?
  • Can you create a small "test program" (in either version of LabVIEW), say something that "counts" from 1 to 10 at 1 second intervals (i.e. a For Loop with a 1000 ms Wait inside the Loop and an indicator wired to the loop index, "i")?  Attach the VI or a picture of the Block Diagram, and tell us if this simple program also crashes.

     Be sure to provide us more than a Crash report.

 

Bob Schor

 

P.S. -- Were there any other versions of LabVIEW on your machine when you installed LabVIEW 2026 Q3?  If so, what were they?

0 Kudos
Message 4 of 10
(180 Views)

@Bob_Schor wrote:
  • You are running Windows 10. 

Yes, we just now learned that from the attached log (You should have mentioned that in the original message!). It is very unusual that a PC bought 3 years ago is still running windows 10. I wonder why that is?

0 Kudos
Message 5 of 10
(168 Views)

Hi Both,

 

Just a little correction. I dont have Windows 10 and i never had it in last 3 years. I always had Windows 11 Pro. Dont know why that crash report says i am using Windows 10.

 

By the way, i have now erased the labview and going to install it from scratch as i read it somewhere that there could be some incompatible add-ons which are causing this crash. Lets see how that goes.

0 Kudos
Message 6 of 10
(163 Views)

@altenbach wrote:

@Bob_Schor wrote:
  • You are running Windows 10. 

Yes, we just now learned that from the attached log (You should have mentioned that in the original message!). It is very unusual that a PC bought 3 years ago is still running windows 10. I wonder why that is?



 

Just a little correction. I dont have Windows 10 and i never had it in last 3 years.s.


 

Windows 11 is reported as Windows 10 by design because the kernel version for both Windows 10 and Windows 11 is NT 10.0. This is intentional to preserve application compatibility. It is a Microsoft behavior, not an NI issue.
Detecting the OS is possible, but only indirectly, by checking the build number. The official API always returns 10 for Windows 11.

 

If your program is really small, just share the code if possible, or gradually strip it down step by step until you find the point where LabVIEW crashes.

Message 7 of 10
(105 Views)

Labview crashes even when no program is running. Its definitely not the program that is causing crash as i mentioned before. So far i have tried erasing all the labview versions and their packages and re-installed labview 2026. Problem is still same and for 2026 version i am not getting a pop up message which shows the the crash report is generated etc.

 

Another thing i have found is, if i disconnect my USB hub that i use to connect multiple instrument then labview doesnt crash. Do you think hardware can also cause labview program to be crashed ?

0 Kudos
Message 8 of 10
(55 Views)

@Andrey_Dmitriev wrote:

 

Windows 11 is reported as Windows 10 by design because the kernel version for both Windows 10 and Windows 11 is NT 10.0. This is intentional to preserve application compatibility. It is a Microsoft behavior, not an NI issue. Detecting the OS is possible, but only indirectly, by checking the build number. The official API always returns 10 for Windows 11.

That is technically not entirely correct. The standard Windows GetVersion(Ex)() API and friends does since Windows 10 not return the factual version anymore but whatever the application manifest requests the OS to be.

 

If an application does not have such a manifest, the functions report Windows 8.1 since it actually runs in compatibility mode.

 

To get the real Windows version one would need to call RtlGetVersion() in NtosKrnl.exe.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
Message 9 of 10
(22 Views)

@rolfk wrote:

@Andrey_Dmitriev wrote:

 

Windows 11 is reported as Windows 10 by design because the kernel version for both Windows 10 and Windows 11 is NT 10.0. This is intentional to preserve application compatibility. It is a Microsoft behavior, not an NI issue. Detecting the OS is possible, but only indirectly, by checking the build number. The official API always returns 10 for Windows 11.

That is technically not entirely correct. The standard Windows GetVersion(Ex)() API and friends does since Windows 10 not return the factual version anymore but whatever the application manifest requests the OS to be.

 

If an application does not have such a manifest, the functions report Windows 8.1 since it actually runs in compatibility mode.

 

To get the real Windows version one would need to call RtlGetVersion() in NtosKrnl.exe.


That was just an answer from microsoft learn, nothing more: https://learn.microsoft.com/en-us/answers/questions/4333284/windows-11-supposedly-installed-but-keep...

0 Kudos
Message 10 of 10
(3 Views)