everytime i startup my desktop, my ram is instantly 85-90% full
Show Content
the actual processes open barely add up to over 1 GB (and right now its only at 700 MB, and the most any process is using is 300) when I add them up and I am the only user on my desktop.
How do i fix this, as its making my computer very slow
i ran mbam and nothing was wrong, cpu usage is at 2-5%, i dont know whats wrong
thanks
everytime i startup my desktop, my ram is instantly 85-90% full
[spoiler][img]http://puu.sh/s0flZ/771ac5dc60.png[/img][/spoiler]
the actual processes open barely add up to over 1 GB (and right now its only at 700 MB, and the most any process is using is 300) when I add them up and I am the only user on my desktop.
How do i fix this, as its making my computer very slow
i ran mbam and nothing was wrong, cpu usage is at 2-5%, i dont know whats wrong
thanks
Ice_Cold_Lemonadedownloadmorewam.com
this was not very helpful :(
[quote=Ice_Cold_Lemonade]downloadmorewam.com[/quote]
this was not very helpful :(
Why don't you click on the "Resource Monitor" button/link on the screen? Then you can look at the table for memory usage and see what each user process is using.
You'll likely see memory usage low in the resource monitor (matching what you saw on task mgr). "Low" as in the usage doesn't add up to 14GB. This means the leak is probably from something running in kernel mode.
Here's a pretty good resource on diagnosing the driver at fault.
http://superuser.com/questions/533135/98-100-memory-use-no-process-uses-more-than-25mb
IIRC services are sometimes a bit funky about showing up on task mgr. If you see usage in resource monitor is high due to svchost, then it's a service at fault. You can use Process Explorer from SysInternals (available on microsoft's website) to figure out which service.
Why don't you click on the "Resource Monitor" button/link on the screen? Then you can look at the table for memory usage and see what each [b]user[/b] process is using.
You'll likely see memory usage low in the resource monitor (matching what you saw on task mgr). "Low" as in the usage doesn't add up to 14GB. This means the leak is probably from something running in kernel mode.
Here's a pretty good resource on diagnosing the driver at fault.
http://superuser.com/questions/533135/98-100-memory-use-no-process-uses-more-than-25mb
IIRC services are sometimes a bit funky about showing up on task mgr. If you see usage in resource monitor is high due to svchost, then it's a service at fault. You can use Process Explorer from SysInternals (available on microsoft's website) to figure out which service.
EnderpWhy don't you just click on the "Resource Monitor" button/link on the screen? Then you can look at the table for memory usage and see what each user process is using.
You'll likely see memory usage low in the resource monitor. "Low" as in the usage doesn't add up to 14GB. This means the leak is probably from something running in kernel mode.
Here's a pretty good resource on diagnosing the driver at fault.
http://superuser.com/questions/533135/98-100-memory-use-no-process-uses-more-than-25mb
If you see usage in resource monitor is high due to svchost, then it's a service at fault. You can use Process Explorer from SysInternals (available on microsoft's website) to figure out which service.
you're correct, the usage didnt add up to 14 GB. there are a lot of svchost stuff, but all their usage is very small.
according to process explorer, MsMpEng.exe (antimalware executable by microsoft) is taking up the most private bytes-- everything else thats using memory is actual programs that im using. This service is only taking up 200 MB though
[quote=Enderp]Why don't you just click on the "Resource Monitor" button/link on the screen? Then you can look at the table for memory usage and see what each user process is using.
You'll likely see memory usage low in the resource monitor. "Low" as in the usage doesn't add up to 14GB. This means the leak is probably from something running in kernel mode.
Here's a pretty good resource on diagnosing the driver at fault.
http://superuser.com/questions/533135/98-100-memory-use-no-process-uses-more-than-25mb
If you see usage in resource monitor is high due to svchost, then it's a service at fault. You can use Process Explorer from SysInternals (available on microsoft's website) to figure out which service.[/quote]
you're correct, the usage didnt add up to 14 GB. there are a lot of svchost stuff, but all their usage is very small.
according to process explorer, MsMpEng.exe (antimalware executable by microsoft) is taking up the most private bytes-- everything else thats using memory is actual programs that im using. This service is only taking up 200 MB though
So it's a driver at fault then. The superuser link has an answer to the user's question where he suggests installing the Windows Driver Kit and running poolmon to figure out which pool is consuming the memory, and from there to figure out which driver(s) are using the pool.
You'll likely get a small list of suspect drivers, some probably packaged as part of Windows. Look at the non Microsoft drivers first because it's probably a fault from there.
Or if you have an AMD GPU you could probably just try updating or reverting to a different stable release and see if it's fixed.
So it's a driver at fault then. The superuser link has an answer to the user's question where he suggests installing the Windows Driver Kit and running poolmon to figure out which pool is consuming the memory, and from there to figure out which driver(s) are using the pool.
You'll likely get a small list of suspect drivers, some probably packaged as part of Windows. Look at the non Microsoft drivers first because it's probably a fault from there.
Or if you have an AMD GPU you could probably just try updating or reverting to a different stable release and see if it's fixed.
EnderpSo it's a driver at fault then. The superuser link has an answer to the user's question where he suggests installing the Windows Driver Kit and running poolmon to figure out which pool is consuming the memory, and from there to figure out which driver(s) are using the pool.
You'll likely get a small list of suspect drivers, some probably packaged as part of Windows. Look at the non Microsoft drivers first because it's probably a fault from there.
Or if you have an AMD GPU you could probably just try updating or reverting to a different stable release and see if it's fixed.
ill try this, thanks for the help
[quote=Enderp]So it's a driver at fault then. The superuser link has an answer to the user's question where he suggests installing the Windows Driver Kit and running poolmon to figure out which pool is consuming the memory, and from there to figure out which driver(s) are using the pool.
You'll likely get a small list of suspect drivers, some probably packaged as part of Windows. Look at the non Microsoft drivers first because it's probably a fault from there.
Or if you have an AMD GPU you could probably just try updating or reverting to a different stable release and see if it's fixed.[/quote]
ill try this, thanks for the help