New
#11
I was going to up from 16 to 32, the tech store said don't bother there is no difference - so I didnt.
I was going to up from 16 to 32, the tech store said don't bother there is no difference - so I didnt.
Then I'd suggest looking into using Rammap https://docs.microsoft.com/en-us/sys...wnloads/rammap to figure out what's going on. When you reboot your system, what does your non-paged pool memory look like compared to the picture you posted?
Hi,
Said it on page one now you ask again on page two the same thing :/
https://technet.microsoft.com/en-us/...or=-2147217396
It is better for the OS to utilize RAM than use the hard drive during its operations. Look at programs running and the percentage of RAM they are using with Process Explorer from sysinternals. It could be a memory leak or you just have something running like a P2P server, etc that is using the RAM.
When investigating these types of issues, you have to close all running programs one by one, along with using a clean boot. Just looking at the graph and going “Wow”, does not give you that much information.
Task Manager can be useful with this problem but don't use the Processes tab. This often doesn't provide sufficient information for diagnostic purposes. The memory usage it shows is not the full usage of the processes. It was never meant to. And the problem may not be a process at all, and it very often isn't.
The Details tab of Task Manager is much better. But you will need to use the "Working set" column. You may need to add it from the column context menu. RAM Map is the best tool to use but as mentioned it is not easy to use.
The Non-paged pool usage is high but this must be considered in context. This is a 32 GB system and Non-paged pool usage is generally proportional to memory size. And the usge is only a fraction of the total so it cannot be the problem. I suspect it is just a symptom of the problem.
I have a low opinion of tools like CleanMem. It doesn't solve anything but simply covers up the problem. As it unnaturally alters memory values it will make diagnostics more difficult. I would not care to diagnose a memory problem on a system on which it is running. I do have a pretty good understanding of how it works. It is not as sophisticated as it may seem. The most complex part of the program is the user interface.
This is something I could never understand... what is the objective of having 32 GB of RAM? Did you put it in there for the computer to actually use? Or did you put it in there so you can point to it and say, "Look at that! I've got 20 GB of RAM in there not being used by anything at all! "