Today my Toshiba Satellite started to run very very slowly. I had a few large
programs running, so I opened Task Manager to see what was taking up so much
CPU and I closed down Photoshop and Firefox. But it was the window manager
that was using so much CPU... so I switched off Aero and everything is
running fine. But everything has been fine up until now. The only thing I can
think of is that i updated my nvidia drivers for my GeForce Go 7900 the other
day when 100.64 came out, but it went the past 2 days without causing
problems. Whats up?

There were a couple of posts in other groups with this same problem
recently. I would recommend that you roll back to the previous driver.

--

Ronnie Vernon
Microsoft MVP
Windows Shell/User


"Firefox User" <(E-Mail Removed)> wrote in message
news:03A8AF9B-514C-4E85-B504-(E-Mail Removed)...
> Today my Toshiba Satellite started to run very very slowly. I had a few
> large
> programs running, so I opened Task Manager to see what was taking up so
> much
> CPU and I closed down Photoshop and Firefox. But it was the window manager
> that was using so much CPU... so I switched off Aero and everything is
> running fine. But everything has been fine up until now. The only thing I
> can
> think of is that i updated my nvidia drivers for my GeForce Go 7900 the
> other
> day when 100.64 came out, but it went the past 2 days without causing
> problems. Whats up?

Firefox User wrote:
> Today my Toshiba Satellite started to run very very slowly. I had a
> few large programs running, so I opened Task Manager to see what was
> taking up so much CPU and I closed down Photoshop and Firefox. But it
> was the window manager that was using so much CPU... so I switched
> off Aero and everything is running fine. But everything has been fine
> up until now. The only thing I can think of is that i updated my
> nvidia drivers for my GeForce Go 7900 the other day when 100.64 came
> out, but it went the past 2 days without causing problems. Whats up?

So you've got a display related issue a few days after changing display
drivers? I'd have said the most likely cause of the issue was pretty clear.