OK, so this looks to be almost all used in Nonpaged pool (a region of kernel memory used mostly for driver use). Now that we know it is almost all nonpaged pool, we can figure out what's going on. However, I'm going to need for you to get a rather detailed trace of your machine to figure this out using the Windows Performance Toolkit. I'll update a tutorial on this in the future, but here are the instructions on how to gather a trace tracking pool allocations.
First, you need to run the web installer for the Assessment and Deployment Kit for Windows 8.1 (even if you're on Windows 7 or Windows 8, this is the version you will want to use):
View attachment 28926
Once you click the "Download" button and run the installer, you will see a download box to specify a location - just click the "Next" button:
View attachment 28927
The only option you need to select is the "Windows Performance Toolkit", and then click the "Install" button:
View attachment 28928
It will download and install the WPT component at this point:
View attachment 28929
Once installed, you should have some new icons in your modern start screen (if you're using 8.1, you'll have to go down to the all applications list, or just type "wpr" to find it). In this screenshot, it's the icon on the bottom-left of this group:
View attachment 28930
Once you've got the Windows Performance Recorder open, uncheck the "First level triage" box, and check the "Pool Usage" box, and then click the "Start" button to start tracing:
View attachment 28931
You should see the trace window change slightly to notify you that it's started tracing the system:
View attachment 28932
Let the reproduction of the memory consumption issue run for at least a few hours, up to a day or so if necessary - however, if you notice any large spikes in memory usage during this time, you can save the trace earlier (this is going to generate a LARGE file, so the less time traced and still capture the data, the better).
Once you're comfortable memory usage has increased steadily to the point you'd consider it an obvious issue, please click the "Save" button, where you'll then be presented the ability to save the trace file:
View attachment 28933
Make sure you save it somewhere where you have LOTS of disk space available (preferably a few GB), and then click the "Save" button - it will start writing the file out to the location you specified here:
View attachment 28934
Once the file has saved successfully, click the "OK" button:
View attachment 28935
I will need you to zip up the resulting .ETL file that was saved, and upload it to a file hoster (or PM me and I'll give you an FTP location to upload) so I can download and analyze the behavior:
View attachment 28936