Blue Iris Constantly Crashing

SeymourIT

n3wb
Jan 13, 2025
8
1
Canada
Hi there,

I work for a business who has been using the blue iris software for several years now, and at this point we are considering switching software. If we are able to fix the issues we have (or if its the software, then if an update will fix them) we will be happy to continue to pay for blue iris. Infact, because we rely on blue iris for the security of our business so much, we wouldn't mind paying more for the software.

I realize this forum isn't the official blue iris forum, nor are the developers for it here, but I am out of ideas on how to get this software to stop crashing. Im hoping someone here can help point out why this is happening.

What works and doesn't crash:
-the webserver software that blueiris runs for users to log in and view the cameras that are assigned to them and their group. this software is stable, although I am often worried about how secure it is for web facing servers

-the recordings are often fine, but what clips get recorded to what HDD and in what folder is not very intuitive, but for the most part, this part of the software works

-the AI integration works. when we had codeproject.ai integrtated it would work fantastic

-encoding to different formats works as long as there is enough cpu and gpu resources, but this is almost never done

-windows itself and other windows services are stable and do not cause issues as far as we can tell

-almost everything else, works except for the crashing



What crashes and when it crashes:

When we remote into blue iris or when we are infront of the actual computer and we bring up the blue iris admin interface, this is generally when it crashes. A few years ago, when we first started adding cameras it worked great. We knew from the start of this project that we would need a decently powerful server for the amount of feeds and how much we wanted to record. Here are the specs of our server:

Supermicro Server
RAM: DDR3 ECC buffered 1333Mhz, 128GB total
CPU: intel xeon E5-2687W @3.10 Ghz x2 (two CPUs, 64GB of ram per CPU)
GPU: nvidia Quadra k1200 x2 - used for encoding sometimes if we need them, but they remain unused otherwise. the CPU does most of the work

HDDs:
C: drive - intel D3-S4610 series 800GB SSD - used for the OS and the instal of blue iris only. (originally we were using windows 10 pro, but changed to windows server 2019. performance was better but it still crashed.)
D drive through to K drives - Seagate Seahawk 16TB drives
L: drive - NVMe Samsung 1tb drive (this was added wen we realized that the database was slowing down the performance of the computer, we though by adding the blueiris database to a super fast NVMe drive that it would stop it from crashing and make things faster. It made blueiris start up faster, and do clip lookups faster, but it did not help the crashing)

We thought it might have been the NIC not giving it enough bandwidth for the amount it needed, so we tried setting up Link Aggregation with the 4 port server NIC card that was installed in it, but we noticed that it was dropping packets, so we just use 1x regular 1gbps NIC. We have tried several different types of NICs, PCI, PCI-e and even usb3 ones and it makes no difference.

Other services running on the computer: None. We did have CodeProject.AI running on it for the ALPR, but we removed that when trying to figure out what makes it crash and have not yet put it back on. It is running on a fully updated version of windows and an up to date version of blue iris.

Almost never does the CPU usage get anywhere near 100%.. or even near 60%. The same goes for the RAM.

We have thoroughly tested the hardware. We did 2 full passes over a full week to test out all the ram the last time we upgraded it, and as far as we can tell theres nothing wrong with the motherboard or CPUs.

We monitor the HDDs constantly, looking for any errors or signs of bad sectors or the like. Occasionally one of the spinning Seagate drives die, but thats to be expected. Whenever they die we replace them with Seagate Skyhawk drives of the same size or larger.

The server has dual power supplies and a battery backup with a feature that is supposed to give it clean power all the time. It is in a server room with other servers with air conditioning so we know its not overheating, plus we watch the IMPI sensors for that sort of thing. Infact we often go through the event logs looking for hardware issues and other reasons this might occur with no results.

How we have blue iris set up:

As far as I know there really arnt any settings that can make the whole thing unstable.

