BI will no longer start - exception 0xc0000005

[Tygunn]

So, yesterday BI started acting up. All my cameras were going offline at random. When I went to check what was up, I noticed BI had an update pending to 5.3.3.13, so I installed it. At that point BI would run and then I've get a dialog indicating that the BI service had stopped. At this point the BI UX stops. With no valid point forward I simply uninstalled BI and reinstalled 5.3.3.13 (no biggie; BI is easy to install).

However, now the problem is worse. When I run BI the startup splashscreen gets to the point of saying, "extracting UI3" and then just goes away. I see this app error in the windows event log.

Confirmed permission is set so admins have full control over the BI folder, etc, etc.

Kinda stumped at this point.

This is why I REALLY wish BI was not a Windows app. I'm sure the next step is to reformat the machine and reinstall Windows 10... because that's how things in Windows are always solved.
Emailed BI support since I pay for it; we'll see what they say. Maybe someone else has an idea?

Log Name: Application
Source: Application Error
Date: 11/3/2020 9:52:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-89CE0FJ
Description:
Faulting application name: BlueIris.exe, version: 5.3.3.13, time stamp: 0x5f9f2738
Faulting module name: BlueIris.exe, version: 5.3.3.13, time stamp: 0x5f9f2738
Exception code: 0xc0000005
Fault offset: 0x00000000010f1f74
Faulting process id: 0x1870
Faulting application start time: 0x01d6b26eb83bbf85
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 5\BlueIris.exe
Report Id: ae0aa595-48ce-4148-9bd1-2f9713fb2563
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="

http://schemas.microsoft.com/win/2004/08/events/event

">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-04T05:52:48.370475800Z" />
<EventRecordID>14337</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-89CE0FJ</Computer>
<Security />
</System>
<EventData>
<Data>BlueIris.exe</Data>
<Data>5.3.3.13</Data>
<Data>5f9f2738</Data>
<Data>BlueIris.exe</Data>
<Data>5.3.3.13</Data>
<Data>5f9f2738</Data>
<Data>c0000005</Data>
<Data>00000000010f1f74</Data>
<Data>1870</Data>
<Data>01d6b26eb83bbf85</Data>
<Data>C:\Program Files\Blue Iris 5\BlueIris.exe</Data>
<Data>C:\Program Files\Blue Iris 5\BlueIris.exe</Data>
<Data>ae0aa595-48ce-4148-9bd1-2f9713fb2563</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

 

[SouthernYankee]

Stop automatically installing updates. this is for windows and BI.

I believe the current stable update is 5.3.2.11

Blue Iris Software Updates

ipcamtalk.com

 

[Tygunn]

Stop automatically installing updates. this is for windows and BI.

I believe the current stable update is 5.3.2.11

Blue Iris Software Updates

ipcamtalk.com

Doesn't help that both WIndows and BI both are set up assuming you're going to update things, so it seems both parties need to put more effort into supporting the model they extol. Nowhere in the BlueIris documentation does it say you should leave the OS and Blueiris executable in a static state; that's just a bandaid on a faulty OS and software implementation.

Sure doesn't help that BI doesn't actually offer older versions on their website.
5.3.0.2 also does not work (which is a version I had an installer for).

 

[fenderman]

Doesn't help that both WIndows and BI both are set up assuming you're going to update things, so it seems both parties need to put more effort into supporting the model they extol. Nowhere in the BlueIris documentation does it say you should leave the OS and Blueiris executable in a static state; that's just a bandaid on a faulty OS and software implementation.

Sure doesn't help that BI doesn't actually offer older versions on their website.
5.3.0.2 also does not work (which is a version I had an installer for).

Common sense tells you that you should not update bi Until you have confirmed that the release is stable we’ve discussed this many many times that blue Iris is not designed for people with OCD who cannot do this the developer chooses to give you the option to update. I have over 20 blue Iris machines with zero issues. Those machines receive windows updates as well with no problems nine times out of 10 these issues are caused by user error. If you want to blame blue Iris and windows there are plenty and by that I mean hundreds of other options for a VMS. The developer went out of his way to indicate which releases are stable releases yet the OCD persists.

 

[Tygunn]

Common sense tells you that you should not update bi Until you have confirmed that the release is stable we’ve discussed this many many times that blue Iris is not designed for people with OCD who cannot do this the developer chooses to give you the option to update. I have over 20 blue Iris machines with zero issues. Those machines receive windows updates as well with no problems nine times out of 10 these issues are caused by user error. If you want to blame blue Iris and windows there are plenty and by that I mean hundreds of other options for a VMS. The developer went out of his way to indicate which releases are stable releases yet the OCD persists.

