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


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.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don S.Commented:
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.
Spike99On-Site IT TechnicianCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Have a look at this question on EE, that has a variety of suggestions which, according to the asker, made a difference eventually...
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Spike99On-Site IT TechnicianCommented:
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.
@ 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!
lianne143Author Commented:
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

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.