We have a total of 35 cameras currently set up, mostly axis cameras. We have them all to record straight to disk without re-encoding. We have set all their framerates low, some of them at 10, some lower. The cameras themselves all have sub streaming set up at the lowest bandwidth settings possible with the default settings on the main stream.

It crashes whenever we click anywhere in the main GUI of the blue iris admin control panel, weather it is to zoom out of a camera to view all of the cameras, or when we go to right click and to add a new camera, or when we try to double click or right click on a n existing camera to change settings it will first hang and turn gray. at this point, if it does this and stays this way for any longer than 3 seconds it will hang for sure.

When blueiris hangs we have to kill it from the task manager in order to re-launch it.

About half the time when we do that it will work for a few clicks to add or edit a camera, but the other half the time we need to kill it again and re-start the service.

No additional windows server have been added. For backups we make a weekly backup of the system drive and of the blueiris database. We occasionally make backups of the settings on blueiris as well. What im saying is that its not backups that are causing it to crash, the backups only take about a half an hour once a week to complete. the recordings are not important enough for us to retain them. Retention of the videos, by the way, is set to 23 days maximum before simply getting deleted. By choosing this short retention period it looks like the huge amount of storage we invested into this machines isn't at all being used.

We require adding more cameras but at this point its very difficult too. We have contacted support for this in the past and they always come out with an update that sometimes works for a bit then breaks, or simply does not work for our issue at all. We are going to attempt to contact them again for advice, but i was hoping maybe someone here can give me some ideas.

It has gotten to the point where we are now installing microSD cards in all of the cameras because whenever the crashing happens it screws up the recordings to disk. Sometimes if we close blueiris from the task manager and then restart the service and dont launch the UI... THATs when it can remain stable for a long time,, but often we require logging into the admin panel on the computer

Does anyone else experience this? Is there a solution to this? If so, what is it? better hardware? A more powerful GPU? Different software?

Thank you for any help
 
Have you cleaned the gold edge connectors on the memory?

It's pretty humid where I live and I recall I have had to remove some RAM on a few PC's and laptops, and even video cards, clean the card edges on both sides gently with a Pink Pearl eraser, blow off the rubber, re-insert and all was good.....

Gold will oxidize a little under the right conditions so it's easy to see how the slightest amount of oxide on a gold finger that's passing probably only nano-amperes of current will be affected. Big currents can more easily pass through high resistance but tiny currents cannot.

Add excessive ambient cigarette smoke, dust and vapors from plastics and vinyls curing (the "new car smell" scenario) and it can add up.

Not saying this happens a lot, even in the humid SE but I have experienced it.

The softer the pink eraser, the better. Keep it in a closed, plastic bag away from the air as much as possible so it won't harden.

NOTE:
Risk of static damage can be much higher in the winter, but any time I would use a grounded wrist strap and ground the PC chassis before starting. Place PC on a table. Wear only cotton clothing. Don't do in a room with carpet. Don't touch the memory gold fingers except with the eraser. Be easy, don't press too hard, better to clean with more passes and less pressure. Gently wipe the cleaned card edge with facial tsssie or toilet paper to remove any rubber residue.

Pink-Pearl_eraser.jpg
 
Last edited:
If you're sure the memory is the correct choice for that motherboard and if the above provides no joy, consider replacing the memory. :cool:
 
Try a different version of the intel graphics driver perhaps? or see if an update changed the version with an intel update.
try moving some of the cameras to Nvidia NVDEC hardware decode and free up the intel graphics unit(s) from some of the load.
 
Have you clenaed the gold edge connectors on the memory?

I worked in an organization that designed and built PC cards and peripherals. This was back in the 286/386 days. We had all the latest equipment like fancy 100+ channel logic analyzers. I was always in disbelief when in this environment, the solution to a problem was to attack the contacts on a board with a pink eraser, against common wisdom and instincts. It was the go-to thing to try before escalating to higher levels of troubleshooting.
 
