Windows 10: Huge memory leak keeps crashing the system

Hi,

I'm running the latest April update 1803 on my Acer nitro vn-791g. My problem is that my committed memory and paged pool climb up after 2-3 days of my laptop being turned on (with sleep mode at night). This reaches a point where the system hangs, browsing tabs crash repetitively and then it BSODs or force restarts.

I have only noticed the problem recently but for some reason I've always had relatively high ram usage (50%) even when there are no open programs. However, this is only apparent when the system has being left on for some time. Cold reboots yield 35-40% RAM usage initially. Recently as mentioned, it became so severe that I cannot keep my system turned on for more than 3 days at best, before it crashes or I restart it.

It's becoming super frustrating and I can't figure out what could be causing the huge memory. My network card is a qualcomm QCa61x4 since I heard network drivers might be a problem but I switched across drivers and that made no difference.

I'm attaching taskmanager screenshots in a zip file of the problem and a cold reboot right after to see the difference.

Thank you.

:)

 

Windows 10 System Memory leak

I discovered that Skype was the main cause in my case. I don't have to autostart, but I wanted to be able to start it manually. Last time I was paying attention, no memory leaks occurred, but as soon as Skype started I noticed it started to drain my hard
drive, and the huge system memory appeared again. I uninstalled skype to see if it reappears, but I am very much positive that skype caused this anomaly.

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.