Windows 10 runs out of RAM

fenderman said:
Your issue is likely not related to the driver particularly if you tried the known good drivers listed in the wiki. I personally have never seen a 4th gen haswell suffer from a memory leak.
Your issue is also not with blue iris. Blue iris itself does not suffer from a memory leak. Perhaps you are better off with the dahua NVR.
Click to expand...

Its definitely not Blue Iris; performance monitor shows it consistently using ~3.7GB of ram.

I'm starting to suspect its not the video drivers and its some other driver or Windows issue. This machine ran Blue Iris for almost a year without a reboot up until recently.
 
Its probably time to toss this PC in the trash. Time to re-purpose my Intel i7 desktop for Blue Iris so I have a good excuse to build a new desktop for daily use.
 
fenderman said:
Just clean install Windows takes 10 minutes
Click to expand...

Suppose its worth a shot as an intermediate step. Hah, if it wasn't for Blue Iris I would not be using Windows at all any more. I absolutely DESPISE how a fresh OS install always fixes things like this.

I'm still thinking I'd like a new PC for BI since I do want to get a Tensorflow model trained to add some more intelligence to my camera motion detection though.
 
Tygunn said:
Suppose its worth a shot as an intermediate step. Hah, if it wasn't for Blue Iris I would not be using Windows at all any more. I absolutely DESPISE how a fresh OS install always fixes things like this.

I'm still thinking I'd like a new PC for BI since I do want to get a Tensorflow model trained to add some more intelligence to my camera motion detection though.
Click to expand...
There's no problem with Windows... There's a high probability that you didn't do a clean install initially using the Microsoft media creation tool.. I run over 20 blue Iris machines and many many more personal desktops and Windows 10 runs flawlessly. The key is a clean install of Windows initially and no crap.
 
Tygunn said:
Its probably time to toss this PC in the trash. Time to re-purpose my Intel i7 desktop for Blue Iris so I have a good excuse to build a new desktop for daily use.
Click to expand...
one question, did you activate Intel QSync acceleration in BI ? if yes may be you could deactivate it and see if it help, may be Intel's drivers that provide QSync have memleak ?
 
fenderman said:
There's no problem with Windows... There's a high probability that you didn't do a clean install initially using the Microsoft media creation tool.. I run over 20 blue Iris machines and many many more personal desktops and Windows 10 runs flawlessly. The key is a clean install of Windows initially and no crap.
Click to expand...

This was a clean install of Windows 10 back when I first set this machine up a couple years back; I wiped the machine completely and started fresh when I re-purposed for Blue Iris.
However, its worth a shot.
 
Tygunn said:
This was a clean install of Windows 10 back when I first set this machine up a couple years back; I wiped the machine completely and started fresh when I re-purposed for Blue Iris.
However, its worth a shot.
Click to expand...
A leak cannot simply develop on its own. Something had to have changed.
Did you perform a clean install using the media creation tool or the OEM media?
 
Dodutils said:
one question, did you activate Intel QSync acceleration in BI ? if yes may be you could deactivate it and see if it help, may be Intel's drivers that provide QSync have memleak ?
Click to expand...

Yes, I did activate all the hardware acceleration I could. I will give that a shot as well. It would be nice to be able to root cause the problem so I know what caused it, other than the usual, "Windows bloated itself up with crap and slowed down.". :)
 
fenderman said:
A leak cannot simply develop on its own. Something had to have changed.
Did you perform a clean install using the media creation tool or the OEM media?
Click to expand...

I used the media creation tool since the PC has no CD/DVD drive in it.

I agree something had to have changed to cause the problem. :) I only wish I knew what that was so I could avoid the issue in the future.
 
I finally got around to using the media creation tool to wipe the machine I'm using and re-install BlueIris.

Kudos to BlueIris for the awesome export/import. It was easy to get things back up and running on the newly wiped computer. I only have to reconfigure the volumes because Windows changed my drive labels.

Fingers are crossed that this solves the memory leak.
 
Dodutils said:
Hope it will be ok after installation of all Windows and drivers updates ;-)
Click to expand...

Sadly everything on the PC seems faster now that I've wiped it and started fresh. Of course for windows I guess this is just par for the course.

I use linux at work day in and out and haven't restarted my machine in ages; haven't re-installed the OS since I got the PC a few years ago.
 
Tygunn said:
Sadly everything on the PC seems faster now that I've wiped it and started fresh. Of course for windows I guess this is just par for the course.

I use linux at work day in and out and haven't restarted my machine in ages; haven't re-installed the OS since I got the PC a few years ago.
Click to expand...
Having to reinstall Windows is unusual...I can't remember the last time I needed to do this...And there are occasions where Linux has to be reinstalled as well.
I had an instance of blue Iris for running for over a year with updates disabled on Windows.
You should be running Windows and blueiris on an SSD....
There's nothing wrong with Windows it's usually the end-user that causes problems.
 
fenderman said:
Having to reinstall Windows is unusual...I can't remember the last time I needed to do this...And there are occasions where Linux has to be reinstalled as well.
I had an instance of blue Iris for running for over a year with updates disabled on Windows.
You should be running Windows and blueiris on an SSD....
There's nothing wrong with Windows it's usually the end-user that causes problems.
Click to expand...

Yet when things go wrong with Windows the solution is always, "reinstall a fresh copy". Try as I might there was no good way to diagnose the source of the leak despite hours spend researching and many tools.
Windows and BI are both running on an SSD; recordings go to a WD Purple drive.
I think you can be more accurate, "There's nothing wrong with Windows; it's USING it that causes problems.". Ha ha ha.
But in all seriousness the computer I run BI is not used for anything else. It literally sits on its own network segment, in a corner, on its own, doing its thing.

Oh well, whatever we'll see if the problem clears up.
 
Tygunn said:
Yet when things go wrong with Windows the solution is always, "reinstall a fresh copy". Try as I might there was no good way to diagnose the source of the leak despite hours spend researching and many tools.
Windows and BI are both running on an SSD; recordings go to a WD Purple drive.
I think you can be more accurate, "There's nothing wrong with Windows; it's USING it that causes problems.". Ha ha ha.
But in all seriousness the computer I run BI is not used for anything else. It literally sits on its own network segment, in a corner, on its own, doing its thing.

Oh well, whatever we'll see if the problem clears up.
Click to expand...
Yes because its generally the user who screwed things up beyond repair. With linux, the average users does not have the know how to install anything .
Like I said, I have over 20 BI machines, and many many more office machines running windows. None of these "issues".
 
fenderman said:
Yes because its generally the user who screwed things up beyond repair. With linux, the average users does not have the know how to install anything .
Like I said, I have over 20 BI machines, and many many more office machines running windows. None of these "issues".
Click to expand...

Sure, its certainly _something_ I did on the machine that got it into that state. However, despite 20 years of software development experience I was unable to diagnose the cause of the memory leak other than "there's memory leaking". I probably could have figured it out if I had persisted, but I didn't feel like digging into kernel debugging tools, etc.
 
You must log in or register to reply here.
Top Bottom