console can’t connect to process error - v5.2.3.2

balham
Posts: 12
Joined: Tue Mar 31, 2020 9:55 am

console can’t connect to process error - v5.2.3.2

Post by balham »

Hi,

I am getting the "console can’t connect to process" error intermittently using version 5.2.3.2. Once received, the service will not restart though if I reboot, then it will normally start again as a service until the next error time. I've been using BI for some while and never had problems before.

In Windows Event Viewer, the message is:

Faulting application name: BlueIrisService.exe, version: 1.0.0.1, time stamp: 0x5e7d3b1b
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000005
Fault offset: 0x0000000000028e86
Faulting process ID: 0x570
Faulting application start time: 0x01d607324f6c1208
Faulting application path: C:\Program Files\Blue Iris 5\BlueIrisService.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: b0831cd7-c554-4e79-8b14-40c3d30f33c8
Faulting package full name:
Faulting package-relative application

Unfortunately, I don't have any previous installation files though I have now installed the update manager.

Can anyone help please?
AbsoluteWireless
Posts: 3
Joined: Wed Apr 01, 2020 1:19 am

Re: console can’t connect to process error - v5.2.3.2

Post by AbsoluteWireless »

Also getting similar error

Category: Application Crashing Events
Message:
Faulting application name: BlueIris.exe, version: 5.2.3.2, time stamp: 0x5e80ca52
Faulting module name: VCRUNTIME140.dll, version: 14.21.27702.2, time stamp: 0x5ccadaa9
Exception code: 0xc0000005
Fault offset: 0x000000000000127e
Faulting process id: 0xdd0
Faulting application start time: 0x01d607091566fda6
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 9c01ae55-5493-400a-9865-53cb67421a3f
Faulting package full name:
Faulting package-relative application ID:
BruceH
Posts: 38
Joined: Wed Apr 01, 2020 10:10 pm

Re: console can’t connect to process error - v5.2.3.2

Post by BruceH »

I am also getting this error, just upgraded to V5.2.4.2 and it is still happening

When I try to start the console I get this message "Console could not connect to service process (2)"

Event Viewer shows this
The Blue Iris Service service terminated unexpectedly. It has done this 1 time(s).

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7034</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2020-04-01T22:28:44.571246500Z" />
<EventRecordID>144751</EventRecordID>
<Correlation />
<Execution ProcessID="100" ThreadID="6496" />
<Channel>System</Channel>
<Computer>Spare-PC</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">Blue Iris Service</Data>
<Data Name="param2">1</Data>
<Binary>42006C007500650049007200690073000000</Binary>
</EventData>
</Event>
nielk
Posts: 7
Joined: Thu Apr 02, 2020 10:07 am

Re: console can’t connect to process error - v5.2.3.2

Post by nielk »

I had a similar error last week, fixed by rebooting.

Code: Select all

Faulting application name: BlueIrisService.exe, version: 1.0.0.1, time stamp: 0x5e7cb1bb
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000005
Fault offset: 0x0000000000028e86
Faulting process ID: 0x2d4c
Faulting application start time: 0x01d603c85888ff72
Faulting application path: C:\Program Files\Blue Iris 5\BlueIrisService.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 9f1fd65c-8260-41c3-b99d-906a2e517ec1
Faulting package full name: 
Faulting package-relative application ID: 
And again today after updating to BI 5.2.4.2 ...

Code: Select all

Faulting application name: BlueIrisService.exe, version: 1.0.0.1, time stamp: 0x5e7d3b1b
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000005
Fault offset: 0x0000000000028e86
Faulting process ID: 0x2218
Faulting application start time: 0x01d608d43316432c
Faulting application path: C:\Program Files\Blue Iris 5\BlueIrisService.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 2cdb707a-5be3-4b9a-b35c-9fe8007c2c49
Faulting package full name: 
Faulting package-relative application ID: 
balham
Posts: 12
Joined: Tue Mar 31, 2020 9:55 am

Re: console can’t connect to process error - v5.2.3.2

Post by balham »

I too upgraded to the latest version but am still having the same problem.

I can only restart the BI service by rebooting but then I will get another crash several hours later. The same file ntdll.dll seems to be involved.
nielk
Posts: 7
Joined: Thu Apr 02, 2020 10:07 am

Re: console can’t connect to process error - v5.2.3.2

Post by nielk »

Still the same exception in ntdll.dll when upgrading to 5.2.4.4 ...

Code: Select all

Faulting application name: BlueIrisService.exe, version: 1.0.0.1, time stamp: 0x5e7d3b1b
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000005
Fault offset: 0x0000000000028e86
Faulting process ID: 0x27dc
Faulting application start time: 0x01d60a97a50eae09
Faulting application path: C:\Program Files\Blue Iris 5\BlueIrisService.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 45eec270-4fa9-46f2-bd87-ab777c290907
Faulting package full name: 
Faulting package-relative application ID: 
User avatar
Rahaboss
Posts: 4
Joined: Fri Dec 20, 2019 7:48 pm

Re: console can’t connect to process error - v5.2.3.2

Post by Rahaboss »

Getting same error after todays update:
"Console could not connect to service process (2)"

Error in windows 10 event viewer:
Faulting application name: BlueIrisService.exe, version: 1.0.0.1, time stamp: 0x5e7d3b1b
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000005
Fault offset: 0x0000000000028e86
Faulting process ID: 0x2fb8
Faulting application start time: 0x01d60b2aa99d8961
Faulting application path: C:\Program Files\Blue Iris 5\BlueIrisService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: bb36705d-687a-4997-9dc4-3cf50e8e2d4a
Faulting package full name:
Faulting package-relative application ID: 
balham
Posts: 12
Joined: Tue Mar 31, 2020 9:55 am

Re: console can’t connect to process error - v5.2.3.2

Post by balham »

I was about to post this morning that I haven't had any more crashes (as described in the top post), but this morning it crashed again with the same error report. My system has been updating to the latest release - now on 5.2.4.6.
BruceH
Posts: 38
Joined: Wed Apr 01, 2020 10:10 pm

Re: console can’t connect to process error - v5.2.3.2

Post by BruceH »

I also have had this happen on one of my two Windows 10x64 systems running Blue Iris (5.2.4.6) I found it odd that only one of the systems was crashing.; then I noticed that the one that was experiencing the crashes was also running Bitdefender Total Security and the other system was only running the stock Antivirus from Microsoft as it was not exposed to the Internet. I found that if I stopped the Blueiris Service it would not restart without a reboot. I then turned off all of the Bitdefender protection and found that the service had no problems with stopping and starting. After some experimentation I found that all that was required to solve this issue in relation to Bitdefender was the following. In the Exception section of "Advanced Threat Defense" add the program for the "blueirisservice.exe". It must be in the subsection for "Advanced Threat Defense" which requires that you pick the exact program, you can not exclude the entire folder for this to work.

I am sure that other Antivirus programs may also be interfering and causing this problem for other users
balham
Posts: 12
Joined: Tue Mar 31, 2020 9:55 am

Re: console can’t connect to process error - v5.2.3.2

Post by balham »

That's really interesting - I, too, have Bitdefender Total Security so I've done as you suggested (create an exception for the Blue Iris service) and will report back here on the result. Many thanks for this help.
Post Reply