My computer that runs my camera restarts itself every 4 to 8 days. I figured it was Windows automatically updating and restarting. Turns out that is not the case as I completely disabled Windows update.
Well it did it again and I can’t figure out why. Is there some way that if the computer restarts it will automatically open BlueIris for me?
At the moment I have a password to start home screen so it gets stuck there. Don’t really need the password home screen.
But it is quite a pain because I don’t know when the computer restarts or it may be hours before I can get home to open the program rendering my cameras useless.

See if you can run Blue Iris as a service.

It should be in the configuration of the application.

In Blue Iris, under settings, on the startup tab, click run as a Windows service.

As for the reason for the restarts you need to start looking at your event viewer.

2 problems:
1. Yes, run Blue Iris as a service and it will start automatically.

2. Several things can cause a restart, but I'd start with blowing out the computer with compressed air to reduce heat.

I'd clean it out really well, as someone mentioned heat will cause random reboots when the CPU tries to save itself. Take it outside with a couple cans of compressed air, open it up and blast away, including up inside the power supply.

Check that all RAM and cards are seated too.

A bad power supply could also be the culprit.

quote:

Originally posted by PASig:
as someone mentioned heat will cause random reboots when the CPU tries to save itself.

Download the software called "Core Temp" to know for sure.

+1 on checking the event viewer log. gotta know for sure what's going on.

As everyone suggested above - set Blue Iris to run as a service and ensure your system is not overheating

Then run msconfig - go to the Startup tab under System Configuration then uncheck all boxes or select Disable All.

Select Apply > OK

then reboot the system - ensure your Blue Iris is running - I am not familiar with Blue Iris so do not know if there are any supporting startups even if it runs as service so you many need to check this is running after you disable all startups and blue iris set as a service

Now give it some soak time and let it run with all user startup items not running - and see if it reboots - if it does not then it narrows it down to a user startup item then from there start rolling through the startup list and enable the basics first - for example using one of my systems I would enable the Realtek audio manager first - or enable a like group together like all audio together - or all video so it it at least is not one at a time and waiting a day or days between each to see what could be rebooting

speaking of video, a few years ago some of the office systems I swapped out with nvidia cards and they caused system crashes sporadically - had to update drivers so also check on updates for hardware and any running software - especially if you installed any updated or new hardware - most especially video and memory

//ETA - in the case of the issue when I installed the video cards - I had installed the newest driver for the video at install - it was only after I updated drivers of the rest of the hardware that the sporadic issues stopped with the systems - honestly don't know which it could have been audio, controllers etc but did a bios update as well and I *think* it was that - I didn't do one at a time but all of them to resolve it quickly if all possible

Looked at the Windows Event log that is all Greek to me so I don’t have a clue what I am looking at or for in particular.

Setup BlueIris as a service reset the machine and had access on the smartphone app without logging in. So that looks to be working right and should keep me going in the event of future rests.

I downloaded CoreTemp.
I presume it sets the min/max based upon the processor.
Everything seems to be falling in line as it should while I was watching it.

You computer might has Ebola.

Do you see data running out of its orifices?

power supply is the first suspect with random reboots, but could be a number of things.

Why is VID so low? I thought on the 2nd gen processors it was to be higher than that, but I've not looked at 2nd gen for at least 6 years. Maybe that's correct given your clock speed. Dunno.

Temps are fine and shouldn't be a problem as long as the readings you posted were taken under normal conditions and after the computer had been on a while.

quote:

Looked at the Windows Event log that is all Greek to me so I don’t have a clue what I am looking at or for in particular.

You should look for critical. warning or error events (filter the logs) in the application and system event logs.
First look for any unexpected shutdown events and then look for any immediate preceding events that might indicate what was happening prior.
It may or may not easily indicate what actually happened but is a good place to start.
You may see a driver call that was not there or a power event or perhaps something else.
I have had clients with some certain series Intel SSD drives that would have shutdown events that was caused by firmware.
It was not easily recognized in the event viewer except for the unexpected shutdown event.
It was fixable as there was some drive sleeping firmware that had to be disabled (recognized Intel issue- fixable).
BIOS and device firmware should be researched to see if applicable.
Good Luck.

quote:

Originally posted by radioman:
Why is VID so low? I thought on the 2nd gen processors it was to be higher than that, but I've not looked at 2nd gen for at least 6 years. Maybe that's correct given your clock speed. Dunno.

Temps are fine and shouldn't be a problem as long as the readings you posted were taken under normal conditions and after the computer had been on a while.

What is VID?

quote:

Originally posted by smschulz:

quote:

Looked at the Windows Event log that is all Greek to me so I don’t have a clue what I am looking at or for in particular.

You should look for critical. warning or error events (filter the logs) in the application and system event logs.
First look for any unexpected shutdown events and then look for any immediate preceding events that might indicate what was happening prior.
It may or may not easily indicate what actually happened but is a good place to start.
You may see a driver call that was not there or a power event or perhaps something else.
I have had clients with some certain series Intel SSD drives that would have shutdown events that was caused by firmware.
It was not easily recognized in the event viewer except for the unexpected shutdown event.
It was fixable as there was some drive sleeping firmware that had to be disabled (recognized Intel issue- fixable).
BIOS and device firmware should be researched to see if applicable.
Good Luck.

I’ll take another look.
No Solid State drive just a WD Purple.

quote:

What is VID?

It's the core voltage for the CPU. For your CPU, it's low. Should be 1.2V. The problem is the reading may not be correct, but you can normally go into your BIOS settings to monitor / change it.

But messing with core voltage is not without risk, and honestly shouldn't be done unless you are comfortable with such things. If it were me, I'd boost it, but I cannot recommend this to someone else on the internet.

I also wonder why you are running at 1605 MHz. Your processor should run at 3400 MHz (plus overclock speeds).

To quote one of the news channels, "Sum Ting Wong"

Your processor is about 8 years old, are you sure you don't just want to get something new and improved. FWIW, newer chips will take less power when you run blue iris 24/7. you are likely burning about $12 a month just to run BI 24/7 with your system. You could cut this at least somewhat, although not enough to pay for a new system.

Problem is I don’t have a clue as to anything you are talking about as I am far from a computer guy.

The motherboard, RAM, and processor were a gracious karma from a member here and I supplied a new power supply, hard drive, and case.
I stuck it all together myself which could be why those things are off as I have no clue.