Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Hello Everyone in ServerFault,

I am new to this website. I have been coming here to fix my own problems. I believe everyone here on this website is great. I could not find this issue anywhere. I am sure that other people had this issue. I have IBM X3850 48GB ram 2 TB of hard drives, four NIC cards. 2 Xeon 1.7 CPU. I am running VMware ESX. I believe that was the paid version if not then it is ESXI. I have 7 Servers on this server. All Window server 2003. On one of the Servers I keep on getting CPU is at 100% . So when I go into task manager and look at the processes that is going on, it is my print spooler. I have 30 different HP laserjet printers and two copiers from HP. I believe it is an driver issue, but I can't figure with one is doing this. Is there any programs for window server 2003 that finds bad print drivers.

share|improve this question

You can remove printer drivers using the "Drivers" tab of the "Server Properties" accessible from the "File" menu of the "Printers" dialog.

Unfortunately, there's no built-in tool to "find bad printer drivers". I'd start by looking at printers that have jobs "jammed" in their queues when the CPU on the server begins to spike. If no jobs are being left "jammed" you might turn on "Log spooler information events" (on the "Advanced" tab of the same "Server Properteies" dialog) and start Performance Monitor logging "% Processor Time" to a file. You should be able to correlate the spike in CPU to print jobs logged in the event log by the print spooler.

Failing all of those methods, move half of the drivers / printers to another server (which may be painful, assuming you don't use scripts or Group Policy to populate client printer lists automatically) and perform a binary search (move half, move half of the half where the failure occurred, continue) until you find the failing driver.

share|improve this answer
Thank you I will try the Performance Monitor Log. – Anonymous Jan 8 '10 at 14:37
Taking a peak at the spooler process in Process Explorer while it's running at 100% might uncover some clues as well: – Paul Kroon Jun 30 '10 at 3:07

Kyocera Australia has a "Driver Removal Tool" that lets you completely remove drivers so you know there won't be version conflicts or corrupt files incorrectly skipped during a reinstall.

I'm not aware of anything designed to check drivers for corruption, but you may be able to track down issues by process of elimination simply by trying to print to different printers in turn.

If all of your HPs are network versions you may find HP's universal driver a good fit, though I've found it sometimes troublesome to work with in the past if you're using network print servers from other manufacturers.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.