Question Locked

Spools.exe problem

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
Whenever i try to open any word document(2007 version),Its getting hangged. I checked in task manager, Spoolsv.exe is taking more than 80% of cpu usage. We r sharing a printer .
If i disconnect that printer, its working fine .
I searched in Google and i tried this .
I stopped print spooler service and i deleted
all the files in C:\WINDOWS\system32\spool\PRINTERS, then i started the print spooler service and i Mapped that shared printer.
It worked fine for 2 days.after that again i am getting the same problem.
Kindly give me a solution for this.
Is there any registry settings available to decrease the cpu usage of spools.exe?

4 replies

by Former member

spoolsv.exe hogging 99% of cpu - the fix

Go to Control Panel, Administrative Tools, Services and stop the Print Spooler. Turn off the printer. Now go to C:\WINDOWS\system32\spool\PRINTERS and delete the files there. I found '00020.SHD' and '00020.SPL'. Now turn your printer back on and restart the service. Check task manager, spoolsv.exe should be at 00%.

In my particular case the problems started occurring again after a couple days. This happened because the 'bad' spooler files were coming from another computer on the network. Once that person gave up printing that file, the madness stopped. If you are on your own, chances are it is just a corrupt print file that needs to be cleared out.

Please post back if you have any more problems or questions.
If this info is useful, please give a thumbs up. Thanks

by jharrellz

I hada sys that spoolsv was hoggin 50% of cpu time and causing hangs. Finally tracked it to Acro 8. Remove and reinstall did the trick! Good luck!

JOEOUT!

by sidekick

I had a user with a similar problem. I went so far as to write a script that would stop the spooler, clear the files, and restart the spooler. I ended up replacing her printer with a different model, and she hasn't had a problem since. I've been using the problem printer for months now for myself without any issues.

This discussion is closed to new replies.