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

problems with spoolsv.exe using too much CPU time/memory

We're running Windows 2000 Server on one of our servers that all printers are installed on so domain users can print to them.  Recently, we've noticed that the print spooler service (spoolsv.exe) is constantly taking almost 90% of the CPU resources (it's erratic and jumps between 70 and 90+)... and I just had to stop and start the print spooler service because its memory usage grew to over 500MB (of a little over a GB of system ram) after almost 18 hours.  After a little poking around, we decided to reinstall all of the printers this weekend, but I was wondering if any of you have run into this before, or if there was anything else that might be suspect.

This doesn't seem to be consistent with any server updates, however we have reinstalled a couple suspect print drivers with no success.

Any help would be greatly appreciated.  Thank you!
0
dpsit
Asked:
dpsit
  • 2
  • 2
1 Solution
 
Nirmal SharmaSolution ArchitectCommented:
Its a system module conflict. Did you run sfc /scannow? If not run it in either Normal Mode or Safe Mode. Everything should be ok. Keep your Windows CD ready. The scan will ask you to insert Windows CD.

Let me know.

Thanks
SystmProg
0
 
dpsitAuthor Commented:
Hello SP-

Thank you for the suggestion, however I just ran sfc /scannow a few minutes ago and it did not help...

do you have any other ideas?

Thanks in advance!
0
 
Nirmal SharmaSolution ArchitectCommented:
How many printers you have attached to Windows 2000 Server?
How many printers you have?
Tell your network structure. It could be a cause of Direct or Indirect path if you are using a Network Printer and printer software installed on this server.

Let me know.

Thanks

0
 
dpsitAuthor Commented:
We have eight printers attached to our W2K server.  Two of these point to the same printer (we have had this for a while as we were took the old printer definition and pointed it to a new one).  Basically what they are are two different names for the same centralized printer.

All printers are installed on the W2K server and are shared out to the rest of our users.  So, everyone connects to the printer at \\server\printer.  All printers are attached to some sort of network card or print server, and they are installed on the server via TCP/IP port.

Let me know if you need anything else.  Thanks!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

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

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