Printer spooler service stop running when sent print job

[hen770]

Hi,

Every time i am sending a print job to the printer, i am don't get any response from the printer, and at the printer job list at the status of the job, i see that there was an Error, but it don't give me any clue on what could be the problem.
After some investigation i found that every time that i send the print job to the printer the printer spooler service stops to run, then after a second or two it start again (i think that this behavior is related to the printer spooler settings to rerun it self after it stops).

Things that i have tried so far:

• 
  Remove and Install again the Driver.

• 
  After removing the driver, i have removed the unnecessary registry keys according to this article from Microsoft, these are:
  • rename all files and folders in "c:\windows\system32\spool\drivers\w32x86 "
  • "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86" remove anything but Drivers Print and Processors .
  • remove anything in here "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors" but:
    • BJ Language Monitor
    • Local Port
    • Microsoft Document Imaging Writer Monitor
    • Microsoft Shared Fax Monitor
    • Standard TCP/IP Port
    • USB Monitor
    • WSD Port

• 
  Disconnect and Reconnect the Printer.

• 
  The computer is clean from Viruses & Spywares.

Currently i am stuck, i have no more things to try, if anybody know about any kind of solution please let me know about it.

Since i am want to keep this post as general problem that relate to the printer spooler, and not just my particular problem, i didn't included inside the windows version & the printer model, they are (although i think that it isn't relate just for that particular model):

• Windows 7 32bit
• HP Officejet 4500 G510g-m

Thanks.

 

[Martyn]

You need to tell us how it is connected and what port type. Network printers need specific information to print and will do nothing if it is not setup correct. Is this a new setup or was it working and stopped? Can anyone print to it? You do need to supply printer model, driver being used whether it is from a server and os printed from. This is the basic information you need to supply.

Edit just seen the bit about the service crashing. Make sure you are not short of disk space as print files can spool at a massive size. Check Event Viewer for errors. Clear out the old spool files in the spool directory.

 

[hen770]

It is a USB printer that connected just to one computer and just it print to it.
There a lot of free space, and i have cleared out the spool directory already.

 

[Martyn]

Event Viewer? ...................

 

[MobileTechie]

Anything dodgy in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr ol\Print\Providers?

Did you 100% delete the old drivers and printers before reinstalling?

I have the following in my knowledgebase, copied from a forum somewhere. It's helped in various printer situations before:

"Step 1
======
Start Windows Explorer, and then rename all files and folders in the following two folders:

c:\windows\system32\spool\drivers\w32x86

Step 2
======
1. Navigate to and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86

View the list of subkeys. There should be only the following subkeys:

Drivers
Print Processors

If there are any keys other than those listed above, follow these steps:

a. On the File menu, click Export.
b. In the File Name box, type a descriptive name for this key -- for example, type WindowsNTx86regkey -- and then click Save to save it to your local Desktop.

We can use this backup of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86 registry key to restore the key if you experience any problems after you complete this procedure.

c. Delete all keys other than Drivers and Print Processors.

Step 3
======
Navigate to and click the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors registry key. View the list of subkeys. There should be only the following subkeys:

BJ Language Monitor
Local Port
Microsoft Document Imaging Writer Monitor
Microsoft Shared Fax Monitor
Standard TCP/IP Port
USB Monitor
WSD Port

If there are any keys other than those listed in above, follow these steps to delete them:

a. On the File menu, click Export.
b. In the File Name box, type a descriptive name for this key -- for example, type Monitorsregkey -- and then click Save to save it to your local Desktop.

We can use this backup of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors registry key to restore the key if you experience any problems after you complete this procedure.

c. Delete all keys other than the 5 listed above.

Step 4. Disconnect the printer cable from the computer, and then restart the computer.

Step 5. Reconnect the printer cable to the computer, install the printer according to the manufacturer's installation instructions, and then check if the issue persists.

You can also use these two articles to troubleshoot this issue:
http://support.microsoft.com/kb/2000007
http://support.microsoft.com/kb/933454"

Might be worth looking at.

 

[hen770]

@MobileTechie : see my link at the question and is the same as what you have posted here, and i have tried it all.

 

[hen770]

Event Viewer? ...................

i should take a look on that, update soon.

 

[NETWizz]

You should not need to use Regedit. The Print Server properties allows you to delete/add ports & drivers... use that.

Some printers use a host-based (Windows Only) driver and it causes problems when some programs try to print i.e. Adobe Reader trying to print a HUGE 50 MB print job...


In these situations, a better printer that supports PCL and/or Post Script is the solution...

 

[MobileTechie]

@MobileTechie : see my link at the question and is the same as what you have posted here, and i have tried it all.

Sorry I didn't notice that little link.

I'm out of ideas. Normally these things are related to the driver.

Is it a new printer or has it worked OK previously? Anything changed?