Print spooler crashes

Posted on 2011-11-01
Last Modified: 2012-05-12
Hi dear,

We encounter a very special problem on our Windows 7's PCs.

Since a few weeks, every time we've tried to open a session on a domain computer, we are blocked on the welcome screen during about 5 minutes.

After we try a lot of things, we have found that the problem seems to be bound with the print spooler, indeed, when we stop it remotely, the session opens directly after.

We have changed the printer (before we had a HP LaserJet 4250n), stopped the install of it from GPO (prefecences), installed it directly on the computer, cleaned  the server registry (erased all traces of the printer and the port)

We have formatting and reinstalling all the computers but nothing change, the spooler always crashes.

Which is strange is that the problem is not percistant and difficultly reproducted (when don't know how to reproduce it)

Any Idea ?

Thank's a lot for your answers
Question by:CIAD
    LVL 17

    Accepted Solution

    Have you tried uninstalling all printers and drivers on the server you are trying to connect to

    Once completed try running an RDP session without printer mapping to the server and check the event log
    LVL 37

    Expert Comment

    Spooler problems are nearly always caused by a defective driver. As sgsm81 suggested, reinstalling the drivers should fix it.

    However, you will have to first *completely* remove the old driver. To do that, go to Printers & Faxes. First delete the printer. Then, from the File menu, select Server Properties. Click the Drivers tab and remove any instances of the printer from the list. Then reinstall.
    LVL 20

    Expert Comment

    there was an option to automatically find network printers in XP - i am not sure were this is hidden in win 7, but this problem used to occur regularly for me if this option was turned on
    LVL 7

    Assisted Solution

    To find the cause you should collect one dump of the Print Spooler service running on Win 7 clients to protect the machines from future crashes.

    Make sure the Print Spooler service is running from the Services Console...

    1. Download Debugging tools for Windows -- Install this tool... 32 BIT
    or ... 64 BIT

    2. Open elevated command prompt, go to C:\Progam Files\Debugging tools for windows --- Copy and paste this command

    cscript adplus.vbs -hang -pn spoolsv.exe -o c:\adplus_spooler_crash

    This has to be done at the time when the problem has started or the symptoms you see...

    Or easiest way is .....

    1. Download the process explorer tool on the client machine and when opening a session with the DC run this tool before crashing the process. Right click Spoolsv.exe > properties and check the threads. Copy the stack and paste it. Click OK on the warning message.

    2. Download Debugging tools for Windows

    3. Extract the Process Explorer tool.. Run the Procexp.exe .. Under Options - Configure Symbols
    DBGhelp.dll Path
    Under C:\Progam Files\Debugging tools for windows\Dbghelp.DLL
    Symbols Path:

    In both the cases go to the dump file location and zip the dump and upload it. I will see what is in there causing this. This is some driver is causing this.

    Q: As you said while making the session with the Domain Controller, how? Can you explain?
    Q: This is a DC so there is no point all users are allowed to make a session? You mean, doing \\servername\<printername> >> right click > Connect....
    Q: As suggested above, did you try removing and re-installing the printer?
    Q: Can you also export and send us the printers list?

    Q: On the client machine delete these orphan entries and reboot the Win 7 and try to reconnect. Take a backup before making any changes in the registry.


    Hope this helps..!!

    Good Luck...
    LVL 25

    Expert Comment

    by:Tony Giangreco
    I agree with hdhondt:. I had the same problem on a Windows 2003 server and had to remove all the printer drivers, clean the registry references mentioning those drivers and then installing the latest. I also removed a few checp printers from the network that I didn't trust. Like the $99 printer you find at appliance stores.

    Haven't had a problem since. Hope this helps.

    Author Comment

    Thank's for all your answers, I'll try them and tell you if it's better after !

    Author Closing Comment

    The problem was effectively a corrupted drivers problem.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Learn about cloud computing and its benefits for small business owners.
    Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
    This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum capability. This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.
    The viewer will learn how to back up with the free utility from runtime software, DriveImageXML using Windows 7. Download DriveImageXML from Open folder where it was saved: Start installation by double clicking the install scrip…

    761 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now