Print Spooler Service uses 100% of CPU MS Server 2008 Print Server

Hi everyone,

Quick Details:
Microsoft Server 2008 Standard Edition (Not R2)
DHCP, DNS, Print Server
Virtual Machine (VMWare, ESX Version 4, VMTools installed)

Recently a change was made to my server in which a printer driver was installed without being tested and no snapshot or backup of the server was made before it was installed.

It was specifically for a Kyocera KM-5035. As far as the Driver version I believe it was KM-5035 KX.

Anyway, ever since this installation, the print spooler service is constantly eating up CPU at about 100%.

Here's what I've done so far:

1. Reinstalled the original printer. No good
2. Removed driver using Print Manager. No good.
3. Restarted Server. No good
4. Stopped sharing all printers. No good
5. Deleted printers that used the new driver. No good
6. Restarted the spooler service numerous times.
7. Went to System32/Spooler/PRNTERS and deleted and SPD and SHD files. No good

The worst part about this is that if anybody is connected to the print server, their spooler service starts eating up CPU on their workstation also. Nonetheless, trying to access a print dialog causes any application to freeze as it tries to access the print server.

I cannot delete the networked printer from their list either, as it seems to freeze again.

The only current fix I have right now is to turn off the print spooler service and allow people to work that way. Pretty much they just can't print, though it seems that those that are not connected to the 5035's can print to other printers. Otherwise, our print server is just constantly at 100% CPU usage at the moment and I can't figure out what to do.

It seems as though I have uninstalled the new printer driver, the spool service still won't return to normal.

I would prefer not to remove every driver of every printer, as there about over 30 of them. I'm hoping some experts can help me find an alternative to doing this.
happytangAsked:
Who is Participating?
 
happytangAuthor Commented:
Couldn't find an answer to my issue. Ended up just building a new print server.
0
 
nole172Commented:
Not much help, but I had that once with an HP driver and was lucky to find a manual uninstall process for the driver.  You could look for that.  Good luck.
0
 
Nenad RajsicCommented:
same thing happened to me years ago but my printers were hp.
the easiest way to remove you Kyocera drivers completely is to download them and extract those files somewhere for your reference. then see this article http://www.virtualizationadmin.com/articles-tutorials/terminal-services/printing/hunt-bad-printer-driver.html and start removing all offending files and registry keys. i know it's painful and long process but like you said you don't want to remove all the drivers. hope that helps
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
happytangAuthor Commented:
Hi,

So am I correct in assuming that I am looking at a bad printer driver? I thought that the old printer driver might have interfered with the other drivers.

I just want to make sure that that is where I should be heading, because if I need to start uninstalling print drivers, I want to be extra sure I'm putting in the time for the right thing.

Also, thanks for the quick replies.
0
 
Nenad RajsicCommented:
I can't tell you what to do but if you don't have any other solutions and you don't want to remove all the drivers and start from scratch I think your only option is to remove that Kyocera driver manually. (you seem pretty certain that your Kyocera driver is causing you problems so you have nothing to lose). My problem was with HP pcl6 driver but my situation was much more complex because all the printers on my network were from HP so removing the correct driver wasn't an easy task.

You can also backup all of your drivers and registry keys (see that article) and install just your Kyocera driver and see what happens with your print spooler service. You might want to try this option out of hours when no one is using your server. It shouldn’t take you too long. If it doesn’t work you can restore your drivers/registry keys and search for another solution.

0
 
happytangAuthor Commented:
What's up guys,

So an interesting development.

I ended up deleting ALL printers and drivers.

The spool service was still at 100%.

So I ended just removing print services in general.

Spool service dies down to 10%.

Reinstall the services, and the spool services jumps back up to 100%.

I can only assume that something has corrupted the service in general, or possibly a virus or infection of some sort. Any ideas? For the time being I've just offloaded the print server to a new VM, but I'd still like to figure what is specifically wrong with the original server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.