I'm at bit at my wits end with this. I've already emailed support but wondered if anyone else had experienced this.
About 48hrs after I first installed Blue Iris v5, which was working perfectly fine, I woke up to find it wasn't working. Checking I found that my service was going Starting > Running > Stopped over and over, but no luck. I disabled the service and tried to debug it, uninstalling, reinstalling, rebooting, etc. Eventually I tried deleting the registry entry and this allowed it to launch. I tried restoring the settings and it went right back to crashing again. I then reinstalled Windows fresh and set everything up again from scratch. It was working fine for around 48hrs again and has just crashed with the same issue.
It's an entirely fresh and up to date Windows 10 build, has DeepStack on it and nothing else. Only three cameras, nothing at all fancy, and my monitoring says that it's not been in any way over taxed. I'm entirely at a loss as to what could be calling this and am a bit heartbroken since it's proven to be such a better system than what I'm used to so far. The crash reports don't tell me much, unfortunately..
Problem signature
Problem Event Name: APPCRASH
Application Name: BlueIris.exe
Application Version: 5.4.7.11
Application Timestamp: 60c3cf97
Fault Module Name: BlueIris.exe
Fault Module Version: 5.4.7.11
Fault Module Timestamp: 60c3cf97
Exception Code: c0000005
Exception Offset: 00000000010b2fbe
OS Version: 10.0.19042.2.0.0.256.4
Locale ID: 2057
Additional Information 1: 28d2
Additional Information 2: 28d234a5e6c8ba930b84c9a8794e1613
Additional Information 3: b4c0
Additional Information 4: b4c0a783b1747de41592ce65fd197505
I just set it up fresh for the 3rd time. Got everything working, then closed it and re-opened it and found that the same issue was occurring.
I wiped the registry again and since I'd made a back-up before doing anything else I restored the backup which caused the issue to resume.
Since the issue had presented itself after crashes the first two times when it had been running as a service already, it seems like it's something happening after the cameras are added and set up.
About 48hrs after I first installed Blue Iris v5, which was working perfectly fine, I woke up to find it wasn't working. Checking I found that my service was going Starting > Running > Stopped over and over, but no luck. I disabled the service and tried to debug it, uninstalling, reinstalling, rebooting, etc. Eventually I tried deleting the registry entry and this allowed it to launch. I tried restoring the settings and it went right back to crashing again. I then reinstalled Windows fresh and set everything up again from scratch. It was working fine for around 48hrs again and has just crashed with the same issue.
It's an entirely fresh and up to date Windows 10 build, has DeepStack on it and nothing else. Only three cameras, nothing at all fancy, and my monitoring says that it's not been in any way over taxed. I'm entirely at a loss as to what could be calling this and am a bit heartbroken since it's proven to be such a better system than what I'm used to so far. The crash reports don't tell me much, unfortunately..
Problem signature
Problem Event Name: APPCRASH
Application Name: BlueIris.exe
Application Version: 5.4.7.11
Application Timestamp: 60c3cf97
Fault Module Name: BlueIris.exe
Fault Module Version: 5.4.7.11
Fault Module Timestamp: 60c3cf97
Exception Code: c0000005
Exception Offset: 00000000010b2fbe
OS Version: 10.0.19042.2.0.0.256.4
Locale ID: 2057
Additional Information 1: 28d2
Additional Information 2: 28d234a5e6c8ba930b84c9a8794e1613
Additional Information 3: b4c0
Additional Information 4: b4c0a783b1747de41592ce65fd197505
I just set it up fresh for the 3rd time. Got everything working, then closed it and re-opened it and found that the same issue was occurring.
I wiped the registry again and since I'd made a back-up before doing anything else I restored the backup which caused the issue to resume.
Since the issue had presented itself after crashes the first two times when it had been running as a service already, it seems like it's something happening after the cameras are added and set up.