Labview 2023Q3 Crashing on Launch

[thutch79]

I have an install of Labview that is repeatedly crashing on launch. An error was generated while coding, and now I only get this error every time it launches. This has happened in the past, and I can't find a reliable way to get it out of this state. In the past, it has just started working again after time (I know that sounds weird). We have a number of installs on the exact same hardware and it only seems to be this computer that this issue occurs on. Attached is the screenshot of the error and the log generated.

Here's the details:

• Labview 2023 Q3 f2 64 bit
• Windows 11 (fully updated with windows update)
• Installed via NI Package Manager
• No volume license manager (active SSP local license)

Here's what I've tried:

• Computer reboot
• NI Package Manager repair of LV 64bit
• NI Package Manager full uninstall of LV 64bit and reinstall
• Everything relevant in this article: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9TXSA0&l=en-US

I'm sure I've tried other things I can't think of at the moment.

[thutch79]

I literally just left the PC overnight with no changes what so ever, and now Labview launches fine. Maybe that will give a clue to someone as to what may be happening.

[wiebe@CARYA]

I'd suspect something related to FPGA:

Launching resource generator using command: C:\Program Files\NI\LVAddons\nilvfpgahostcomm64\1\Targets\NI\FPGA\bin\gen_res_cache_lvaddons.exe -m "C:\Users\HDMUser\Documents\LabVIEW Data\2023(64-bit)\FPGATargetData\resource_cache_manifest.txt"

IIRC, Error 0xC0000005 is usually an external issue (dll or exe).

I guess this could also be a virus scanner preventing execution, or it could even be processing files in that folder the first (few) times.

Don't know, just thinking out loud...

[thutch79]

Thank you for looking into the logs! Interesting find. This system does not have the FPGA add on installed, but I believe it originally did. I think I took it out at some point when updating LV versions because I don't use it on this system. Comparing this system to another identical PC (even started from the same base image that has LV pre-installed), this is the difference. That system has the FPGA add-on installed still. Maybe removing it left some things behind that are causing the launch to crash. Like you said, maybe whatever is happening is interacting with anti-virus (just using the basic Windows Defender).

Next time this happens, and it likely will, I'll see if I can stop any anti virus activity and/or reinstall the FPGA add-on to see if anything changes.

Thank you!

[thutch79]

As suspected, I'm back in this situation again. I did try disabling antivirus with no luck.

NI Package manager seems to be in a weird state. It does not list FPGA module as being installed, but when I try to install it, it acts like it's a repair, not an install of the module. Any idea how to rectify that?

[thutch79]

For anyone stumbling onto this post.... I think I have found the issue.

When I installed Labview, I chose to install the FPGA module for 32 bit only, not 64. When launching 64 bit, it doesn't always like that. It's still a mystery why it would happen occasionally, and seemingly fix itself over time. But, when I just ran into this issue again, I installed FPGA module 64bit and it immediately started ok. I won't call it a total victory yet, but it's the first time I've been able to resolve the issue without just waiting.

[Matt_E.]

This worked for me as well on a machine that to my knowledge never had any version of the FPGA add-on module installed.  Unlike the op I haven't encountered the recurring come & go behavior of the error (found this post on the first instance), but nothing about my install changed between the day it was working fine and the following day the error started happening.  Feels like a LabVIEW bug, but glad to have a work around.

[JÞB]

I would suggest trying to delete <LabVIEW>\LabVIEW.ini which forces LabVIEW to regenerate that Configuration File with default (Shipping) values.

[thutch79]

Funny that this thread should get revived. I think I've finally found the real issue (or at least another factor). The FPGA thing didn't last. It still came back on occasion. Myself and my coworker now have the exact same hardware (PC) based on the exact same image with Labview already installed. The error happens for me, not for him.

The difference? I access this PC via remote desktop from a Mac. He does the same from another PC. When the error occurs for me, I literally can't restart Labview. When I went directly to the machine, it opens fine and I can go back to remote desktop until it happens again (can take weeks to come back up).

I have absolutely no idea why using remote desktop specifically from a Mac would cause this. I doubt NI nor Microsoft would give it 10 seconds of thought as the use case is probably very rare. I'm going to switch to VNC and see if the error ever comes back.

[Matt_E.]

Interesting, I'll definitely give the .ini approach a try if it comes back up.  For what it's worth I don't remote in to this machine from a Mac but I do use it almost exclusively via remote desktop so perhaps that is a factor (but I agree I don't see any obvious reason that should matter).  Good to know opening from the machine locally may be another work around.