Debugging Print Spooler Crash

You may need to delete the printer driver entries that are still found in the windows registry and clean these up.
I know the windows registry entries will be different on a server but the following may give you an idea of where to look in the registry for these files:
Remove the following registry entries
Click Start, then click Run on Windows XP machines or just start typing. Type Regedit  
Win XP 32 bit systems
HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/CONTROL/PRINT/ENVIRONMENT/ Windows NT  X86 / Drivers  / version-3 / (delete entries for your model of printer)

Windows 7 64 bit choose Windows  x64 instead of Windows NT X86 in the above pathway.
Other registry entries you may delete as well.
HKLM/Sys /CurrentControlSet  / Control / Print / Printers / (delete entries for your model of printer)
HK_Users / .Default  / Software  / (look for your manufacturer of the printer and delete entries)
HKLM /Software  / (look for your manufacturer of the printer and delete entries)
Exit out of the regedit application after deleting the registry entries.

Upload the dmp file for analysis



Ded9

One of the best and full proof TechNet article for Print spooler troubleshooting :

http://blogs.technet.com/b/perfguru/archive/2008/08/06/print-spooler-crash-troubleshooting-steps.aspx

This article include print hive cleaning which is a process of removing all the 3rd party print driver ,monitor and processor.

The basic error of c0000005 is called as access violation error which means in the virtual memory address your spooler services has exceeded its limit or memory manager some how provided the virtual memory address of spooler to any other process.

Did you tried "Print driver Isolation" , this feature is available in Windows 7 and Windows2008 R2 , which gives a privilege to each driver can either run in isolated manner or in shared mode as well . So if any this spooler service is crashing because of a driver than in this it will crash the Printisolationhost.exe rather than spooler and the driver used by the printer will not work at that time however your spooler service will cater other printers request.

Details regarding this can be found at the following link :-

http://blogs.technet.com/b/askperf/archive/2009/10/08/windows-7-windows-server-2008-r2-print-driver-isolation.aspx

RustyMusty, thanks for the links. I hadn't seen the first one you posted in regards to spooler troubleshooting.

I did however see the last one you mention.  

As part of my troubleshooting prior to me deleting all of the non-standard Microsoft drivers, processors, and monitors, I setup print driver isolation on my terminals servers through a domain GPO per the steps in this document.  It seemed to slow down the spooler crashing on this one server but it still continued to occur.  I made sure the policies were being applied and I could see the print isolation happening in the task manager so I know it was working.  But after it continued to crash I decided to delete all the non-standard Microsoft drivers on there and let users just go through the Windows Easy Print driver.  It's been stable since but some desktop printers won't work through the Easy Print driver.  It looks like these desktop printers were never meant to work in an Enterprise environment on a terminal server so I'm not worried about them.  I'm going to force those users to get new printers.

I've never used WinDBG before.  Do you think that it's reading the mini dump file correctly with the symbols it has?  I used the following symbol path in WinDBG to download the current symbols:

SRV*c:\Symbols*http://msdl.microsoft.com/download/symbols