spooler crashes

[Guest]

Hi

We are currently exprencing a spooler crash on our W2K
Server SP4. The KB820550 fix has been applied.

These are the error messages logged,

Application popup: spoolsv.exe - Application Error : The
instruction at "0x77fcc453" referenced memory
at "0x00000000". The memory could not be "written".

followed by

Event Id 7031
The Print Spooler service terminated unexpectedly. It
has done this 1 time(s). The following corrective action
will be taken in 60000 milliseconds: Restart the service.

Any ideas ????

Thanks

 

[Bill Peele [MS]]

--------------------
From: <[email protected]>
Subject: spooler crashes
Date: Mon, 1 Mar 2004 09:04:06 -0800
Newsgroups: microsoft.public.win2000.printing

Hi

We are currently exprencing a spooler crash on our W2K
Server SP4. The KB820550 fix has been applied.

These are the error messages logged,

Application popup: spoolsv.exe - Application Error : The
instruction at "0x77fcc453" referenced memory
at "0x00000000". The memory could not be "written".

followed by

Event Id 7031
The Print Spooler service terminated unexpectedly. It
has done this 1 time(s). The following corrective action
will be taken in 60000 milliseconds: Restart the service.

Any ideas ????

Thanks
--

The most common causes of the Print Spooler service stopping are printer drivers and custom port monitors. If a new
printer or printer driver was added recently try removing it to see what happens. We can also check for a custom port
monitor by looking at HKLM\System\CurrentControlSet\Control\Print\Monitors. If there is a custom port monitor we can
export a copy of that sub-key, as a backup, and then delete the sub-key to remove the custom port monitor. We would then
need to stop and restart the Print Spooler service for this change to take affect.

If this does not resolve the issue the Print Spooler service should add an entry to the Dr Watson log and generate a User
dump file, assuming Dr Watson is still the system's default debugger and it is setup to generate the User dump file, when it
stops. The log and the dump can be used to try and determine why the Print Spooler stopped.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.