Windows 10: Windows 10 Memory Leak. Trying to track down cause using Poolmon.

Hi, I have a real heavy Paged memory leak that just steals memory to the point where I end up getting a low memory warning in Windows 10 and I need to reboot. I've installed Poolmon and to be honest, deciphering what's causing it is above my pay grade. I'm working with 16GB's of total memory. 70% of it has now been used and there's no way I'm using anything even remotely close to that with the windows 10 basic things I've been doing. Poolmon is pointing to the paged tag - None which according to the windows memory tag pool master list states that None refers to "call to exallocate pool' and after a google search when referring to this, all I'm finding is this website

https://docs.microsoft.com/en-us/win...atepoolwithtag![54915-pool-paged-memory-leak.jpg][1

....which frankly isn't really helping me as I'm trying to track down the driver responsible for this memory leak. Originally thought it might be pertaining to macrium reflect as a hunch, but I'll need to uninstall that and wait to see if that's the case. Can anyone guide me in a direction that could explain what 'call to exallocate pool' actually is and what would be causing it to swallow up so much page memory requiring a reboot once it fills completely up. Frankly, I'm head scratching on what to do in order to fix this issue. Thanks for any help. [1]: /answers/storage/attachments/54915-pool-paged-memory-leak.jpg

Windows 10.0.19042 Build 19042




:)

 

HidBthLE.dll - memory leak

Any movement on this? I started getting huge memory leak problems, I think right after the big windows 10 update. The first one I tracked down was my network interface driver. An uninstall and reinstall seems to have fixed that. But theres still a smaller
leak happening. Running poolmon shows this bluetooth driver is growing and growing in size using up all of my memory in a few days.

I use a bluetooth mouse, and as you watch poolmon the size of the memory stays the same if I dont move the mouse, and as I start moving it slowly, the memory used grows slowly, and as I move the mouse faster it grows quicker!

I uninstalled this driver and it reinstalled itself on the next boot, but that did nothing to resolve this problem.

 

Memory leak detected with Poolmon with Tag Py28 and Nr22

I'm running windows 10 and I was able to resolve one of my memory leaks but I have detected another using Poolmon. These seem to have the tag Py28 and Nr22. I cannot seem to find either of these in the Pooltag.txt. How do I find the cause so I can resolve
it?

Tag Type Allocs Frees Diff Bytes Per Alloc

Py28 Nonp 4615 ( 0) 0 ( 0) 4615 45648592 ( 0) 9891

Nr22 Nonp 8 ( 0) 0 ( 0) 8 34343168 ( 0) 4292896

Some additional background. I upgraded to Windows 10 from Windows 8.1.

 

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.