Blue Iris

I have updated to the latest BI. BI starts up ok and then just blinks out of existence in less than 15 seconds.
I've sent a support email to BI, so in the meantime, has anyone else experienced this? I was able to revert BI back to version 5.9.8.5 but get the same results. My next step would be to purge everything I can find of BI off my machine and start a brand new install.

I am running Windows 11 on a lenovo desktop:
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
32.0 GB (31.7 GB usable)
Windows version 24H2

I'm

Did you check the windows event log for the BI application to see if it gives any clues to what is happening, before you take the drastic step of a complete reinstall of BI!

Hopefully you have all your serial numbers and activation codes stored somewhere safe, if you wipe the current install you might have problems reactivating if you are not able to deactivate the current install!

It's pretty hard to guess as to what might be going wrong with out some clues!

That is really strange. In the past when I’ve seen this it could be because hardware acceleration is enabled on a cam that causes the issue but given that you’ve regressed back seems strange that you still have the issue.

You could try disabling hardware acceleration by dealing into the registry?

I checked the Event log and it points to ntdll.dll. Google says:

"ntdll.dll is a vital Windows system file, containing the NT kernel functions and located in the C:\Windows\System32 directory, crucial for core system operations and should never be deleted."

Perhaps corrupted by a virus? I'm running a full Defender scan now.

Faulting application name: BlueIris.exe, version: 5.9.9.30, time stamp: 0x67d471ca
Faulting module name: ntdll.dll, version: 10.0.26100.3323, time stamp: 0xfacafff0
Exception code: 0xc0000374
Fault offset: 0x000000000008b035
Faulting process id: 0x3BF0
Faulting application start time: 0x1DB980A896A2FFC
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 11e6fe7f-ac7e-4ae7-a434-50251f2113c8
Faulting package full name:
Faulting package-relative application ID:

I worked with BI Support today. I was able to disable all the cameras - after several restart by quickly typing CTRL E to toggle them to the disabled state. I then enabled them one by one and found the culprit.

It was my "trusty" Reolink RLC-410 which is probably 7 years old. Time for a camera refresh.

Strange if that was working and the update then did something to make even the older version of BI flake out?

Strange indeed. Perhaps independent events that happened close in time. Ken has sent me more suggestions for me to try, and perhaps more will be revealed. In any case, I'm retiring that camera.

Wow, another example of a reason to stay away from most Reolink hardware!

I think the learning point from the previous text is that one failing IP camera can pull your entire BI5 system down, so figuring out how to disable them is the key.

TimG, good point, thanks