Windows 10: DWM memory leak problems

Like many people, I've suddenly started having memory leak problems with Desktop Window Manager, getting as high as 4.4GB which isnt good for my little 16GB laptop. It seems universally accepted that it's caused by a faulty Intel river for the Intel HD 630 and I've seen a solution posted that could work, but it involves downloading some third party software and messing with the drivers in safe mode. Rather than resort to this just yet, I'm wondering if I could just disable the Intel display adaptor in device manager and have everything run off of my Nvidia GTX 1050 Ti. Most every process is set to run off the high end nvidia processor in the Nvidia control panel, so right now I'm not sure what the intel processor is being used for at all, besides messing with DWM

submitted by /u/SleepyWuff
[link] [comments]

:)

 

Desktop Window Manager Memory Leak

These applications not are compute-intensive, compared to
CPU speed. "The problem" is the memory leak of DWM.

As soon as I could observe a high memory consumption by DWM, I started windows performance tool kit and run the diagnose. Then I switch to the game and
continued playing for a few seconds
until stop the diagnosis.

 

Possible Memory Leaks in Windows 10

A memory leak occurs when an application closes and fails to release all its RAM back to the operating system.

The first step in dealing with a memory leak is to determine which application is leaking memory.

The next step is to contact that application's technical support with complete details of the memory leak, since the developers will want to fix the problem ASAP.

 

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.