Windows 10: Windows 10, NonPaged Pool RAM, Leaking Driver

I have a driver slowly leaking in the NonPaged Pool in my RAM. I have had this problem back in October, and "refreshed" my windows install to fix it, but now it has returned, and is the same drivers.

Restarting my computer fixes momentarily, but it slowly builds up over a couple of days. I installed the stuff for PoolMon to find what the pooltag(s) were, and it showed 2 tags with the highest amount of bytes, both standing noticeably above the rest.



After finding out what the tags were, I proceeded into Command Prompt, doing the commands "cd /d %SystemRoot%\System32\Driver" and "findstr /m /l" to find the offending drivers. The tag "FMic" results in "fltMgr.sys" and "Irp" resulted in a ton an absurd amount, so I did "hIrp" which results in 7 drivers.



At this point, the issue I had 8 months ago, and the issue i have now, are basically the exact same. I still cannot figure out which driver is the offending file. Does anyone know what steps I should take at this point? If you have any questions, or need info I have not included, please ask. I wish to not have to "refresh" my windows install to fix the issue again. Thank you in advance.

:)

 

High RAM Usage Windows 10

Of concern is the nonpaged pool. It should be at a couple hundred MB. There is a memory leak caused by a driver or something. A possible cause is the Killer Network, see this

forum page.

Scroll right to the end. Basically, uninstall the Killer Suite.If it's not that then some further troubleshooting will be necessary.

Windows 10 is designed to take advantage of RAM and doesn't use the minimum. It makes things run way fast.

The Creators Update coming in about a month will have a setting for gaming mode!

 

Winsdows 10 - BSOD

EDIT: I forgot to add that there are also numerous Hardware Errors (LiveKernelEvents) happening as well - as reported in / by Reliability application.

The latest one occurred an one hour ago - and it was exactly when I was logging out from one account and getting back to another one. There's been unexpected 5 seconds of black screen after password was entered and matching event registered appeared in EventLog
at the same time.

When I checked the DMP file (under \Windows\LiveKernelReports\win32k.sys\win32k.sys-20170212-2004.dmp) with Windows Debugging Tools I have found this:

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SESSION_HAS_VALID_POOL_ON_EXIT (ab)

Caused by a session driver not freeing its pool allocations prior to a

session unload. This indicates a bug in win32k.sys, atmfd.dll,

rdpdd.dll or a video driver.

Arguments:

Arg1: 0000000000000002, session ID

Arg2: 0000000000000390, number of paged pool bytes that are leaking

Arg3: 00000000000003a0, number of nonpaged pool bytes that are leaking

Arg4: 0000000600000005, total number of paged and nonpaged allocations that are leaking.

nonpaged allocations are in the upper half of this word,

paged allocations are in the lower half of this word.

Might be a red-herring, but... Thoughts?

Needless to say I have never experienced anything like that in 3.5 years on my SONY VAIO laptop with Windows 8.1 onboard, two odd BSODs I've witnessed were the result of me crossing the line and were entirely my fault...