Console crash after 6-7 uses.

[looney2ns]

I've emailed Ken about this, just curious if anyone has had this issue or ideas as I await a reply.

Bi 4.6.3.0 run as a service.
Close console after each use.

On the 6th or 7th attempt to start the console, it will crash at the splash screen.

The service has to be stopped, and restarted before I can get the Console to run again.

When I do get it to run after one of these crashes, BI has added a camera called Motion, and of course has no signal.

Windows reports this in events:
Faulting application name: BlueIris.exe, version: 4.6.3.0, time stamp: 0x59dd477d
Faulting module name: BlueIris.exe, version: 4.6.3.0, time stamp: 0x59dd477d
Exception code: 0xc0000005
Fault offset: 0x0000000000ea90a6
Faulting process id: 0x1d04
Faulting application start time: 0x01d349101559dfb5
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 4\BlueIris.exe
Report Id: 80f4a89e-25c7-4bab-84b6-521d55fa6d12
Faulting package full name:
Faulting package-relative application ID:

Thanks.

 

[Q™]

Have you tried downgrading Bi to determine if the issue no longer manifests with an earlier version?

 

[NoloC]

Why do you close the console? I thought that was a dedicated BI machine? Does it make a significant difference on cpu usage?

I know that's kind of like the old joke "Hey Doc it hurts when I do this" "Well don't do that"

 

[looney2ns]

Why do you close the console? I thought that was a dedicated BI machine? Does it make a significant difference on cpu usage?

I know that's kind of like the old joke "Hey Doc it hurts when I do this" "Well don't do that"

It is a dedicated machine.
Yes it does make a difference in cpu, drops from 30-40% to less than 20%.

No Q, I haven't tried a downgrade.

 

[NoloC]

So I went to my 7040 to take a look and agree it makes a significant difference. But I rarely look at that machine and now see the ram and cpu have crept up. Must be the Intel Driver badness. Guess I'll have to search for those old threads to see how you guys fixed it with new graphics drivers IIRC.

It was fine for the last 6 months. Weird. I think I caught it from being in the same thread with you and Q.