Woke up this morning, Blue Iris machine totally unresponsive, monitor powered off, had to do a forced reboot, can't figure out what happened.
All my footage just ceased to record at 12:18am last night. Nothing in the Blue Iris log tab about it, in fact, it seemed to have cleared itself when I loaded up Blue Iris (I wish Blue Iris would preserve old log files by default, I did not have "Save to file" checked in the BI log tab!).
I checked out the Windows Event Viewer, and it looks like at 12:19am Windows reported a LiveKernelEvent, but the attached event files don't exist. Obviously something happened...
Also, looking through the Event Viewer, it looks like the computer kept on working all night though on other tasks, at least partially, but like I mentioned, it was unresponsive this morning, and then I did the forced reboot.
Any ideas? Everything is running fine right now.
I wonder if it's a hard drive issue? The drive that was being written to is very old, and I've been meaning swap it out. Maybe the drive did something crazy which caused this odd behavior? I will check that later today.
Also, I've now enabled "Save to file" in the log tab, so if it happens again, maybe BI will give me a clue...
Any thoughts appreciated.
All my footage just ceased to record at 12:18am last night. Nothing in the Blue Iris log tab about it, in fact, it seemed to have cleared itself when I loaded up Blue Iris (I wish Blue Iris would preserve old log files by default, I did not have "Save to file" checked in the BI log tab!).
I checked out the Windows Event Viewer, and it looks like at 12:19am Windows reported a LiveKernelEvent, but the attached event files don't exist. Obviously something happened...
Also, looking through the Event Viewer, it looks like the computer kept on working all night though on other tasks, at least partially, but like I mentioned, it was unresponsive this morning, and then I did the forced reboot.
Any ideas? Everything is running fine right now.
I wonder if it's a hard drive issue? The drive that was being written to is very old, and I've been meaning swap it out. Maybe the drive did something crazy which caused this odd behavior? I will check that later today.
Also, I've now enabled "Save to file" in the log tab, so if it happens again, maybe BI will give me a clue...
Any thoughts appreciated.