Tech Support > Operating Systems > directx9.0 + critical sec-updates killed performance on XP1-(Pro)
directx9.0 + critical sec-updates killed performance on XP1-(Pro)
Posted by Linda A W on August 8th, 2003


After the flurry of security updates in late July and the
Directx 9.0b update, I noticed my computer was really
running slowly. I also noticed an increasing tendancy
for Outlook 2002 to hang -- little timer shows busy, but
it will stay that way for hours -- no timeouts built-in
to the software or failsafe procedures -- only option,
often, is to kill the process.

But other symptoms -- when starting programs or redrawing
windows, my cursor will lock up for 5-10 seconds at a
time. I ran a process monitor (process explorer) at
realtime to see if i could see what was happening, but it
stops updating as well (so much or 'real time'). When
the computer comes out of the freeze, I'll see the main
copy of explorer grabbing the most CPU, but not 100, but
that could just be processing my mouse and keyboard
attempts that were backlogged.

I tried system restore -- but all restore points before
the directx9 install were somehow 'corrupt' -- none would
install. They act like they are installing, but after
reboot, they proclaim failure and that my system was
unchanged and couldn't be restored.

I've turned off font smoothing/cooltype (I've an LCD
screen) and all desktop features -- disabled any fancy
desktop addons...but no go. Everything is lead.

Have free memory and CPU isn't pegged -- max commits are
around 300Mb and I have 512Mb physical mem (and 512
additional virtual in pagefile).

Best guess is directx 9.0 since it would involve the most
video /screen driver changes, but it could have been one
of the security patches as well...dunno.

Help?
Linda

Posted by Racing Penguin on August 8th, 2003


there is an update that makes this happen. it is in the microsoft knowledge
base


Posted by Bruce Bowman on August 9th, 2003


I had similar performance problems with my computer.. would tend to slow
up, and had delayed mouse response, delayed sound responses, etc.
I finally discovered that the problem was that I had connected my palm
pilot through a USB hub rather than connecting the palm directly into
one of the 2 USB ports on the computer.. everything runs much better
since I made the change.

Bruce

Linda A W wrote:

--
_________________
Bruce T. Bowman
London, Ontario, CANADA



Similar Posts