Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I pulled up my Task Manager today, and found that out of my 16GB of RAM, 14.5GB was "in-use".

Naturally, I switch to the Processes tab, click "show processes by all users", and sort by Working Set - only to find that all the processes listed in Task Manager together only use up ~3GB of RAM. I've also tried Process Explorer, which doesn't give me any new information.

So what's eating up almost 11GB of RAM?

I found one tool - RAMMap - which tells me that 11GB of ram is being used by "Paged Pool". What is this used for? And how can I find out what caused it to spike up so high and stay high?

Paged Pool

share|improve this question
Try killing programs and see when it dives? – soandos Feb 27 '12 at 6:23
I found this link on troubleshooting the paged pool memory hope it helps… it sounds liek it may be a device driver of some sort – Mark S. Feb 27 '12 at 13:51

Best way to see which process is eating up ram is to click on Processes tab on your Task manager.
Add a new column to it (View -> Select columns) called Working Set (Memory).

Now sort processes using this column, and you will see which process is taking up this much memory.
Should you find a process, but don't know what it is - post it here and we'll help you out.

I just saw I failed to answer to your post properly. You will need to select a column Commit Size.
This will tell you the amount of virtual memory reserved for use by a process.
It is not currently being used, so you can not see it in working set, but it is still taken away from the pool of free resources.

share|improve this answer
Any luck with this? – extremko Mar 16 '12 at 9:26
It's been more than 2 months now. Care to post results? – extremko May 4 '12 at 12:34
@FrankieA - I guess I need to include your nick in order for you to receive a message. Question answered? :) – extremko May 15 '13 at 9:33
Sorry but ... Paged pool allocated by a process will not show in its working set, nor in "commit size". And commit size shows the provite virtual memory (not RAM) that is committed , not reserved, for a process. i.e. that process's contribution to commit charge. It is also unrelated to paged pool. Reserved v.m. is just reserved addresses and takes essentially no space (and is also, you guessed it, unrelated to pool). – Jamie Hanrahan Sep 11 '15 at 18:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .