New
#1
Uncontrolled RAM usage
Hi,
I am have been having some problems recently with RAM usage. Normally when my computer is just sitting at the desktop it is using about 23% of my total RAM (which is 8gb) However, within the last day or so whenever I boot up the computer will start at about the normal 23% but then work its way up to the 40-60% range.
This will happen even if I am not using the computer or even if I just let it boot up and then sit there if I come back a few hours later the RAM use is sky high. In the process manager once I click the "show processes for all users" button and sort by the amount of memory being used I get an svchost.exe at the top and the RAM usage for this process will just grow and grow and continue to grow until I restart my computer.
Again, this happens even if I don't use my computer to do anything.
When I right-click on this process and select the "go to services" option the services that are listed are:
UxSms
TrkWks
HomeGroupListener
Netman
IPBusEnum
WPDBusEnum
PcaSvc
Sysmain
AudioEndpointBuilder
wudfsvc
Malwarebytes scan and Norton scan reveal no virus or malware.
The most recent piece of software I installed was Alpha Protocol via Steam, however I did uninstall this software and re-boot to test and see if it was the problem and it still did it with it uninstalled.
I am running windows 7 home premium 64 bit fully updated
The most annoying and strange thing is that it will start off low and then just keep growing and growing until a reboot, even if I don't use programs and just let it sit at the desktop.
Sorry for the somewhat wordy description, I just didn't want to leave anything out. Any suggestions would be greatly appreciated.
(I attached a screen capture of the offending process just in case that helps out and in the picture i do realize that there are more things using my RAM there than just that process but I think you get the point)
EDIT: I just thought of this: my Norton Security Suite (provided by Comcast) just went through a MAJOR update where the whole program was basically changed. Not sure if this could be causing the problem or not, just thought I'd mention it.