If you run resource monitor off the performance tab in task manager... sort by working set...I'll bet you the SYSTEM process is using it all...
most other programs WILL NOT see the system process (ntoskernel.exe), and you are left in the dark to what's going on.
I'm having the same issue... It was fine when I had 8GB memory.. but when I installed 16, SYSTEM started using 5MB commit, 3GB working set (meaning it's not paged to the page file).. and when I went up to 32GB...system started using 16+GB of working set...
The GOOD news is, if you NEED the memory, SYSTEM will give it up and drop back down to 200KB-275MB working and 5MB commit. Ive searched the web for DAYS without any reason WHY it's doing this.. I can't find one.. I called MS.. they were clueless....
but SYSTEM is ntoskernel.exe.. the Windows Kernel.. the heart and soul of windows.. but MANY ring 0 drivers use it.. and SYSTEM does a LOT of stuff.... it manages restore points, cache data, and MANY more things.
As a test, I upgraded my partners machine today from 8 to 32... SAME result... so either it's a 8.1 bug or "feature"..
The fact that it WILLINGLY gives it up once ALL free and standby memory is exhausted sounds more like a feature to me... I don't know what all it's loading to use so much... right after boot and login, it's at 3GB working set... and over about 6 hrs.. idle or not.. it creaps up to about 8GB... after a few days.. it's hogging everything.. but again.. it will release it as the system needs it.
If it were a TRUE memory leak, then it would NOT be able to release it....
So I'm guessing this is a FEATURE of 8.1
Something like... windows sees there's 16-32GB a memory..a situation that's very rare in home machines... so it's loading something.. almost like it's loading every file of the OS it can into memory for lightning fast response times....that's just a GUESS...
Google and download PRIME 95, 64bit version... go to options, torture test.. hit custom...in MEMORY TO USE enter 16000 for a 15GB machine or 32000 for a 32GB machine.. click ok.. then INSTANTLY ... pull down TEST then STOP and hover the mouse over OK...let it run for about 15 seconds then click ok about 10 times... it may take a few seconds or up to 5 minutes to respond depending on how well your pagefiles are set up (I have 3 across 3 physical drives)... What this will do is:
1) cause system to panic dump it's working set to near nothing
2) erase the entire read cache
3) swap as much of every driver, dll, service, program, etc to the pagefile(s)... on avg about 50% the entire working set on everything will be paged... and you will end up with about 1.5GB in use... and about 6GB committed.
After this, your drives will thrash again as windows brings back some data from the page files.. but after 5 mins, the disk reads end... for a while, things will be slow to start up as code has to be read in from the page file
one way to REALLY speed this up is to stick a 32GB USB 3 thumbnail drive.. format it NTFS and dedicate it to ready boost.. that sucker can read/write data faster than any sata 3 HD.. and you will have 32GB extra cache memory that doesn't get wiped out when you run low, or did what I did above.. just make sure the stick is capable of at least 200Mbytes/sec read/write speed....300-400 is better.
My page files are set up like this:
C: 2048MB (min req for a 32GB for a dump is 1600MB)
D: 2048MB
E: 28672MB
Total page files, 32GB + 32GB RAM=64GB commit limit
I've also tried NO page file, tiny page files.. HUGE page files (3TB total).. and it does NOT affect this issue.. so it's not related to overkill use of the page files
it's directly related to system RAM
Each drive is Raid 0, Sata 3, all non SSD...so I get around 200-250MB/sec read speed. which is just slightly slower than my 2 32GB readyboost usb3 thumbdrives.... under normal circumstances, they give me very little speed boost.. but when a hard drive is under heavy load, programs pop open as if the drive(s) weren't busy at all..