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

Welcome to my morning emergency:

System is Windows 2003 SP2, operating as a terminal server. There are several printers shared from this system, and users connecting also map their locally mapped printers in their TS session. Intermittently, and sometime frequently, the print spooler service stops:

Event Type: Error
Event Source:   Application Error
Event Category: (100)
Event ID:   1000
Date:       2/24/2011
Time:       8:16:47 AM
User:       N/A
Faulting application spoolsv.exe, version 5.2.3790.4759, faulting module msvcrt.dll, version 7.0.3790.3959, fault address 0x00038efa.

I can re-start the service, and things work "normally" until it crashes again.

I have a hunch that it's one printer and/or one user causing the problem, and I've asked for detailed information from user-space to help isolate it. Is there anything else I can do to try and isolate the problem, or do you have any suggestions?

share|improve this question

Your initial reaction is probably right. I would start by uninstalling that printer used by the user, and reinstalling with the latest software. Try updating or installing .Net Framework 2.0 as I believe C++ can be a culprit, if you have some custom apps. Also, it's usually default, but check that your spooler service is set to restart on failure.

share|improve this answer
Ahh, but the problem is I don't know which user or printer it is. I'm trying to figure out which one to look at... – Tony Feb 24 '11 at 14:39
oh i see, so there are no other Events related to these problems, as far as user or profile fails? – Seth Feb 24 '11 at 15:04

You can try using the Citrix StressPrinters utility (doesn't need to be a Citrix server):

Run it, and it will ask which drivers you want to test. It then installs a dummy printer with each of the selected drivers, and reports back any errors. If the server crashes on installing one of the drivers, you'll know that one is likely causing the problem. If it doesn't crash, but does report errors installing it, I'd recommend removing it temporarily and see if that fixes the crashing.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.