Windows 10: Update 2004 Memory Leak

So I just got the Windows 10 ver. 2004 update, and now my memory's leaking all over the place. My computer is currently using 50% of its overall memory and I can't seem to figure out what's causing it to leak as much as it is.


Is anyone else having this issue? Or is there any way to fix it?

:)

 

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.

 

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.

 

Windows 10 memory leak after update [Wfpn / ntoskrnl.exe]

Notice: I have already read this answer and followed the steps in it, but I can't figure out what is causing the leak. What I'm looking for here is help in singling out the problem.

As you can see from the title of the question I've encountered a memory leak in Windows 10 after the latest update (Creator's Update I believe). The first thing I did was open the task manager, where I've noticed unpaged memory taking up about 13GB of RAM.

I went through the Poolmon/Pooltag/findstr process only to get garbage on the cmd




I then tried to use Xperf to find out what was happening, but I'm still unsure as to what I'm looking at. The root cause seems to be the kernel image, and I find that hard to believe. Here's the output of Xperf as seen in WPA:




I've had a similar problem in the past on Windows 10 that was caused by Killer Networking drivers, but this time around that doesn't seem to be the culpript.

If anyone is able to help me out it would be greatly appreciated!

EDIT: I state in the first paragraph that this question is different from the one being suggested by the mod (I even link that very question). I had already taken all the steps in the answer to that question and still couldn't track down which driver was causing the issue, hence I was asking for users to help me find which one was the problematic one.