S
Scott
I'm having a problem with Office 2003, specifically Excel, on an XP SP2
machine that I've never seen, and can find very little info on.
When Excel is open, the csrss.exe and spoolsv.exe processes both go into
very high use totaling 100% CPU usage between the two. This causes the
typical jerkiness, slow performance, lagging, etc. that you'd expect from
something maxing out the CPU. Excel doesn't even have to be the active
application, it just has to be displayed on the screen for the problem to
show itself. If left idle long enough the CPU cycles will drop down, but
come back up as soon as another windows is dragged in front of Excel, or any
work in Excel is done. If the program is minimized, the problem goes away.
I found something online mentioning the possibility of a corrupt user
profile. I deleted the user's profile, and created her a new one. This
fixed the problem for a couple of days, and then came back. I then tried
doing a complete uninstall and reinstall of Office 2003. This again fixed
the problem for a couple of days, and then came back.
When logging on with my account, which has administrative privileges to the
machine, this does not happen. Everything else on the machine appears to be
functioning properly, and there don't appear to be any unexpected/unusual
processing running. We've got a good number of other PCs with the same
Office and OS versions, all at the same patch levels, and they are fine.
Has anyone experienced this? I'm out of ideas. I'm open to any suggestions
on how to fix this or what to try next to determine what the cause might be.
Thanks.
machine that I've never seen, and can find very little info on.
When Excel is open, the csrss.exe and spoolsv.exe processes both go into
very high use totaling 100% CPU usage between the two. This causes the
typical jerkiness, slow performance, lagging, etc. that you'd expect from
something maxing out the CPU. Excel doesn't even have to be the active
application, it just has to be displayed on the screen for the problem to
show itself. If left idle long enough the CPU cycles will drop down, but
come back up as soon as another windows is dragged in front of Excel, or any
work in Excel is done. If the program is minimized, the problem goes away.
I found something online mentioning the possibility of a corrupt user
profile. I deleted the user's profile, and created her a new one. This
fixed the problem for a couple of days, and then came back. I then tried
doing a complete uninstall and reinstall of Office 2003. This again fixed
the problem for a couple of days, and then came back.
When logging on with my account, which has administrative privileges to the
machine, this does not happen. Everything else on the machine appears to be
functioning properly, and there don't appear to be any unexpected/unusual
processing running. We've got a good number of other PCs with the same
Office and OS versions, all at the same patch levels, and they are fine.
Has anyone experienced this? I'm out of ideas. I'm open to any suggestions
on how to fix this or what to try next to determine what the cause might be.
Thanks.