Windows XP / 7 getting bogged down by SVChost (windows update)

brandonkick

Well-Known Member
Reaction score
849
So I posted a good while back about a machine I have (it's my fathers computer from his automotive repair business) that was running like crap. There was a SVC host process that would continuously suck up memory until the machine was flopping around like a fish out of water. After much research, and question asking here on the fourm, I discovered the problem to be windows update. There were two options here that came to me:

1) Disable windows update

or

2) Install more system memory and hope for the best

I had an old stick of compatabile memory lying around, so I threw that in and it took the system memory
from 2GB to 3GB (replaced one of the 1GB sticks with a 2GB stick)

The machine improved notably, and even after the SVC host process did it's dirty work the system still have some 400-500 MB free which isn't a lot at all but was enough to be able to use the system. When the system only had 2GB of memory, and SVC host sucked up everything that was still available, the system was brought too it's knees and even doing something like launching IE took 2-3 min.


I decided not to disable updates, but to max out the system memory at 4GB. It seemed that for whatever reason, windows update only sucked up a certain amount and stopped at one point. So incraseing the total system memory up past the point of where SVC host stops hogging will fix the problem.

Other times, especially where I know the people are either A) going to screw the system up in six months or less anyhow or B) are going to belly ache about having to spend money on memory upgrades, I'll simply disable windows update and tell them to turn it back on every wednesday and let it do the automatic updates then turn it back off.


My question, and the point of this whole thread, is why does this happen? It almost appears to happen randomly. I've seen 2GB memory windows 7 systems that don't have this problem even with Automatic Updates turned on and I've seen systems in the same spec range get this problem? Does anyone know what might fuel this? I mean in most cases, 2GB is a joke amount of ram and should be 4 minimum and more like 8GB for the low cost of memory but I guess I wonder why some low ram systems are affected and others aren't. I'd almost bet I could buy two Dell systems exactly the same, same OS, same software installed and one would be affected and one wouldn't.... or like three out of ten would be affected and 7 wouldn't.


Very strange indeed.
 
I've yet to find out the exact cause....
I recall towards the end of the XP years, this issue started cropping up.

I can tell you, within the past 6 months, the couple of low RAM Win7 systems that got nuked 'n paved in our office....were basically useless after the first Windows update. They wouldn't even complete. These were fresh, clean installs. I think I posted in your original thread about that. To the point now, a system with 2 gigs or less...not even worth starting the nuke 'n pave unless you have more RAM.
 
@stro

Thanks for the link, at least M$ is apparently doing something about it. I can now patch the system I described above
(because the owner has yet to pay me for the machine and in turn hasn't picked it up yet) and have a better "fix" in place.

The system won't be sluggishly slow any more, and can get proper updates.


Its a very annoying thing.

@YeOldeStonecat

I agree, 4GB min and 8GB preferred. Memory is cheap enough these days, no reason to have less than 4 and should
try to get 8.
 
What I do to fix this one is go through the painfully slow process of installing all the updates. Sometimes it takes hours, sometimes a day just to scan for the updates. After all the updates are installed it seems to go away.
 
Back
Top