Excessive RAM usage, Cannot find culprit, need it fixed ASAP

[Da3droth]

So just as i said in the description, my ram fills up till there is nothing left (8GB) there are no open programs and i shut off unnecessary processes but its still right up there, here are some screen shots.
Any Help will be greatly appreciated.

 

[Layback Bear]

What is ASAP?

 

[Da3droth]

As soon as possible, please and thank you.

 

[LMiller7]

Post a screenshot of Task Manager - Processes tab showing and sorted by the "Memory - Working set" column. You will need to add this column with the "Select columns" option in the view menu. The "Memory(Private working set)" column does not show all of the processes usage.

 

[Da3droth]

I do believe this is what you are asking for?

 

[LMiller7]

As I suspected the process list shows nothing that would account for the problem. The Non paged pool seems high but not nearly high enough to account for the issue. More advanced diagnostics will be required. I don't think I can be of much further help.

 

[Tookeri]

The last screenshot says the physical memory is only 44%. Add the column Peak Working Set, that might be useful.

 

[andrew129260]

What programs are set to run as startup?

What is your virtual memory set to?

advanced system settings-performance settings-advanced tab-virtual memory Should be checked to automatically manage page file.

 

[Berton]

Windows likes to use as much RAM as possible. Yours doesn't seem out of line to me. One thing that may help is to set the Paging File/Virtual Memory to the recommended 1.5 times the installed RAM [in Search, Help and Support on Virtual Memory]. Virtual Memory allows offloading the older data from RAM to make room for newer. I also have 8GB on my Win7 and have the Virtual Memory at 12GB but it's on a second physical HDD [not a separate partition on the C: drive] and usually get a noticeable improvement playing videos.

 

[LMiller7]

The pagefile is most likely system managed. We already know that the current size of the pagefile is roughly the same size as RAM. The commit limit (currently 15 GB) is the size of RAM plus the size of the pagefile minus a small overhead. Under normal conditions the current size should be more than enough. The commit charge tells us nothing about how much of the pagefile is actually in use.

 

[Tookeri]

Recommended virtual memory size is often misleading. Windows guru Mark Russinovich from Sysinternals(Microsoft) recommends this:

So how do you know how much commit charge your workloads require? You might have noticed in the screenshots that Windows tracks that number and Process Explorer shows it: Peak Commit Charge. To optimally size your paging file you should start all the applications you run at the same time, load typical data sets, and then note the commit charge peak (or look at this value after a period of time where you know maximum load was attained). Set the paging file minimum to be that value minus the amount of RAM in your system (if the value is negative, pick a minimum size to permit the kind of crash dump you are configured for). If you want to have some breathing room for potentially large commit demands, set the maximum to double that number.
Blogs - Mark's Blog - Site Home - TechNet Blogs

 

[shadedgrey63]

Is this computer's Graphics card a Nvidia one?