At 10:24 AM 09/05/2007, Brian Weeden wrote:
If you use the awesome ProcessExplorer you will see that of the
multiple instances of svchost, the one that gets called by the
autoupdater is the culprit. Most likely a race condition.
Yes, I agree that this is the problem, but I'm trying to find what is
normal for a working svchost.exe. I have used the following patches:
WindowsXP-KB927891-v2-x86-ENU.exe
and
WindowsUpdateAgent30-x86.exe
both of which are available publically (at least, I found them) but
I'm not sure if they fix the problem or now. For instance, I have
one machine I ran the patch on, and svchost is now consuming 0.25% of
total CPU time, but on another machine I'm still at 11.70% of total
CPU time. Interestingly enough, the peak mem usage on the "fixed"
machine is 159,436K (a 441.06% rise over current), whilst the unfixed
is 127,012K (a 312.96% rise over current.)
T
