CPU pegged @ 100 in windows update

[John Lenz]

I have on WinXP SP2 that consistently pegs the CPU @ 100% for over an hour.

Configuration:
3 GHZ Via MB
2 Gig Ram
C: 60 Gig (systemroot)
D: 130Gig (video work area)
E: 1TB (video files)

Part of Win2K3 SBS R2 domain
Managed by WSUS 3.x

When wuausev process kicks in, it grabs all CPU and runs for more than an
hour. It does this frequently during the day. On other WinXP SP2 machines,
it kicks in but only for a few minutes.

This system is where I store home movies for editing and rendering, thus the
disk space.

When it runs flat out for this long, it overheats the CPU and the system
"clicks off".

How can I manage the update scan process?

Any thoughts greatly appreciated

John

 

[- Bobb -]

I have on WinXP SP2 that consistently pegs the CPU @ 100% for over an
hour.

Configuration:
3 GHZ Via MB
2 Gig Ram
C: 60 Gig (systemroot)
D: 130Gig (video work area)
E: 1TB (video files)

Part of Win2K3 SBS R2 domain
Managed by WSUS 3.x

When wuausev process kicks in, it grabs all CPU and runs for more than
an hour. It does this frequently during the day. On other WinXP SP2
machines, it kicks in but only for a few minutes.

This system is where I store home movies for editing and rendering, thus
the disk space.

When it runs flat out for this long, it overheats the CPU and the system
"clicks off".

How can I manage the update scan process?

Any thoughts greatly appreciated

John

Until that stops, just turn it off. Period.
I turn mine on once a month and I have it set to "Check but notify before
downloading." I get a pop-up and I choose which to install and when to
install the updates.

 

[RxK]

....are you sure it's solely the update service ? ...how about Window
indexing hard disks' ?
.... in any event I'd be investigating the heat-sink and fan on the cpu, dust
clogging fins on the same etc.
I recently had a midi tower PC on the bench - owner reported it would only
run for a short while before shutting down. Popped off case side, and cpu
heat-sink had no visible fins ! ...i.e. h/s fan was blowing onto a solid
"carpet" of dust.
....secured fan blades | fully earth unit | place in driveway | "blow out"
with Electro vacuum cleaner, (forget cans of air!) | ...major dust STORM !!!
....popping the lids of optical drives and delicately cleaning, takes an
annoying amount of time !!!
....anyhow, Arctic Cooling heat-sink/fans are really good and cheap e.g.
"Freezer Pro" type - triple "scintered wick" heat-.

regards, Richard

 

[RxK]

....are you sure it's solely the update service ? ...how about Window
indexing hard disks' ?
.... in any event I'd be investigating the heat-sink and fan on the cpu, dust
clogging fins on the same etc.
I recently had a midi tower PC on the bench - owner reported it would only
run for a short while before shutting down. Popped off case side, and cpu
heat-sink had no visible fins ! ...i.e. h/s fan was blowing onto a solid
"carpet" of dust.
....secured fan blades | fully earth unit | place in driveway | "blow out"
with Electro vacuum cleaner, (forget cans of air!) | ...major dust STORM !!!
....popping the lids of optical drives and delicately cleaning, takes an
annoying amount of time !!!
....anyhow, Arctic Cooling heat-sink/fans are really good and cheap e.g.
"Freezer Pro" type - triple "scintered wick" heat-PIPES ...that should have
been.

regards, Richard

 

[Gerry]

John

Please see the advice is this link:
http://technet.microsoft.com/en-us/library/bb643196.aspx


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[HeyBub]

I have on WinXP SP2 that consistently pegs the CPU @ 100% for over an
hour.
Configuration:
3 GHZ Via MB
2 Gig Ram
C: 60 Gig (systemroot)
D: 130Gig (video work area)
E: 1TB (video files)

Part of Win2K3 SBS R2 domain
Managed by WSUS 3.x

When wuausev process kicks in, it grabs all CPU and runs for more
than an hour. It does this frequently during the day. On other WinXP
SP2 machines, it kicks in but only for a few minutes.

This system is where I store home movies for editing and rendering,
thus the disk space.

When it runs flat out for this long, it overheats the CPU and the
system "clicks off".

How can I manage the update scan process?

Any thoughts greatly appreciated

That's absurd. Windows update takes but a few minutes once a month (as you
see on your other machines).

More likely the bot herder has directed your machine to launch 250,000
emails touting a do-it-yourself tattoo kit.

 

[RxK]

...didn't you cast your eye down through this thread ? ....looks like
"Gerry" pegged it !

regards, Richard

 

[Thee Chicago Wolf]

I have on WinXP SP2 that consistently pegs the CPU @ 100% for over an hour.

Configuration:
3 GHZ Via MB
2 Gig Ram
C: 60 Gig (systemroot)
D: 130Gig (video work area)
E: 1TB (video files)

Part of Win2K3 SBS R2 domain
Managed by WSUS 3.x

When wuausev process kicks in, it grabs all CPU and runs for more than an
hour. It does this frequently during the day. On other WinXP SP2 machines,
it kicks in but only for a few minutes.

This system is where I store home movies for editing and rendering, thus the
disk space.

When it runs flat out for this long, it overheats the CPU and the system
"clicks off".

How can I manage the update scan process?

Any thoughts greatly appreciated

John

You need to update the msi31.dll file and this will go away. Get the
update here: http://support.microsoft.com/?id=927891

- Thee Chicago Wolf