windows using 3gb of ram

[awhir]

hey guys , im having a problem with 7 .After about 2-3 hours from a cold boot windows will start using loads of memory on ideal , the problem is that i cant find whats using the memory ! when looking at task manager and adding up what all the programs are using it does not match with high amount being used .

im just wondering if anyone knows how to fix this probelm ?

cheers andrew

 

[ignatzatsonic]

Did you look at the memory tab of resource monitor?

You can access resource monitor from task manager. There is a link to it at the bottom of the performance tab.

 

[DarkXeno]

Hello awhir, can you help us out my filling out your system specs in your userCP and taking a few screen shots of the taskmanager to post up here so we all can take a look and help out more.

 

[awhir]

uploaded a shot and updated my specs , chhers

 

[logicearth]

What antivirus are you running? Gah I ask that a lot...but it is the first thing to strike off, IMO.

 

[Fluffy]

61 processes is quite a lot also

 

[sup3rsprt]

One or more of your programs may be leaking resources (look at the task manager "handles" and "paged" entries). Perhaps it would be a good idea to cut down on the amount of running processes, as Fluffy has hinted.

 

[whs]

There is absolutely nothing wrong judging from your snips. You cannot just add up the processes. Most of your RAM is used for caching - and that you don't see anywhere. Be glad all RAM is used. I assume it's all paid for - lol.

BTW: have a look at mine which is completely normal - there is zero free:

 

[sup3rsprt]

There is absolutely nothing wrong judging from your snips.

I beg to differ.

 

[H2SO4]

There is absolutely nothing wrong judging from your snips.

I beg to differ.

FWIW, I agree with sup3rsprt - there's so much wrong that it's a testament to his hardware and Windows that the thing is still managing to "run" at all.

Close to 3 million handles, if eyesight serves, an insane amount of paged pool.... it's possible that the AV (or another filter driver) is the cause, as logicearth said, though it may also be one or more handle leaks in process instances.

The gargantuan paged pool size is a side-effect of the handle leak. The handles themselves, plus potentially the kernel objects they're pointing to, are obviously residing in paged pool.

@Fluffy: the number of processes has nothing to do with it until you get into quadruple digits

 

[Frostmourne]

What run's at startup in the msconfig tab, or use Autoruns. What have you installed? That isn't right. Scan with superantispyware too.