After not restarting/fully shutting down my computer for a bit, paged pool RAM goes up to what I think are abnormally high levels. Upon restarting my computer and letting it sit for a bit without running anything, paged pool RAM seems to stabilize at around 700MB. After using my computer normally for a bit, it goes up, and as of this post it's at 3.8GB for a 16GB system (non-paged pool seems to rest at around 200MB after a fresh restart and goes up to around 600MB after normal PC usage, if that's unusual).
I've tried following the instructions here Identifying root cause of high RAM usage in Paged Pool? and it shows "Key" and "MmSt" as the biggest causes. Entering findstr /s Key *.sys results in a list of stuff so long that some of it is cut off when I scroll up. Entering findstr /s MmSt *.sys apparently results in nothing.
What's the issue here and how can I fix it? I'm pretty sure I've updated all my drivers and Windows is completely up to date as well. My computer is running Windows 10 Home OS build 19042.685
wpr.exe -start Pool. Leave this for 1 minute, then run:wpr.exe -stop C:\pool.etl. The hope is the driver or drivers responsible for allocating but perhaps not freeing pool memory will have "leaked". Then open the trace in Windows Performance Analyzer (SDK or Store). View the Pool graphs view and sort by the Impacting Size column, and add to the right of the pool tag column the stack column. This should help name the driver responsible for the tag and the memory. – HelpingHand Dec 19 '20 at 23:21