A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Printing and Faxing with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

spoolsv.exe using 50% of CPU constantly



 
 
Thread Tools Display Modes
  #1  
Old March 18th 08, 09:39 PM posted to microsoft.public.windowsxp.print_fax
skipper[_2_]
external usenet poster
 
Posts: 14
Default spoolsv.exe using 50% of CPU constantly

Task manager tells me that the print spooler in XP Pro (spoolsv.exe) is
running constatnly and consuming fully 50% of the CPU. No other programs
running. Can you help with this problem? It only happens on one of four XP
Pro machines I use.
Ads
  #2  
Old March 19th 08, 09:16 PM posted to microsoft.public.windowsxp.print_fax
Alan Morris [MSFT]
external usenet poster
 
Posts: 783
Default spoolsv.exe using 50% of CPU constantly

Check the system eventlog for Print event 20 if one of the printers is a
connection.

Is the user not admin on the machine?



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"skipper" wrote in message
...
Task manager tells me that the print spooler in XP Pro (spoolsv.exe) is
running constatnly and consuming fully 50% of the CPU. No other programs
running. Can you help with this problem? It only happens on one of four
XP
Pro machines I use.



  #3  
Old March 26th 08, 01:11 PM posted to microsoft.public.windowsxp.print_fax
Linn Kubler
external usenet poster
 
Posts: 35
Default spoolsv.exe using 50% of CPU constantly

Hi,

I have run into this problem also and here is one possible cause. If you
have Office 2003 installed it creates a local printer called Microsoft
Office Document Image Writer. This printer object will save your print job
to a file which can be read later by the Microsoft Office Document Imaging
program. This is all well and good except when there are no other local
printers on the computer.

In our case we use all networked printers and what happens is, when a user
logs into a system for the first time there is no default printer set. So
this Microsoft Document Image Writer is automatically selected as the
printer. My users don't understand this concept and when they print
something and the Save As dialog box comes up they simply 'X' out of it.
Unfortunately, all this does is close the dialog box and not cancel the
print job.

End result, there is a print job in the Microsoft Document Image Writer
queue that the computer desperately tries to print, but can't. So it works
it's little hind end off trying to print it driving the processor
utilization up to about 80% on my systems. This job will remain there until
the user deletes it, even after reboots.

Check your print queues, look for a printer with a job pending, that's
probably your culprit.

Sorry for the long winded story but I wanted to be clear.

Hope this helps,
Linn

"skipper" wrote in message
...
Task manager tells me that the print spooler in XP Pro (spoolsv.exe) is
running constatnly and consuming fully 50% of the CPU. No other programs
running. Can you help with this problem? It only happens on one of four
XP
Pro machines I use.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 01:44 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.