Are we allowed to discuss computer troubleshooting issues in this section? This is for a camera server, but I don't believe the issue is related to the camera server software running on this computer, however, I feel like the people who browse this section may be able to help.
If I get the ok to discuss, I will post the issue, if this is the wrong place, I will delete the thread.
Thanks.
EDIT
Here is my issue
I have an NVR that is running Avigilon. A few weeks ago, the system blue/screened/rebooted/locked up, it was in the middle of the afternoon, I was not on site, I didn't find out until the next morning when I was on site, I saw that the system was in the blue screen stating that it didn't boot up properly.
At that point, I rebooted, windows loaded w/o issues. I launched Avigilon and everything was fine....or so I thought. Live view worked great, but it wasn't until I saw that nothing was being recorded. I opened a ticket with Avigilon and they figured out that the Avigilon software was confused, momentairly, and saw the system/date change to a date/month in the year 2030 and to avoid recording over existing footage (at this point the computer was automatically switched back to the present, correct, date/time) it wasn't going to record anything until it saw the date 2018 change to 2030. The tech cleared up all the db to get rid of all the 2030 recordings, restarted the NVR service, and things were back to normal......for about a week. Then the same exact thing happened, the computer improperly reboots/blue screens/etc, again, I am not there and I find myself in the same scenario.
Now that we know why Avigilon recording fails, the tech states that it is not an Avigilon problem and I agree with him.
I checked Event Viewer when the system failed, but nothing stands out, to me. This problem occurred yesterday and this time I exported the EV.
System Log
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-Boot 20 -31 The last shutdown's success status was false. The last boot's success status was true.
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-Boot 153 -62 Virtualization-based security (policies: 0) is disabled.
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-General 12 -1 The operating system started at system time 2018-03-22T21:15:41.499211900Z.
Information 3/22/2018 12:00 EventLog 6013 None The system uptime is 628368 seconds.
The server crashed/rebooted at 3-22-18 at 4:15pm and nothing stating that shows up between 12:00 and 16:15
Application Log
Error 3/22/2018 16:16 Avigilon Control Center 0 None Recording interrupted on camera '14' because the system time has been changed backwards. Recording will resume at 2030-Feb-27 05:35:14.464 PM.
When the system crashes, the time temporarily switches to sometime in 2030. Windows is set to obtain time automatically and the time is always correct when I look at it. I've only seen the 2030 date/time in logs, never in the OS or camera program.
The system is custom built, I can provide parts list if needed. It is also connected to a UPS w/o the UPS software/cable controlling shutdown (that can be ruled out).
I tried setting the windows time option to manual to see if something with the time was causing the computer to act up, but the issue occurred with the time being set to manual (that can be ruled out).
Active hours on the windows computer are 8am to 8pm, it has always rebooted, improperly, sometime between 4:30pm and 6:30pm (rebooting due to windows updates can be ruled out).
I'd like to test memory and possibly the power supply, next. I'd like some input from others who are more experienced in PC troubleshooting.
Thanks.
--------------------------------
--------------------------------
--------------------------------
UPDATE 5-24-18
--------------------------------
--------------------------------
--------------------------------
UPDATE, I replaced the power supply, about 25 days ago, and the computer has been up and running ever since. I received a notification for windows updates which I set to remind me later/postpone/whatever the option to do it later was. This is w10, but you still get 1 or 2 changes to push updates to a later time.
Anyway, I wanted to make sure it went more than two weeks w/o a reboot before I posted the resolution.
If I get the ok to discuss, I will post the issue, if this is the wrong place, I will delete the thread.
Thanks.
EDIT
Here is my issue
I have an NVR that is running Avigilon. A few weeks ago, the system blue/screened/rebooted/locked up, it was in the middle of the afternoon, I was not on site, I didn't find out until the next morning when I was on site, I saw that the system was in the blue screen stating that it didn't boot up properly.
At that point, I rebooted, windows loaded w/o issues. I launched Avigilon and everything was fine....or so I thought. Live view worked great, but it wasn't until I saw that nothing was being recorded. I opened a ticket with Avigilon and they figured out that the Avigilon software was confused, momentairly, and saw the system/date change to a date/month in the year 2030 and to avoid recording over existing footage (at this point the computer was automatically switched back to the present, correct, date/time) it wasn't going to record anything until it saw the date 2018 change to 2030. The tech cleared up all the db to get rid of all the 2030 recordings, restarted the NVR service, and things were back to normal......for about a week. Then the same exact thing happened, the computer improperly reboots/blue screens/etc, again, I am not there and I find myself in the same scenario.
Now that we know why Avigilon recording fails, the tech states that it is not an Avigilon problem and I agree with him.
I checked Event Viewer when the system failed, but nothing stands out, to me. This problem occurred yesterday and this time I exported the EV.
System Log
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-Boot 20 -31 The last shutdown's success status was false. The last boot's success status was true.
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-Boot 153 -62 Virtualization-based security (policies: 0) is disabled.
Information 3/22/2018 16:15 Microsoft-Windows-Kernel-General 12 -1 The operating system started at system time 2018-03-22T21:15:41.499211900Z.
Information 3/22/2018 12:00 EventLog 6013 None The system uptime is 628368 seconds.
The server crashed/rebooted at 3-22-18 at 4:15pm and nothing stating that shows up between 12:00 and 16:15
Application Log
Error 3/22/2018 16:16 Avigilon Control Center 0 None Recording interrupted on camera '14' because the system time has been changed backwards. Recording will resume at 2030-Feb-27 05:35:14.464 PM.
When the system crashes, the time temporarily switches to sometime in 2030. Windows is set to obtain time automatically and the time is always correct when I look at it. I've only seen the 2030 date/time in logs, never in the OS or camera program.
The system is custom built, I can provide parts list if needed. It is also connected to a UPS w/o the UPS software/cable controlling shutdown (that can be ruled out).
I tried setting the windows time option to manual to see if something with the time was causing the computer to act up, but the issue occurred with the time being set to manual (that can be ruled out).
Active hours on the windows computer are 8am to 8pm, it has always rebooted, improperly, sometime between 4:30pm and 6:30pm (rebooting due to windows updates can be ruled out).
I'd like to test memory and possibly the power supply, next. I'd like some input from others who are more experienced in PC troubleshooting.
Thanks.
--------------------------------
--------------------------------
--------------------------------
UPDATE 5-24-18
--------------------------------
--------------------------------
--------------------------------
UPDATE, I replaced the power supply, about 25 days ago, and the computer has been up and running ever since. I received a notification for windows updates which I set to remind me later/postpone/whatever the option to do it later was. This is w10, but you still get 1 or 2 changes to push updates to a later time.
Anyway, I wanted to make sure it went more than two weeks w/o a reboot before I posted the resolution.
Last edited: