Faulting module name: VCRUNTIME140.dll,

adehaan86

Young grasshopper
Joined
Nov 14, 2018
Messages
56
Reaction score
2
Location
US
Blue Iris Appears to crash at 2 am . Its happening more and more as of lately and unsure why.

I have tried reinstalling vcruntime140 but that helps for maybe a week or 2. Any ideas what I may be missing?


Faulting application name: BlueIris.exe, version: 5.1.0.1, time stamp: 0x5e4ef722
Faulting module name: VCRUNTIME140.dll, version: 14.21.27702.2, time stamp: 0x5ccadaa9
Exception code: 0xc0000005
Fault offset: 0x000000000000127e
Faulting process id: 0x1fcc
Faulting application start time: 0x01d5ec27a7496687
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: fa0d07c6-a133-4a4b-9a6e-01baf0ce5f83
Faulting package full name:
Faulting package-relative application ID:
 

IAmATeaf

Known around here
Joined
Jan 13, 2019
Messages
1,425
Reaction score
736
Location
United Kingdom
I’ve been getting something similar, logged a call with Ken and then soda law it stopped so am waiting for the next crash so that I can maybe examine the crash log files.
 

SouthernYankee

IPCT Contributor
Joined
Feb 15, 2018
Messages
3,543
Reaction score
2,411
Location
Houston Tx
seethe following post and see if that helps
 

bp2008

Staff member
Joined
Mar 10, 2014
Messages
10,063
Reaction score
7,651
Location
USA
Well a fault while the program was executing code in vcruntime140.dll does not mean that dll was at fault. It just means that is the code which experienced the crash. Which doesn't narrow anything down at all, unfortunately.
 

bp2008

Staff member
Joined
Mar 10, 2014
Messages
10,063
Reaction score
7,651
Location
USA
The exception code 0xc0000005 indicates a memory access violation. That most likely means you've found a programming bug in Blue Iris (good luck figuring out the exact cause though). It could also unfortunately be the fault of any third-party code Blue Iris uses, or it could be your PC hardware's problem.
 

IAmATeaf

Known around here
Joined
Jan 13, 2019
Messages
1,425
Reaction score
736
Location
United Kingdom
This is going to sound stupid but for me certainly it now looks like I only get this error when there is an update. So today I had it which coincided with when BI did an update.

When I logged the problem with Ken I was getting BI crashing whilst I was reviewing recorded footage, the entire app would crash and then restart but checking yesterday it no longer seems to be doing this but last time I noticed this I was reviewing hours of footage looking a particular silver car
 

eladbar

n3wb
Joined
Mar 1, 2020
Messages
2
Reaction score
0
Location
IL
I have the same issue since that version, talked with Ken from BI, suggested to do driver updates, remove HW accel (I'm using NVidia encoding),
Seems that the real issue is with nightly job running every night at 2:00.

In addition, I have weird error message in BI logs:
Setup failed: 483 for 'recording 0'

It's related to profile "recording 0" which is being activated when BI is reencoding the file and not saving direct to disk,
I'm working with direct-to-disk which raises the questions - why it happens...

Event log message for BI crash:
Faulting application name: BlueIris.exe, version: 5.2.4.6, time stamp: 0x5e8b8378
Faulting module name: VCRUNTIME140.dll, version: 14.21.27702.2, time stamp: 0x5ccadaa9
Exception code: 0xc0000005
Fault offset: 0x0000000000001534
Faulting process ID: 0x1164
Faulting application start time: 0x01d6117f4ed56ef6
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report ID: f8ebf521-2a93-4843-a7b4-b6146c15ecc9
Faulting package full name:
Faulting package-relative application ID:
 
Top