Jump to content

Print Spooler Keeps Stopping


Recommended Posts

OS: Server 2000 SP4

Used as a Print Server for about 50 printers.

Print Spooler keeps stopping. Rpc services are started. Logon is set to local system and interact with desktop. Tried using domain admin account for logon but service keeps stopping anyway. I tried moving the print spooler to a partition that has a much more free space about 50gb but with no luck....

Here is an excerpt from the Dr. Watson log, it's too large to post all of it. I cant FTP either because the big wigs above our network has disabled FTP and even us, the sys admins cant enable it.

Microsoft ® Windows 2000 Version 5.00 DrWtsn32

Copyright © 1985-1999 Microsoft Corp. All rights reserved.

Application exception occurred:

App: spoolsv.exe (pid=632)

When: 11/25/2005 @ 08:06:48.656

Exception number: c0000005 (access violation)

*----> System Information <----*

Computer Name: NH_BFT1

User Name: SYSTEM

Number of Processors: 1

Processor Type: x86 Family 6 Model 11 Stepping 4

Windows 2000 Version: 5.0

Current Build: 2195

Service Pack: 4

Current Type: Uniprocessor Free

State Dump for Thread Id 0x26c

eax=7c2e4376 ebx=00000000 ecx=7c2e0070 edx=00000000 esi=00000000 edi=00000030

eip=77f88a87 esp=0006fbf0 ebp=0006fc60 iopl=0 nv up ei pl zr na po nc

cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246

function: NtReadFile

77f88a7c b8a1000000 mov eax,0xa1

77f88a81 8d542404 lea edx,[esp+0x4] ss:00889ad7=????????

77f88a85 cd2e int 2e

77f88a87 c22400 ret 0x24

77f88a8a 8bff mov edi,edi

Link to comment
Share on other sites


Hmmm - looks like spooler crashing, not stopping (access violation on a readfile usually means you've got a printer driver or processor/monitor trying to do something that's not allowed, and honestly, this isn't that uncommon). Would you be able to download / install userdump 8.1 onto that box, and create a rule for spoolsv.exe and get a dump of it crashing?

Userdump 8.1 download

Just install it, open the Process Dumper control panel icon and create a new rule for spoolsv.exe and take all the defaults. The next time the spooler crashes after that, you should get a userdump .dmp file in the default location (you can see where it puts it in the rule properties).

Link to comment
Share on other sites

sorry it took me so long to get back to you been swamped...with that dump file program I was actually I was able to drill down and figure out it was two corrupted print drivers that were causing the spoolsv.exe to crash. Thanks for your help and link!!!!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...