Printer spooler stops on a windows 7 PC and the network printers disappear.

Posted on 2014-11-24
Last Modified: 2014-12-16

We have Windows 2008 print server with Papercut installed (Print Management software).The clients are Win 7 PC, the printers get mapped on the workstations through VB logon script. Every so often users experience printers "disappear".

When this happens I have noticed that the local print spooler has stopped. When I restart the spooler service, it starts again and when I add the printer manually again the spooler service stops.

When I restart the PC and go to printers and faxes, I can see the printers listed. If I right click the printer it doesn’t give me the printer properties.

So far when this problem happens , I came across an article says to go to the following location and delete the files within the folder 3  and restart the spooler service and when I do this  printer gets installed successfully again. This has happened twice on the same user and random users are experiencing this issue recently. This is really causing frustration with users. Sometimes the users open an office document and, not knowing that the spooler service has stopped they try to print and the word\excel application crashes and closes.


I am not sure as why this is happening and is there a permanent cure for this?
Please see the error from event viewer , when this happens.
Logname :Application
Source:Application error
Event ID:1000

Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time stamp: 0x4f35efc3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea91c
Exception code: 0xc0000374
Fault offset: 0x000c3873
Faulting process id: 0x9a8
Faulting application start time: 0x01d0080574a1389c
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a56152b0-73f9-11e4-b0bb-0016d4ace036

Event from another PC, which has similar problem
Problem signature:
 Problem Event Name:                        APPCRASH
  Application Name:                             splwow64.exe
  Application Version:                           6.1.7601.17777
  Application Timestamp:                     4f35fbfe
  Fault Module Name:                          StackHash_d187
  Fault Module Version:                        6.1.7601.18247
  Fault Module Timestamp:                  521eaf24
  Exception Code:                                  c0000374
  Exception Offset:                                00000000000c4102
  OS Version:                                          6.1.7601.
  Locale ID:                                             2057
  Additional Information 1:                  d187
  Additional Information 2:                  d1876d8deb38d6f6da352005a5c5e3bd
  Additional Information 3:                  4f7a
  Additional Information 4:                  4f7a8a4a90500da23caa90ff708752e9

Is there a way to trouble shoot this problem , please let me know if you need any further information.
Any help to sort this will be really really grateful.
Question by:lianne143
LVL 18

Assisted Solution

by:Don S.
Don S. earned 100 total points
ID: 40462788
This looks to be a classic "bad driver" situation.  The quick fix is to delete the spooled files the local system is trying to process.  That will get the spooler running again.  But as soon as you try to use the printer with the bad driver, it will crash again.  since the end user gets it's drivers from the server, you would need to change the driver on the server.  What printers/drivers do you have?  Some brands and versions are known to cause these types of issues.  Windows 7/server 2008 and above have print driver isolation which can help isolate which is the misbehaving driver.  But this is only available for newer drivers that support it.  That is where I would start.  Hope this helps.
LVL 16

Accepted Solution

Spike99 earned 200 total points
ID: 40462792
That path, C:\Windows\system32\spool\DRIVERS\x64\3, is the location where the printer drivers are installed on a 64 bit Windows OS.  I wouldn't manually delete the files in there unless you're prepared to re-install the drivers.

Do you have any brother or hp print drivers installed?  They do run port monitoring services that are known to cause print spooler issues.   These are particularly problematic on a terminal server, but I wouldn't be surprised if they caused issues on a desktop PC as well.

BrSplService  - brother print spooler service
HP Port Resolver - hp print monitor server
HP Status Server - hp print monitor server
Net Driver HPZ12 - hp print monitor server
Pml Driver HPZ12 - hp print monitor server

I would stop & disable these services if you find them on the PCs in question to see if that helps.
LVL 15

Assisted Solution

Perarduaadastra earned 200 total points
ID: 40462795
Have a look at this question on EE, that has a variety of suggestions which, according to the asker, made a difference eventually...
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

LVL 16

Assisted Solution

Spike99 earned 200 total points
ID: 40462929
That's funny: a lot of those tips in that older post were mine... :)

Checking to make sure the spooler services restarts after every failure & checking for .BUD files were going to be my next suggestions if the services weren't a factor.
LVL 15

Assisted Solution

Perarduaadastra earned 200 total points
ID: 40462997
@ Alicia W:

I noticed that too, but when I was posting I was being called to dinner so I didn't have time to say anything about it!

Author Comment

ID: 40463508
We have Ricoh and Toshiba printers , Do i need to isolate all the printer driver\do i need to isolate one by one on the server  and see if workstation causes this printing issues. If i isolate the driver and when a new PC is installed , will it pick up the drivers from the server?

Ricoh MP7502SP  -   Driver used is PCL5E
Ricoh MPC4502AD  -   Driver used is PCL5C
Ricoh MPC3002AD -   Driver used is PCL5C
Ricoh MPC300  -   Driver used is PCL5C
Toshiba  eStudio 2330C -Driver used is PSL3
Toshiba  eStudio 6530C - Driver used is PSL3


Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now