Windows 10: What is causing non-paged memory leak tied to KSED, KSEE, EVEN?

I am running Windows 10 on a Surface Laptop 3. Starting approximately 2-3 months ago, I noticed the machine was extremely slow switching between applications and unlocking. After researching, I found that the non-paged pool could grow from about 300MB to 6GB overnight with nothing running. Once I closed all apps, it didn't change. But I could reboot, and the non-paged pool went back down to 300MB.


I used poolmon and identifed these three components as having massive non-paged pool growth:


Memory: 7969280K Avail: 368256K PageFlts: 4237 InRam Krnl:11256K P:331240K

Commit:8985364K Limit:16095744K Peak:9300988K Pool N:4280792K P:434068K

System pool information

Tag Type Allocs Frees Diff Bytes Per Alloc


KSee Nonp 9988845 0 339 0 9988506 1757977536 0 176

Even Nonp 56646783 25 46642308 25 10004475 1280597152 0 128

KSed Nonp 9988845 0 339 0 9988506 958896576 0 96


However, when I researched those three, I could not find anything that pinpointed the driver or where to look for more issues. I have done other recommendations scan memory, run sfc, etc. and seen on difference. I checked and updated all drivers.


Does anyone have a solution on how to determine what is causing growth in KSee, Even, and KSed?


For the "before" snapshot, here is what those three look like immediately after a reboot.


Memory: 7969280K Avail: 3734548K PageFlts: 16 InRam Krnl:11748K P:293264K
Commit:4234260K Limit:16095744K Peak:4787672K Pool N:195260K P:315296K

System pool information

Tag Type Allocs Frees Diff Bytes Per Alloc

Even Nonp 282767 1 267098 0 15669 2014720 128 128

KSed Nonp 99 0 70 0 29 2784 0 96
KSee Nonp 99 0 70 0 29 5584 0 192

:)

 

is this memory leak?

Hello RASHMIRANJAN1,

I'm an independent advisor and hope this would address your questions.

This is not a memory leak. A memory leak happens when a process or program failed to discard utilized memory when it is no longer in use. In that case, you would see a process or program consuming more and more memory over time.

I wouldn't be worried about the paged and non-paged pools as they aren't excessively large in size. The paged pool is used to store handles of kernel objects, so it is normal to have some usage there. And non-paged pool is used by kernel and drivers of the
operating system, so it is also normal for some usage there.

 

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.