I worked in an organization that designed and built PC cards and peripherals. This was back in the 286/386 days. We had all the latest equipment like fancy 100+ channel logic analyzers. I was always in disbelief when in this environment, the solution to a problem was to attack the contacts on a board with a pink eraser, against common wisdom and instincts. It was the go-to thing to try before escalating to higher levels of troubleshooting.

It never ceases to amaze me how often the solution to problems with electrical and electronic devices is not a complicated, high-tech component failure but a mechnical issue that causes intermittant operation, voltage drop and corrosion issues from the resulting temperature increase; add to that more mechanical issues caused by ambient temperature fluctuations, local vibrations and even strong audio harmonics. :cool:
 
Hi there,

Thank you for all the replies regarding my issue.

Lets just assume that its not oxidization of the leads of the RAM for now. We upgraded the ram from 64GB to 128GB of the correct ECC ram for this particular supermicro server motherboard not long ago and the reason we upgraded was because the more cameras we added the more often we seen it crash when using the admin GUI. This seamed to help a little bit but blue iris is still constantly crashing. It is particularly annoying when trying to modify or add a new camera.

In the windows log files we dont see any errors that stand out, other than the ones showing blue iris crashing.. We have checked all of the HDDs and they show no smart errors, nor do they show any errors in the windows event logs that might suggest they are failing in any way.

My question to those on this forum: have you noticed any degradation of blue iris with the more cameras that you add? This seams to be what the issue is, possibly. Does anyone here have more than 50 IP cameras connected to blue iris without blue iris crashing? Right now it seams impossible for us to install any more cameras, let alone even modify the ones that we already have without it crashing.

Here are a few of the errors in the windows system logs that we see:

event 1000:
Faulting application name: BlueIris.exe, version: 5.9.9.21, time stamp: 0x678722a1
Faulting module name: ucrtbase.dll, version: 10.0.17763.6189, time stamp: 0xbc3e3f37
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x6fc
Faulting application start time: 0x01db69221af33bb4
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 8e139e3f-cfe9-40bc-8dc9-f7b28751658f
Faulting package full name:
Faulting package-relative application ID:



Faulting application name: BlueIris.exe, version: 5.9.9.19, time stamp: 0x6771bc82
Faulting module name: BlueIris.exe, version: 5.9.9.19, time stamp: 0x6771bc82
Exception code: 0xc0000005
Fault offset: 0x00000000010dff00
Faulting process id: 0x29e0
Faulting application start time: 0x01db5d57adfaf210
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 5\BlueIris.exe
Report Id: 562a1476-b4ec-48e6-ad97-8649c3c8004e
Faulting package full name:
Faulting package-relative application ID:


event 1002
The program BlueIris.exe version 5.9.9.14 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 30d8
Start Time: 01db4f3577a99ba4
Termination Time: 4294967295
Application Path: C:\Program Files\Blue Iris 5\BlueIris.exe
Report Id: 0dda6aa0-e3c9-490c-894a-b299bfa8cef4
Faulting package full name:
Faulting package-relative application ID:
Hang type: Top level window is idle
 
How many drives are capturing the data streams?
what is the processor? does it have onboard video?
 
Hi there Flintstone61,

There are 10 drives total. drive C: is an intel datacenter 800GB drive that is meant to only be for the OS and the program files.
drives D through K are all 16TB or 18TB Seagate seahawk drives that are meant for the cascading of clips... so thats a total of 8 spinning disk drives for the streams.

One they reach drive K they get deleted.

Clips are only stored for a total of 23 days.


drive L: is a Samsung nvme drive for blueiris database and nothing more. ....
The crashing had been occurring since before the installation of the nvme drive so we dont think its that, and it has sped up the ability to search for clips.

nothing in the log files points to any issues with drive D through K, or drive C or L either as far as I can see (in regards to blue irirs crashing, anyways)

I just did an exact count of the cameras..

41 cameras are IP cameras, 39 of them are expected to record continuously 24/7
1 USB camera that does not record at all

