spoolsv.exe process using 90-98% CPU

[Guest]

The aforementioned process is eating up my CPU and bogging my system down. I
can end the process via task manager and performance returns to normal,
except that I can't print.

There's a support article on a similar problem with Win2K Server but not for
XP2.

Any suggestions?

 

[Juan]

The article you mention for Win2000 should also apply for WXP SP2... why not
give it a try?...
Another aproach would be to change the printer driver, it may be the one
presently running is corrupted or inadecuate. There are many printer drivers
in windows XP that can run any printer but install one that seems most
compatable according to make and model... a number in printer model driver
should not cause any trouble... I have tested one printer make with other
printer make drivers, and have had acceptable results. EG: HP 950 or 970
printers with Lexmark or Cannon drivers, and they ran ok. Or you can
download an updated driver from one of many driver sites. One I download
from is http://www.driverguide.com

 

[Guest]

Heavens no. The article contains a fix with lots of new files...and I know
better than to mix OS system files!

 

[Guest]

Yes to the former. However, I find that I *can* start new local and network
print jobs; I just have to shut down spoolsv.exe again if I want to use my PC
for anything else afterward.

Haven't tried the latter.

 

[Juan]

Sorry if I didn't explain better... I didn't mean to mix win2000 fixes with
WXP.... what it meant was to apply what you can with keyboard and mouse,
specially being that SP2 articles on printer troubles are hard to find or do
not exist. Another and probabbly better aproach would be to uninstall the
printer from the Device Manager, delete it from the printers folder and
phisically remove the printer. Reboot the computer and then reinstall the
printer.


-------------------------------------

 

[Guest]

Well, you had no way of knowing what the fix entailed. But you're right,
there is precious little on the subject specific to XP and I looked at the
W2K fix to see if I could make it work for this problem.

I had hoped we had evolved past the "completely remove any trace and
re-install" approach, but perhaps you're right. I'll give that a try.