[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 500
  • Last Modified:

How can I figure out which driver is crashing print spooler?

I am getting the "print spooler service terminated unexpectedly" error on windows 2008 server. I am not sure how to determine which driver is causing this error but I need to as there are 15-20 different printers being used thru TS on this server.
1 Solution
Gabriel CliftonCommented:
Usually you have to go through each one, Remove a driver and test. If is not the one that crashes spooler reinstall and move on to the next one. When you find the problem driver you can check for newer drivers on the manufacturers website. Sometimes older drivers are the ones that do not crash when the new drivers are the one causing the problem.
Check event log it should tell you what driver is causing the crash

You could also download Process Monitor by Microsoft at


and then click filter Process Name and look for spoolsv.exe  

good luck!
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Spike99On-Site IT TechnicianCommented:
You might want to try removing .BUD files.

.BUD files are binary printer description files that are associated with specific drivers & they help the OS spool print jobs to the printer.  As I understand it, they shouldn't hang around after print jobs are done, but they often do not go away.  If you update the driver on a PC, then any old .BUD files can cause issues.  I've seen them cause spooler crashes many times.  Deleting them will sometimes help.

To find & delete those files:
stop the print spooler service (you can use an elevated cmd prompt, run:  net stop spooler)
browse to the System32\spool folder in your windows directory
search for *.BUD
delete all .BUD files you find older than today
restart the spooler service (at an elevated cmd prompt, run:  net start spooler)

Also, check out your running services, there are some HP services & a Brother service which can cause issues with the spooler.  In your services console, click the column heading for "Description" to re-sort the list of services by Description.  Of the services with an empty description, do you see any of these listed?

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

if you do, stop & disable them.  All of those services are known to cause issues with the spooler on terminal servers (they're usually fine on single-user workstations). Disabling the services will not prevent you from printing to the printers.

I hope this helps.
mikesmithccsAuthor Commented:
I actually got this fixed. I found in another thread where it was the universal print driver from HP. Removed that and the issues have stopped. Thanks for the help.
mikesmithccsAuthor Commented:
Found the solutions in another thread . None of the solutions in this thread were relative.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now