I run Blue Iris as a service.

When I run Blue Iris to get a GUI so I can see my camera feeds, Blue Iris (version 4 and 5) sometimes freezes and I have to exit and reload to get it back so I can see the live video feeds of my cameras again. Fortunately the service seems to keep running and it is still recording video like it's suppose to... but my video feed preview/monitor stops working.

But why is this happening? It happens even after upgrading to 5 and upgrading to a new computer. I thought it might be a bug but if so then it hasn't been fixed in months. I'd say it happens every day or two or three (it varies).

Any ideas? Anyone else experience this issue? Thanks.

CommonSenseAl wrote: ↑Sun Jul 28, 2019 7:14 pm I run Blue Iris as a service.

When I run Blue Iris to get a GUI so I can see my camera feeds, Blue Iris (version 4 and 5) sometimes freezes and I have to exit and reload to get it back so I can see the live video feeds of my cameras again. Fortunately the service seems to keep running and it is still recording video like it's suppose to... but my video feed preview/monitor stops working.

But why is this happening? It happens even after upgrading to 5 and upgrading to a new computer. I thought it might be a bug but if so then it hasn't been fixed in months. I'd say it happens every day or two or three (it varies).

Are there any "blueiris.exe" crash logs in the Windows Event Application log and if so, can you post one? It sounds like the console/app may be crashing, but the BlueIris service is still running. When Blue Iris freezes, can you still connect to the Blue Iris webserver from your web browser (Internet Explorer, Firefox or Chrome)?

There was a memory leak issue with Blue Iris 5 that existed with versions 5.0.0.61, 5.0.0.62, 5.0.0.63, 5.0.0.64, so I would make sure you are not using any of these versions.

Try unselecting "Run as Windows service" in Blue Iris Settings -> Startup tab to see if the problem persists running Blue Iris as an application instead of a service. It may require you to restart your PC. This will help identify whether the problem is related to running Blue Iris as a service.

I would recommend excluding the "C:\Program Files\Blue Iris 5" folder from your Antivirus security suite.

reddawg wrote: ↑Mon Jul 29, 2019 3:25 amAre there any "blueiris.exe" crash logs in the Windows Event Application log and if so, can you post one. It sounds like the console/app may be crashing, but the BlueIris service is still running.

I found this:

Faulting application name: BlueIris.exe, version: 5.0.0.70, time stamp: 0x5d3a75c9
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x3618
Faulting application start time: 0x01d54484c98fc7a0
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3bd676c1-627e-46d2-9027-25d4b39984d8
Faulting package full name:
Faulting package-relative application ID:

- System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2019-07-27T15:54:53.439385600Z
EventRecordID 27851
Channel Application
Computer Z17
Security
- EventData

BlueIris.exe
5.0.0.70
5d3a75c9
ntdll.dll
10.0.17134.799
7f828745
c0000374
00000000000f479b
3618
01d54484c98fc7a0
C:\Program Files\Blue Iris 5\BlueIris.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
3bd676c1-627e-46d2-9027-25d4b39984d8

reddawg wrote: ↑Mon Jul 29, 2019 3:25 amWhen Blue Iris freezes, can you still connect to the Blue Iris webserver from your web browser (Internet Explorer, Firefox or Chrome)?

I can still access my cameras from my mobile devices and the Blue Iris app.

reddawg wrote: ↑Mon Jul 29, 2019 3:25 amThere was a memory leak issue with Blue Iris 5 that existed with versions 5.0.0.61, 5.0.0.62, 5.0.0.63, 5.0.0.64, so I would make sure you are not using any of these versions.

No. The report above says 5.0.0.70.

reddawg wrote: ↑Mon Jul 29, 2019 3:25 amTry unselecting "Run as Windows service" in Blue Iris Settings -> Startup tab to see if the problem persists running Blue Iris as an application instead of a service. It may require you to restart your PC.

I may try that again the next time it happens. Fortunately it doesn't happen THAT often and the service still runs.

Having the same issue very frequently now with BI version 4.8.4.5 x64.
It only started couple of weeks ago and I have no idea what is causing this.
As it seems to happen with BI v5 also, maybe some Windows update might be the reason.

I noticed that after RDPing into a machine it is very likely to happen.

CommonSenseAl wrote: ↑Mon Jul 29, 2019 5:38 am
Faulting application name: BlueIris.exe, version: 5.0.0.70, time stamp: 0x5d3a75c9
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x3618
Faulting application start time: 0x01d54484c98fc7a0
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3bd676c1-627e-46d2-9027-25d4b39984d8
Faulting package full name:
Faulting package-relative application ID:

In other forums, whenever I have seen blueiris.exe appcrashes with faulting module: ntdll.dll, it usually was a problem with Blue Iris. However, from experience the most common causes of ntdll.dll error messages are usually the result of a corrupt or damaged version of ntdll.dll file, corrupted hardware drivers, a bad memory module or issues between Windows and other applications. I would recommend trying the following and see if they help resolving your sporadic crash problem when running BI5 as a service.

1. Windows Updates...I would make sure Windows Updates are up to date.

2. Check and repair any corrupt or damaged Windows operating system files using SFC and DISM by opening an Admin elevated CMD prompt and typing the following:

# SFC /scannow

It should return "Windows Resource Protection did not find any integrity violations" upon no errors.

# DISM /Online /Cleanup-Image /CheckHealth
# DISM /Online /Cleanup-Image /ScanHealth

both should return "No component store corruption detected" upon no errors. If either SFC and any of the DISM commands indicates errors then run the following below.

# DISM /Online /Cleanup-Image /RestoreHealth
# SFC /scannow

3. Re-register ntdll.dll
a) Open an Admin elevated CMD prompt.
b) Type this in command prompt:

# regsvr32.exe /u ntdll.dll (this will unregister it)
# regsvr32.exe ntdll.dll (this will register it)

4. Verify memory using MemTest86 v8.2 Free Edition from a bootable USB flash drive.

If none of these steps help eliminate or identify the problem, I would contact support@blueirissoftware.com.

...

Just released:

5.0.1 - August 1, 2019
After a couple of months spent focusing solely on bug fixes and minor usability
enhancements, we have reached a point of stability that now allows us to continue with
more significant development.

The console now recognizes when the service has crashed and has been restarted. An
automatic reconnection is attempted for seamless use of the console window.

The latest version of the Intel MFX library (2019R1) is now being used. This update was
made in an attempt to bring stability to systems experiencing memory leaks with some
versions of the Intel drivers, and to possibly offer H.265 decoding and (eventually) hardware
encoding using Intel QuickSync.

MikeBwca wrote: ↑Fri Aug 02, 2019 6:37 amThese versions of BI... They are on different computers? Your not shutting down v5 and starting v4 on the same computer - and vice versa, are you?

I was using v4 on an old machine and the problem happened several times. I have since upgraded the machine and moved to v5 at the same time so I do not use v4 anymore.

The problem has not occurred in a few days so I'm hoping whatever it was is resolved (maybe through a BI or Windows update?). If the issue comes back then I will try some of the things reddawg mentioned.

reddawg wrote: ↑Fri Aug 02, 2019 6:37 am Just released:

5.0.1 - August 1, 2019
...
The console now recognizes when the service has crashed and has been restarted. An
automatic reconnection is attempted for seamless use of the console window.
...

Yes, that may be what was happening.... server crashing and the console not reconnecting. I hope that was it!