It's nothing to do with OCD, it's a matter of running into a routine issue and trying to resolve it. BI was flaking and reporting cameras were losing signal. Restarted the computer and the cameras with no effect. Tried updating with the hopes of fixing; no dice. So I tried re-installing from scratch; that doesn't work. Tried using 5.3.0.2 (which did work before) but that does not work either. Clearly something changed on this PC, and I'd love to know what. This is not a computer I'm using for any other purpose; it literally sits behind a desk vacuuming up dust.

Time to reformat. This time around I'll make a system image when I do.

 

[sebastiantombs]

Better idea, shut off Windows updates and BI updates so you can pick and choose. There are several threads about doing this. The main reason to stop Win10 from updating is the video driver, especially if you're using hardware acceleration.

 

[Tygunn]

Better idea, shut off Windows updates and BI updates so you can pick and choose. There are several threads about doing this. The main reason to stop Win10 from updating is the video driver, especially if you're using hardware acceleration.

Sure, great; I just reformatted the PC and re-installed Windows 10.

Both BI 5.3.0.2 (old copy I had kicking around) and 5.3.3.13 (downloaded off internet) fail in the EXACT same manner.

 

[sebastiantombs]

Yup, has to be Win10 and BI, can't be anything else, obviously. Thousands of copies of BI running on Win10 with no problems, my own included. Can't be a hardware problem or driver conflict, has to be the OS and BI.

 

[Tygunn]

In an effort to make this discussion thread helpful to people who may experience this problem in the future.

It appears the root cause of the problem is a corrupted registry entry for Blue Iris related to my previous installation.
I had restored from a BI backup file to get things going and the crash happened immediately.

I used the following steps to remove the BI registry entries:

1. Open a CMD prompt with Run as Administrator privileges.
2. Type: reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Perspective Software" /f.
3. Run Blue Iris or start BlueIris service.

Latest version of BlueIris now runs as expected. I'm able to re-add my cameras manually with no issues.

As a software engineer it's exactly as I expected; software issue. No software is perfect and there is always a bug somewhere in the waiting.
Once BI support gets back to me I will send them my broken backup file so they can take a look and determine the root cause.

I hope this can help someone out!

 

[fenderman]

It's nothing to do with OCD, it's a matter of running into a routine issue and trying to resolve it. BI was flaking and reporting cameras were losing signal. Restarted the computer and the cameras with no effect. Tried updating with the hopes of fixing; no dice. So I tried re-installing from scratch; that doesn't work. Tried using 5.3.0.2 (which did work before) but that does not work either. Clearly something changed on this PC, and I'd love to know what. This is not a computer I'm using for any other purpose; it literally sits behind a desk vacuuming up dust.

Time to reformat. This time around I'll make a system image when I do.

windows has a system restore function.

 

[Tygunn]

windows has a system restore function.

Yes, that's true, good point.

I guess in this case I'd have been out of luck since my last BI settings backup was broken.....
I will have to retain a backup of that from once I get everything set up again.

 

[Tygunn]

So I did hear back from Ken at Blue Iris regarding my Blue Iris configuration. I had configured an MQTT server in my BI configuration. The MQTT server apparently was not responding and this is the cause of the crash when I was trying to start Blue Iris.
Ken mentioned if the MQTT server is on the same computer as BI this is not typically a problem. In my case I run MQTT on a HomeAssistant device running on a PI on my network, so I can see how it could occasionally glitch out. In my case I'm just going to move to using the web APIs for now instead of MQTT.

 

[Kameraad]

Never would have guessed that! I run a mqqt server (mosquitto) in a docker container, on a ubuntu vm on my proxmox server. I never ran into issues. Maybe worth checking your PI if its having some problems?

 

[Tygunn]

Never would have guessed that! I run a mqqt server (mosquitto) in a docker container, on a ubuntu vm on my proxmox server. I never ran into issues. Maybe worth checking your PI if its having some problems?

Yeah, it's really strange I use MQTT for some other stuff and the PI has never caused any troubles. It always "just works". I'm not sure why it failed in this case....
In any case I consider BI to be a "mission critical" app, where my home automation stuff isn't. So I will ensure I don't mix the two service.