LabVIEW crash (ntdll.dll issue)

[MikeAM]

Hi,

I am now having my LabVIEW application crash every 1 or 2 days. I continuously run the application on industrial PC and found application front panel disappear from my screen.

Tried to look into event viewer at the time my data logging stopped, found application error as below.

Faulting application name: LabVIEW.exe, version: 21.0.1.4001, time stamp: 0x624b3ed7
Faulting module name: ntdll.dll, version: 10.0.19041.1682, time stamp: 0x9b46280a
Exception code: 0xc0000374
Fault offset: 0x000e6cf3
Faulting process id: 0x2b14
Faulting application start time: 0x01d876598f21d723
Faulting application path: C:\Program Files (x86)\National Instruments\LabVIEW 2021\LabVIEW.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: b65cf0a8-4855-478c-9e90-ef897b7c79bf
Faulting package full name:
Faulting package-relative application ID:

Any could tell what is happening here?

Note: I started with uninstalled all NI related software via NI package manager.
Then, I installed LabVIEW 2021 (32-bit), Vision Acquisition Software 2021, Vision Development Module 2021, and DAQmx 21.8 one by one with reboot in between.

My OS is Windows 10 Pro.

[sorin1]

Hello, 

I didn't see any reply for this case. I'm interesting because I have the same error in my LabView 2013 application. It is an application installed some years ago on Windows 7 pc without any errors and now it is installed on Windows 10 and the error is present. My application crash without showing any error, I found the error in the Windows event viewer.

This is the first event found in the event viewer Windows:

.NET runtime error ID 1026

Application: MyAppLV.exe
Versione framework: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception info: exception code c0000005, exception address 77CEF583

And this is the second event (occurred in the same time):

Faulting application name: MyAppLV.exe, version: 1.0.0.95, timestamp: 0x52cf1e34
Faulting module name: ntdll.dll, version: 10.0.19041.1466, timestamp: 0x9012d056
Exception code: 0xc0000005
Fault offse 0x0005f583
Faulting process id: 0x2694
Faulting application start time: 0x01d96086d38dff18
Faulting application path: C:\Program Files (x86)\MyApp\MyAppLV.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5a381d88-3f89-4601-94d2-71bb9c2322db
Faulting package full name:
Faulting package-relative application ID:

[dj_tony]

win 10 LTSC - LV2020

application working on 100 system. 18 - 01 - 2025 (dd-mm-yyyy) 2 updates for windows and ntdll.dll crash appears everytime i use a part of my software. for now only on one fresh installed system that has worked until 18-1-25. everything is on a build exe.

this evening a customer leave a machine on, so i can try some fix or investigate.

[rolfk]

ntdll.dll errors are unfortunately very unspecific. It could be anything, from a bad driver for any of your device hardware, a 3rd party DLL that you call somewhere in your application, to a bug in LabVIEW itself.

I regularly run into ntdll.dll errors when developing and testing my own DLLs. And generally they are nothing more than: "Yes you did something wrong. But I can't even start to guess where and what." If this happens during development it is partially helpful as the first subject to investigate is your last code change, but otherwise it means usually: starting to make changes until something changes. If you are lucky the error gets more specific and gives you a real hint where the problem is.

[Andrey_Dmitriev]

---

@rolfk wrote:

I regularly run into ntdll.dll errors when developing and testing my own DLLs. 

---

You're very "lucky", Rolf, I also crashing LabVIEW regurarly, but such crashes are very seldom deep propagated up to ntdll.dll. But when this happened, then usually I run app under debugger (WinDbg or dbg64), sometimes call stack could give me additional info, but it depends, of course. Usually such crash raised from my own code, then trivial static code analysis or "intrusive debugging" with logging is sufficient to catch wrong point.

[dj_tony]

UPDATE.

i don't know why but it was related to a reciver dongle of a wireless barcode reciver, that was a simple HID. 

i've switched pc to customer with a fresh new one, no update, and after inserting the damn dongle sw start crashing again. LOL

was not a barcode provided by us. i've ordered one to see what can be.