BI crashing windows 10 every couple of hours

[Frank]

Hi,

So I upgraded my windows 7 nvr to window 10 and now BI is constantly crashing, I can't even load it back up until restarting the machine. I gather the following eventlog maybe someone had same problem and found a fix.

Faulting application name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Faulting module name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Exception code: 0xc0000005

 

[gsxr1181]

Whats your system specification? Is it running an Intel graphics card by chance?

 

[fenderman]

Search forum for memory leak.. Also always do a clean install of Windows

 

[Frank]

I first upgraded and was crashing, so I went ahead and did a clean install but didn't fix anything.

I'm using the following.

i5-3570k CPU 3.40ghz
32GB RAM
I had an external vcard but it was recommended in this forum to use builtin intel vcard to turn on hardware

 

[fenderman]

I first upgraded and was crashing, so I went ahead and did a clean install but didn't fix anything.

I'm using the following.

i5-3570k CPU 3.40ghz
32GB RAM
I had an external vcard but it was recommended in this forum to use builtin intel vcard to turn on hardware

Check to see if memory use is constantly increasing..If so it's a leak..

 

[gsxr1181]

I first upgraded and was crashing, so I went ahead and did a clean install but didn't fix anything.

I'm using the following.

i5-3570k CPU 3.40ghz
32GB RAM
I had an external vcard but it was recommended in this forum to use builtin intel vcard to turn on hardware

OK, I should have asked what Intel driver your running. Take you external card, and install it with Win10 drivers. Disable your internal graphics card and see if it goes away. If so your bitten by the Intel driver bug.

I had a system that was running Win7 flawlessly for years, and decided to upgrade to Win10 since it was new and shinny. I was getting an instant crash with the same exception code. Fresh installed till the cows came home with same result. After doing some digging, I found it was a video driver issue. Come to find out there is a bug with the Windows 10 Intel HD driver set.

Basically Intel says there driver is fine, and its a problem with Windows 10. Microsoft says it's a Intel driver issue. So I don't know if it's been fixed, but 6 months ago it wasn't. Just two companies finger pointing. Even different versions didn't work. But if you go to Intel's forum and search Windows 10 driver bug, you will have lots of reading. If I remember right that 0xc0000005 is an access code violation, which basically means a driver or program is trying to access data in RAM outside it's allocated memory stack. So Windows see's this violation, and closes the program to prevent stack overflows. <------ I could completely wrong on some of this, but that's what I kinda remember reading.

I decided to go back to Windows 7, and was problem free and rock solid. Sometimes new isn't better. So if you need 10 for any reason, you will probably need to stick to your external card. But I suggest go back to Windows 7 and be stress free.

Just to reference my system is an i5-4690 with a Asus Sabertooth 990fx using the Intel HD 4600 internal graphics. Windows 7 and 8.1 worked just fine, but Windows 10 wouldn't have any of it.

 

[fenderman]

You can test for the memory leak without using the card....simply disable hardware acceleration....
I can further assure you that its not related to windows 10 as I have 20+ blue iris machines running w10

 

[Frank]

memory is always at a steady 17-19%\

I just disabled hardware acceleration and restarted, gonna run it for while see how it behaves.

 

[Frank]

No luck, still crashing even with hardware acc turned off and memory still at 17-19%

 

[fenderman]

No luck, still crashing even with hardware acc turned off and memory still at 17-19%

likely unrelated...what does event viewer show?

 

[Q™]

I had a Blue Iris crash problem recently. Turns out I had resent some of my cameras to the camera firmware default, which reset the camera to h.265 codec. Turns out that Blue Iris crashes when recording Direct-To-Disk in h.265. It took me a long friggin' time to figure that one out. Once I reset each camera to h.264 the crashing ceased. Not saying that this is your problem, but knowing this may help someone sometime.

 

[fenderman]

I had a Blue Iris crash problem recently. Turns out I had resent some of my cameras to the camera firmware default, which reset the camera to h.265 codec. Turns out that Blue Iris crashes when recording Direct-To-Disk in h.265. It took me a long friggin' time to figure that one out. Once I reset each camera to h.264 the crashing ceased. Not saying that this is your problem, but knowing this may help someone sometime.

I think that issue was resolved...

 

[Frank]

Interesting enough I've witness 2 crashes and multiple cameras go offline before crashing, no specific pattern.

Event view shows the following.

Faulting application name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Faulting module name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Exception code: 0xc0000005
Fault offset: 0x00000000007d9599
Faulting process id: 0x444
Faulting application start time: 0x01d280a054d1f58a
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 4\BlueIris.exe
Report Id: e261f58d-c5eb-424c-9c4b-afec070094ae
Faulting package full name:
Faulting package-relative application ID:

 

[fenderman]

Interesting enough I've witness 2 crashes and multiple cameras go offline before crashing, no specific pattern.

Event view shows the following.

Faulting application name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Faulting module name: BlueIris.exe, version: 4.5.0.2, time stamp: 0x5893542c
Exception code: 0xc0000005
Fault offset: 0x00000000007d9599
Faulting process id: 0x444
Faulting application start time: 0x01d280a054d1f58a
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 4\BlueIris.exe
Report Id: e261f58d-c5eb-424c-9c4b-afec070094ae
Faulting package full name:
Faulting package-relative application ID:

I would email that info to support

 

[Frank]

I did but sadly they aren't of much help, I may end up buying a new pc.

 

[fenderman]

I did but sadly they aren't of much help, I may end up buying a new pc.

That seems silly..test the memory...when you did a clean install did you use the microsoft media creation tool?

 

[Frank]

No, I downloaded and installed from a CD a fresh windows 10 pro

 

[fenderman]

No, I downloaded and installed from a CD a fresh windows 10 pro

run memtest on your memory....and/or test with only 8gb..

 

[ldasilva]

turn off blue iris and test the computer
use Cinebench and memtest Prime95 if fail take out 1 stick of mem still fail take out another stick still fail swap sticks if no fail you found your problem

this will take a while to test

 

[GBJames]

I had similar crashing issues which stopped when I set BI to run as a service.