30 total posts
Some one wrote that complaint when...
They were "testing out firewalls." I can only guess there was some remnant left behind.
There is no clear fix besides "stop testing" and do the old hunt down and destroy all old firewalls and files belonging to said firewalls.
Process Explorer when used tends to leak. At least we don't have to run it too long. http://forum.sysinternals.com/forum_posts.asp?TID=11509#52076
BTW, also possibly of interest is that my 'system' process on this machine is experiencing I/O reads and page faults that are DRASTICALLY higher than my other XP systems...
Read another discussion about this.
That case looks different than mine... That guy's system process was small, but the sub processes were eating up memory. Mine is all in the system process itself...
Now you're getting somewhere.
See how all those processes are lumped under System?
You (not me) need to find out each and every one. I've spent many replies and must go now. You seem to think this is tech support but it's not. It's just a discussion forum where we can find people to help us out. You seem upset at times but I have some errands to do and will hope you find why the process under system is at 25M
I wonder if you are running a torrent app, skype or such.
I appreciate the help...
I'm still not clear how these processes could be affecting this when the same problem occurs with all those processes off. Anyways, hopefully someone else can jump in here as well.
PS, what indication have I given that I'm upset?
Your ludicrous reply.
You created the issue with some combo. It's up to you to peel back the layers until you find it.
The 22MB svchost is the clue it's some application that is using the network. Your Hijackthis log was helpful but there is far too much running still. Peel it back till its fixed. Use the scans of MBAM and SUPERANTISPYWARE to be sure.
Uninstall AVG, the firewall and stop software until you find it. This area of finding what that 22MB Svchost is up to you.
I'm not understanding...
How can this be something I've installed when a diagnostic startup has the same problem. I can run process explorer after a diagnostic startup and the 22mb svchost isn't there... nothing is there but the system at 60,000k still. If none of the applications I've installed are running, how is my system still spiked?
There is that issue with nvidia drivers.
But I missed where you share the system details.
Let's take this from another angle. What's broken? So what if this runs at 100Megabytes when we usually see 1+GB RAM machines today.
I'm not sure what you're asking
Well, as you noticed earlier, it's an atom processor, 1GB ram, 160GB hdd...
Maybe I have this machine.
I picked up an Acer Aspire One. But I can't find make or model in these posts.
Are you seeing the words in red? I went over your posts again and it's rather piecemeal as to the details.
Again, why would we worry about this memory use? What's broken, dysfunctional?
Bob, I'm not following you...
You're telling me I'm not giving you details.. but I guess I'm going to need you to tell me what details you need. It's an Eee PC in the 900 series. Anything else?
Those details are asked for everytime you post.
The words in red ask every time you post. I have the Asus Aspire One with XP, 1GB ram so let me check my too similar machine.
I asked a question and you are not replying so I must wait for that answer.
AHA! I see I have a 36MB SVCHOST running. Unlike yours it is not attached to System. So let me be clear I will not dissect why Microsoft sometimes attaches it to System and sometimes not.
But I will reveal it is affected by services that run under the System account. There is NO REASON to fix this issue.
Mystery solved1! You have a Svchost and other items running under System so it looks bigger than most.
Nothing busted, nothing broken.
Can you explain how that can solve my issue when my diagnostic startup doesn't include that svchost at all, and yet my system is still at 60,992k? I don't get it...
You found it!
In your posts you discovered that some processes are lumped under System and that bloats it's displayed memory.
This is for YOU to research why this OS sometimes puts this processes under System and sometimes not. At the end of the day it's the same total memory footprint for the OS so it's just a matter of why Microsoft does this. That is your research.
Nothing is busted here.
I did ask a question and it does need an answer.
What question was that again? If you're still talking about the 'red text' which states that I should include all my 'system info, including OS, model number and any other specifics related to the problem' I've done that. I told you my hardware config, my OS, etc. I asked you if there was something I'm leaving out and you didn't answer me...
I've asked you several times how processes that are not running could be affecting my problem, but you've not answered that. Minimal processes, with all others not running, still result in my system resource being at 60,992k.
I noted it above but let's do it for the last time.
"I've asked you several times how processes that are not running could be affecting my problem, but you've not answered that. Minimal processes, with all others not running, still result in my system resource being at 60,992k."
Because you have child processes that are under the System process (the parent process) that on the other machine are not under the System process.
It's like this math problem:
Are these equal?
1. (A+B+C+D) + E
2. (A+B+C) + D + E
I've seen this and it's not a bug, it's not anything to fix, it is just another way that processes can be organized.
It will only bother those that think it's broken.
Nothing is broke?
Yes something is broke.
The average "SYSTEM" image process should only be using about 55k in an idle state.
I have seen this issue on a few machines and yes I believe they were at one point infected with something unknown or a type of malware un-detected by AVG.
Perhaps a string of code somewhere that it should not be.
If your "SYSTEM" image process is pulling anything from 50,000k - to 70,000k - SOMETHING IS WRONG.
I have been searching the internet for answers however I have not found anything to help resolve the issue - only a bunch of bloggers conversing about it.
Let's say you're right.
Since this is seen on many Windows machines what should be done next?
I've seen this and there is not much to write except that it is there and those that look under the hood and "find things that are wrong" often lose a lot of time.
Let me share another area I've seen people lose gobs of time over. The Event Viewer. I've watched others spend years trying to correct what they think is wrong.
AVG FOR FREE
If I could have the original poster or a few more people to respond to this question, I might have found the issue.
This maybe questionable to some however there is no doubt in my mind that AVG is the CAUSE of this problem. I inspected 2 machines over the weekend having the very same instance of high memory usage under the system image.
I removed AVG on both - the problem was gone!
Get back to me people - it's AVG that is the problem.
They need to be contacted
Antivirus and memory use.
The questions swirl around where the memory should be reported. An antivirus may or should latch onto and be reported under the system memory total. I went under the hood on an AVG machine and found that AVG was tacked onto the system process. On another machine the antivirus still ate ram but was on it's own process tree.
Does it really matter which process tree the memory is consumed under?
AVG is correct culprit
I know its a late response to this issue, but this information about the high memory use being due to AVG is correct. Uninstalling AVG verified it.
AVG has addressed this issue in its free help forums; do a search for 'avg runs in memory' if one cares to read about it. AVG loads its virus database into memory so that the running AVG components can immediately access that database instantly. Like the OP, I was puzzled about what that strange 'System' process that now uses upwards of 100MB in my task list was doing there. Not sure if it is fixable, as 'bob' said it appears to be part of the normal scheme of things if you want to use AVG.
system process usage
Im also an xp user but my system process is using 90MB of my ram. Any idea as to whats going on. Ive run all kinds of viral and spyware checks all negative.
We went round and round with the discussion ending with the member disenchanted with the antivirus lumping its memory use under a system process.
system process mem usage
my system process was using from 77 up to 98 MB of memory, i suspected why so i uninstalled AVG Antivirus (it was the free version but anyway) now it is back to 244k if you're having this issue try uninstalling the avg av ... for me it helped
Can I ask?
Why is this a problem? AVG's process memory can be reported as it's own process or under that task so where's the problem?
As a programmer this looks COSMETIC and not a big issue. But consumers would and do complain about it so maybe for them they should use something else?