Hello again, I am having an issue with BI and remote desktop. When running BI I get disconnected when I try and connect to the cam PC remotely. This is not an issue when BI is not running on the cam PC. This is a fresh win11 install and only BI installed and running. BI seems to be running fine and now with help from this forum BI runs with little CPU and other RSS issues. If I check the PC locally all is fine, but when I remote into it I logs in and opens the PC usually with some type of display issue (small text and or pics, offset toolbar etc) and then I get disconnected. Retry and get back in can move mouse around a little then disconnected again. Anyone else seeing this issue. If I can get task manager to run after a few tries, it shows no issues.
Blue Iris and Remote Desktop crashing
- Thread starter wlf311
- Start date
Unfortunately this sounds like probably a hardware or driver issue and it may be hell to solve.
But it looks like your Event Viewer may hold some clues. Although most events are incredibly vague, sometimes they do contain useful information. You should go through that summary page and look at any events that happened recently (especially those in the Critical section or Error section. When you double click one of those lines in Event Viewer it will bring you to a filtered view showing the type of event you double-clicked. When you're done reviewing those events, you can use the back button in the upper left to go back to the summary view.
Kernel-Power events (which you had twice in the last week) occur when Windows boots up after an unclean shutdown (which could be intentional done by you, or the result of a power outage, or hardware/driver-caused crash).
The DriverFrameworks-UserMode events are something I haven't seen before, and with any luck they correspond to your Remote Desktop failures. Hopefully in the event data there will be some indication of which driver is having a problem and what the problem is, as this could indicate you have some failing hardware causing issues. Could be anything from some onboard component to a USB-connected device and it certainly could be involved in causing the problem you are having.
The nvlddmkm error is associated with your nvidia GPU so it would not be a bad idea to get the latest nvidia graphics driver. However with only one occurrence in the previous week I doubt it is the cause of your remote desktop issue.
Also check out the Application Hang line in event viewer and see if you can tell what that is about.
Also, if your system happens to be maxed out on CPU or RAM usage while you are trying to connnect with remote desktop, that could aggrevate the issue. High enough memory usage may even cause apps like remote desktop to fail to load correctly and crash. You should be able to monitor this remotely via Blue Iris's web interface (UI3) or mobile apps, and if memory usage is very high (like above 90%) then it could be a possible problem for you.
But it looks like your Event Viewer may hold some clues. Although most events are incredibly vague, sometimes they do contain useful information. You should go through that summary page and look at any events that happened recently (especially those in the Critical section or Error section. When you double click one of those lines in Event Viewer it will bring you to a filtered view showing the type of event you double-clicked. When you're done reviewing those events, you can use the back button in the upper left to go back to the summary view.
Kernel-Power events (which you had twice in the last week) occur when Windows boots up after an unclean shutdown (which could be intentional done by you, or the result of a power outage, or hardware/driver-caused crash).
The DriverFrameworks-UserMode events are something I haven't seen before, and with any luck they correspond to your Remote Desktop failures. Hopefully in the event data there will be some indication of which driver is having a problem and what the problem is, as this could indicate you have some failing hardware causing issues. Could be anything from some onboard component to a USB-connected device and it certainly could be involved in causing the problem you are having.
The nvlddmkm error is associated with your nvidia GPU so it would not be a bad idea to get the latest nvidia graphics driver. However with only one occurrence in the previous week I doubt it is the cause of your remote desktop issue.
Also check out the Application Hang line in event viewer and see if you can tell what that is about.
Also, if your system happens to be maxed out on CPU or RAM usage while you are trying to connnect with remote desktop, that could aggrevate the issue. High enough memory usage may even cause apps like remote desktop to fail to load correctly and crash. You should be able to monitor this remotely via Blue Iris's web interface (UI3) or mobile apps, and if memory usage is very high (like above 90%) then it could be a possible problem for you.
Thank you for the tips. I will have to research some of these things. I never had had these issues when running BI on this machine a couple years ago. I just recently got more cameras and figured I needed a new version of BI. I did a fresh Win11 install, nothing else is running on this PC and no other hardware other than a 10Gb ethernet adapter and the NVIDIA card. The help I received here has gotten my cpu down to about 6%, gpu at about 6%, and I just put 32G of ram in and not much of that is being used, 2 M.2 drives, 500M for C and BI main, 1TB for BI storage. I have not set it up yet but every 30 minutes the D drive is moved to NAS and cleared.
After some research the errors had to do with a driver issue of some sort. Unfortunately I ran a recommended "verifier" program from Microsoft which essentially prevented my PC from being able to restart. So after multiple tries I had to do a windows restore and I did the remove programs option. Since that I reinstalled BI and set all my cams up in the most basic way to see what happens. So far so good, I was able to remote into the PC and install backup software and other utility style programs and run a full image backup, copy images off to the NAS etc. without any remote desktop crashes. Thank you again for the help.
Well next is figuring out the new Empiretech LPR camera and how that setup and software works to add that into BI.
Then looking into how this AI gets installed and set up.
Then looking into how this AI gets installed and set up.
You would need a Dahua OEM NVR or use the Dahua PC-NVR software to use SmartPSS software. It will not work with BI.
And the Dahua PC-NVR software is horrible. It is a resource hog.
SmartPSS is limited to 256 cameras.
Just curious about it as I am learning about this new camera. I can't get it to recognize all my cameras at once. It stops at 10 and if I manually add more they show as offline. The smartPPS lite does the same thing. Not a big deal just curious as what I saw online said 256 as well. Not going to lose sleep over it as I plan to use BI, especially now that it works so well and uses little rss. I can even go back to an old spinning drive again as I am just wearing out my M.2 drive for no good reason. Thank you again.