Sign in with
Sign up | Sign in
Your question

Printer Spooler service crash

Last response: in Windows XP
Share
July 16, 2011 3:06:30 PM

Hello,
Had my Laserjet 120 for many years on this system and suddenly a couple of weeks ago it stopped working.

I've tried to re-install driver with out success. It says Print Spooler Services are not running so I go to Services and start it and make sure it is on Automatic mode. Then I can see the printer again but only for a short while (some seconds) before it is not running again.

Is it a hardware or software issue? If it could be solved by buying a new USB cable I'd be happy. But if I have to reboot the whole system. well, then thats what I'll do.
July 16, 2011 3:26:06 PM

In where you manage the service, go to recovery tab and select restart service after 1st, 2nd and subsequent failure. Happened to me on a window 7 machine with the audio service. I applied this fix but still finds it too annoying and decide to reboot. I still don't know what causes it but I suspect a window update stuff it up.
July 16, 2011 3:30:51 PM

Thanks, but I tried, it does not help.
Related resources
July 16, 2011 3:47:44 PM

You probably checked but still, no harm asking. Did you find out the dependent service are all startup automatic?
July 17, 2011 9:20:00 AM

The only dependency is Remote Procedure Call (RPC) and it is is running, but it has complained some times that is has not. Not lately though, and I cannot remember under which circumstances.
July 17, 2011 9:47:24 AM

I am not sure if you tried this. Can you unplug your printer and empty the content in:

C:\Windows\System32\spool\PRINTERS
C:\Windows\System32\spool\drivers

and plug printer back
July 18, 2011 7:53:19 AM

Pyree said:
I am not sure if you tried this. Can you unplug your printer and empty the content in:

C:\Windows\System32\spool\PRINTERS
C:\Windows\System32\spool\drivers

and plug printer back


No I did't try this. Should I delete the two folders color and w32x86 in the drivers folder, or just the content in these two sub-folders?
July 18, 2011 8:01:47 AM

Pyree said:
I am not sure if you tried this. Can you unplug your printer and empty the content in:

C:\Windows\System32\spool\PRINTERS
C:\Windows\System32\spool\drivers

and plug printer back


Well, I emptied PRINTER only, and it works! Thanks Pyree, your my hero today!
July 18, 2011 8:20:55 AM

No problem.
April 3, 2012 8:01:52 PM

I use Windows 7 Professional 64 bit. My problem is: Whenever I try to print something (word, pdf, or any other file); printer spooler stops working and when I check the “Devices and
Printers” all the printer drivers seem to be disappeared.



I checked the “Print Spooler” in the “Services” tool; and set the "Recovery after subsequent
failures" option to “Restart the Service”. Therefore all the printer drives coma back after 1 minute. However the spooler stops immediately again when the uncompleted printing job starts; hence I can not print anything more than a page.



Earlier in this forum, someone posted that Microsoft issued a hotfix for this problem ( hotfix 2388142) which can be downloaded from article: http://support.microsoft.com/default.aspx?scid=kb;en-US;2388142.



I downloaded this hotfix and tried to install, however it gives an error message of: “The update is not applicable to your computer” and quits installation.



I did uninstall and reinstall all the printer drives, but this did not help either.

The problem started after I reinstalled windows from a clean formatting.
I tried to restore back to that date but it also did not work...

I also tried Clean Boot as explained in: http://support.microsoft.com/kb/929135

The problem is still there even when all the services (except the Microsoft services) are disabled. Apparently a Microsoft service causes it.

Any other suggestion?
June 14, 2012 8:22:00 PM

Pyree said:
I am not sure if you tried this. Can you unplug your printer and empty the content in:

C:\Windows\System32\spool\PRINTERS
C:\Windows\System32\spool\drivers

and plug printer back



WOW, Thank you so much!

I tried so many different ways to resolve this error, but your simple solution did the job.

I really appreciate it. :D 
!