- Sep 25, 2016
- Reaction score
- Evansville, In. USA
If it's not broke, don't fix it. Most likely, you would be better off removing the Nvidia completely.I'm having somewhat similar issues with my Blue Iris 5.x install (18.104.22.168 to be exact). It runs as a service but I do sometimes connect via RDP and run the app as well to monitor the feeds. I don't normally use the web interface.
From time to time, maybe after 24-30 hours of uptime, about half of the cameras go into "no signal" and the only solution is to close the console and stop the service, then start the service back up. About half the time the service can't be stopped at all and I have to reboot the machine.
My cameras are a hodge podge of Amcrest, Dahua and Reolink (I read through this thread and was surprised to hear of issues with Reolink "tearing" since I've never experienced it, but maybe my settings are different, unless I don't understand what that means? I think they're using RTSP but I don't remember). The cameras that show "no signal" vary, not any specific make or model.
This had all been working great up until recently, and the recent change I made was that the Intel Driver & Support Assistant I have installed on there prompted to update the Intel HD 630 drivers. I'm now running version 22.214.171.12400.
When that happened I thought maybe it was a good time to also update the drivers for the Quadro P2000 in there, which is doing a lot of the HWDEC work. So I updated it as well to Nvidia's version 126.96.36.19970
My guess is that one or the other of those drivers may be the problem so I'll probably roll both of them back and see if a) the problem goes away and b) introduce one back at a time and see which one causes it. Because I'm curious to know.
It does sound like some Intel video driver versions have problems, so I'm headed to the wiki now to see if that version I have is mentioned as good/bad. If that is the problem, then the lesson I learned is, don't update just because, or let someone else do it first and report back.