2 IP cameras are expected to simply take pics when they detect any kind of motion.

all codeproject.ai software and python have been removed for troubleshooting of this issue.

the server is a supermicro
System Model X9DAX

dual CPU.. so 2 of these:
Processor Intel(R) Xeon(R) CPU E5-2687W 0 @ 3.10GHz, 3101 Mhz, 8 Core(s), 16 Logical Processor(s)

here are the specs for the integrated graphics and the nvidia cards:

Name NVIDIA Quadro K1200
PNP Device ID PCI\VEN_10DE&DEV_13BC&SUBSYS_1140103C&REV_A2\4&67C51EA&0&0018
Adapter Type Quadro K1200, NVIDIA compatible
Adapter Description NVIDIA Quadro K1200
Adapter RAM (1,048,576) bytes
Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nvwu.inf_amd64_df7f0c05c5ae4504\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvwu.inf_amd64_df7f0c05c5ae4504\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvwu.inf_amd64_df7f0c05c5ae4504\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvwu.inf_amd64_df7f0c05c5ae4504\nvldumdx.dll
Driver Version 31.0.15.1640
INF File oem4.inf (Section004 section)
Color Planes Not Available
Color Table Entries Not Available
Resolution Not Available
Bits/Pixel Not Available
Memory Address 0xDD000000-0xDE0FFFFF
Memory Address 0xC0000000-0xD1FFFFFF
Memory Address 0xD0000000-0xD1FFFFFF
IRQ Channel IRQ 4294967201
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVWU.INF_AMD64_DF7F0C05C5AE4504\NVLDDMKM.SYS (31.0.15.1640, 41.66 MB (43,683,824 bytes), 11/3/2023 6:17 PM)

Name Microsoft Basic Display Adapter
PNP Device ID PCI\VEN_102B&DEV_0532&SUBSYS_070E15D9&REV_0A\4&53C375E&0&18F0
Adapter Type Matrox Graphics Inc., (Standard display types) compatible
Adapter Description Microsoft Basic Display Adapter
Adapter RAM 0 bytes
Installed Drivers Not Available
Driver Version 10.0.17763.1
INF File display.inf (MSBDA section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1024 x 768 x 1 hertz
Bits/Pixel 32
Memory Address 0xD3000000-0xD3FFFFFF
Memory Address 0xDF000000-0xDF003FFF
Memory Address 0xDE800000-0xDF0FFFFF
I/O Port 0x000003B0-0x000003DF
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\BASICDISPLAY.INF_AMD64_5103AC179273BE89\BASICDISPLAY.SYS (10.0.17763.1, 66.50 KB (68,096 bytes), 9/15/2018 12:11 AM)


We rarely have a monitor plugged into it, most of the time we just use remote desktop to log in.

And as previously stated, the nvidia cards are almost never used because they dont provide much help.

If you think that the nvidia cards have anything to do with the crashing we can remove them (or replace them with a better GPU) but i dont think thats the case because no re-encoding is ever done, every stream goes straight to disk.


If theres any other info yo think might help please let me know. Blue iris is great value for the money when it works. Id hate to have to switch to other software. Id even rather upgrade the hardware if its a hardware spec issue rather than switching software, just because of how well it has worked for us up until the point of it starting to crash due to whaever these issues are.

again, thank you for any help
 
What was the decision to cascade? You may be trying to write too many cameras to one drive.

Best practice is to spread the cameras across the drives. With 8 drives, spreading 5 to 8 per drive would keep camera count down and not have you lose all video if a drive crashes.
 
  • Like
Reactions: Flintstone61
wittaj: It didn't occur to me that you could do that, but that makes sense, but wouldn't the clips still cascade don the drives anyways? for example lets say that:

cameras A, B and C write to Drive 1
cameras D, E and F write to drive 2
and no cameras are set to write to drive 3..

dont the recordings that were on drive 1 get pushed to drive 2, and eventually all the recordings will get pushed to drive 3 ?

maybe im not understanding how the cascading of blue iris works..
 
You shouldn't cascade with BI.

All you are doing is wearing out the drives and using excess CPU moving video files from one drive to the next.

Leave everything in the respective "New" folder on each HDD and do not move it to a "Stored" folder on that HDD or another in the box.

And then have it delete video based on storage limits of each drive.
 
  • Like
Reactions: kklee
My old Standard allocation post.

1) Do not use time (limit clip age)to determine when BI video files are moved or deleted, only use space. Using time wastes disk space.
2) If New and stored are on the same disk drive do not used stored, set the stored size to zero, set the new folder to delete, not move. All it does is waste CPU time and increase the number of disk writes. You can leave the stored folder on the drive just do not use it.
3) Never allocate over 90% of the total disk drive to BI.
4) if using continuous recording on the BI camera settings, record tab, set the combine and cut video to 1 hour or 3 GB. Really big files are difficult to transfer.
5) it is recommend to NOT store video on an SSD (the C: drive).
6) Do not run the disk defragmenter on the video storage disk drives.
7) Do not run virus scanners on BI folders
8) an alternate way to allocate space on multiple drives is to assign different cameras to different drives, so there is no file movement between new and stored.
9) Never use an External USB drive for the NEW folder. Never use a network drive for the NEW folder.
10) for performance do not put more than about 10,000 files in a folder, the search and adding files will eat CPU and disk performance. Look at using a sub folder per camera (see &CAM in bi help)


Advanced storage:
If you are using a complete disk for large video file storage (BVR) continuous recording, I recommend formatting the disk, with a windows cluster size of 1024K (1 Megabyte). This is a increase from the 4K default. This will reduce the physical number of disk write, decrease the disk fragmentation, speed up access.
Hint:
On the Blue iris status (lighting bolt graph) clip storage tab, if there is any red on the bars you have a allocation problem. If there is no Green, you have no free space, this is bad.
======================================
 
  • Like
Reactions: Cooltiger
I typically write to 2 8TB WD purples, splitting the "work" across two drives.
on the storage tab in settings it has all these Aux 1,2,3,4 folder names in it.
you can create new folders with the same name in a second drive, and then close that
and open the recording tab on each camera you want to move there.
then change it to The new folder(s) on the second drive.
also try increasing the size of the Alerts folder so that isnt an issue.
1737396693918.png1737396728461.png1737396855943.png
 
Hey Everyone,

thank you for the insight on this subject.

After reading the BI manual I was under the assumption that all clips get cascaded no matter what cameras are recording t what drive. My thinking was that if you have drive D, E and F with cameras 1 2 and 3 respectively, clips from camera 1 would go to drive D, clips from camera 2 would go to camera E and clips from camera 3 would go to drive F...

.. and when the D drive gets full, they get pushed to the E drive, and the clips from the E drive get pushed to the F drive, and then deleted (as long as the F drive is the final drive in the chain).

So if I do have camera 1 set to record to drive D.. what happens when D gets full? If I set it to delete the clips, will it just delete the oldest clips from the D drive from cam 1 and each other drive is independent of eachother?
 
  • Like
Reactions: Flintstone61
If you have camera 1 set to drive D and keep it all in the respective "New" Folder and don't move it to a respective "Stored" folder and you set it up to delete based on available storage, then when it is full, it will delete the oldest. Do not set up by number of days.
 
I will try this!

BTW did you know this forum doesn't have the best reputation, but everyone here has given me valid and advice that sounds like it will work!

Im glad i asked about my issue, because everyone here has been very helpful with advice that makes sense and I bet will fix my issue! Thank you everyone! I will report back with results.
 
Not sure I fully grasped #10. Do you have some screenshot demonstrating how you have subfolders set up for each cam? BI settings screenshots and may screenshot of the folders?

1738423974084.png
 
  • Like
Reactions: AlwaysSomething