Re: CPU pegged @ 100 in windows update
- From: "RxK" <nospam@xxxxxxxxxxx>
- Date: Thu, 3 Apr 2008 22:41:22 +0100
...didn't you cast your eye down through this thread ? ....looks like
"Gerry" pegged it !
regards, Richard
"HeyBub" <heybub@xxxxxxxxx> wrote in message
news:OsfJwJdlIHA.5208@xxxxxxxxxxxxxxxxxxxxxxx
John Lenz wrote:
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.
.
- References:
- CPU pegged @ 100 in windows update
- From: John Lenz
- Re: CPU pegged @ 100 in windows update
- From: HeyBub
- CPU pegged @ 100 in windows update
- Prev by Date: Rundll exception error involving shell32.dll and sysdm.cpl
- Next by Date: Turning Off Programs Running In Background
- Previous by thread: Re: CPU pegged @ 100 in windows update
- Next by thread: Re: Problem opening a picture in an email
- Index(es):
Relevant Pages
|
