I found this article on a foreign website: Tim's journal: spoolsv.exe hogging 99% of CPU-the fix
The solution is actually very simple. Suppose you have used anti-virus software to exclude viruses and anti-spyware to eliminate the impact of malware:
Just clear all the files in the C:/Windows/system32/spool/Printers directory.
The cause is also documented on the Microsoft Website: The Windows Background print program does not delete the background file of the print job. As a result, the print program may repeatedly attempt to process the print job in the background.
Solution:
To avoid this problem, do not change its properties when the printed background file is in the % SystemRoot %/system32/spool/Printers folder.
To solve this problem, delete the read-only attribute and delete the background file from the % SystemRoot %/system32/spool/Printers folder.
To delete a read-only attribute, right-click windows resource manager or a background file on my computer, click Properties, click the clear read-only check box, and then click OK.
For more information about how to delete files in Windows 2000, click Start, click Help, click the Index tab, type delete, and double-click Delete file topic.
Update:
According to flyingrufei, another method to solve the problem of repeated spoolsv occurs: The printer has a background management option to control. Open the spoolsv service (in my computer --- manage ---- service --- print spool, start), open the printer project on the control panel, right-click the printer properties --- advanced, change Background printing to direct printing --- OK!
Promotion: there should be many similar problems. If you find this method useful, please
Http://www.chedong.com/blog/archives/001117.html
Add this link to your blog:
HTML code:
<A href = "http://www.chedong.com/blog/archives/001117.html"> spoolsv.exe </a>
Postscript:
During a chat with jianshuo, I learned from Wendy, who is also working at Microsoft: this problem actually exists since Windows 2000, but it has not been solved by XP. Microsoft also has related help documents, but it is a pity that users cannot find them online, because there is no description about spoolsv accounting for 100% of CPU, so: the idea between developers and users is simply two different things.