LabView often crashes on startup without error

[Greenas]

Hello, I installed LabView 24 Q3 on a Windows 11 System without any problem.
When I now start LabView the loading screen appears, however it disappears again without a comment and LabView does not start.
However, sometimes it works and then I can use LabView. So I know it is working on my System.
During my try I start it as admin or reload licences.
But it is really annoying that I have to try it half an hour or more each morning to use LabView.
(Other applications like NI-MAX, VI Package Manager or the NI License Manager I can start without a problem)
Do you have any Idea what I can try to solve this problem?

[altenbach]

Are you running any unusual antivirus or other security software?

[Greenas]

Nothing I know about. It is es fresh install of Windows 11.

[altenbach]

• Fresh OS installs are sometimes sluggish until all updates are made.
• How much empty space is on the HD? Is this an SSD?
• Did you check the drive for errors?
• Is there an entry in the task manager if it does not appear on screen?
• Are you opening labVIEW directly or are you clicking on an existing VI?
• Could it be that the welcome screen of offscreen location or on a different monitor?
• Have you tried deleting labview.ini, maybe it is corrupt?
• Have you tried repairing the installation?
• Is this the 32 bit community edition or 64 bit LabVIEW?
• Is this an regular Intel/AMD processor or e.g. an ARM processor in X86 emulation?
• How much RAM do you have?

[Greenas]

Ok, I will do the latest updates and try again.

My System has 100GB of Space, it is an SSD.

Did not check de drive for errors, will do later.

There is a task appering in the manager, but disappears at the same time the loading Screen of Labview Shuts down.

Open Labview directly or by clicking on an existing VI makes do difference.

As there is not entry of Labview in the task manager after it dissapears, I assume that the welcome screen is not offscreen.

I deleted the labview.ini once, after that I was able to start LabView, however I was not able to reproduce that. After a fresh start of my system this trick did'nt work.

I did not try to repair the installation. (Will do tomorrow if needed)

It is the 64 bit LabView.

It is an AMD Processor.

My System has 8 GB RAM.

Will give an update tomorrow, have a nice evening 🙂

[billko]

Good luck - I know how frustrating stuff like this can be.  😞

[altenbach]

These days, an 8GB system is relatively low end, but should work just fine. What is the exact CPU model?

[Kyle97330]

Next time it crashes, open up the Windows Event Viewer and look at the most recent entries under "Windows Logs\Application".

You will probably see one or two "Error" level entries that indicate an application crash and might hint at a reason in the event details when you select the event.

[Greenas]

Thank you for the advice.
There are errorlogs.
A)
Source: .NET Runtime
Application: LabVIEW.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFC58C485EC
Stack:

B)
Source: Application Error
Faulting application name: LabVIEW.exe, version: 24.3.0.4000, time stamp: 0x6688e0f8
Faulting module name: mgcore_SH_24_3.dll, version: 24.3.0.49499, time stamp: 0x66843324
Exception code: 0xc0000005
Fault offset: 0x00000000000085ec
Faulting process id: 0xB4C
Faulting application start time: 0x1DB5DEEC43F9B1B
Faulting application path: C:\Program Files\National Instruments\LabVIEW 2024\LabVIEW.exe
Faulting module path: C:\Program Files\National Instruments\LabVIEW 2024\resource\mgcore_SH_24_3.dll
Report Id: c54de4f4-89da-4921-950b-64ab194114b4
Faulting package full name:
Faulting package-relative application ID:


As the .NET Runtime Error appears first I checked for the error code c0000005.
It seems like this error happens if the program wants to read an invalid address.
Is this something common with LabVIEW and do you have an idea?
Else I will give an update if I find something.

[altenbach]

---

@Greenas wrote:

Is this something common with LabVIEW and do you have an idea?

---

It is definitely not common at all. There is something corrupt and it could be LabVIEW or maybe even a driver. Have you tried repairing the LabVIEW installation yet?