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

K

kjrailfan

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

Continue reading...
 
Back
Top Bottom