Windows Server 2008 R2 Thread, 2008R2 Print Spooler keeps crashing in Technical; Ive got it set to auto restart all the time for now so poeple can print intermittently, but the even ...
16th May 2011, 05:43 AM #1
2008R2 Print Spooler keeps crashing
Ive got it set to auto restart all the time for now so poeple can print intermittently, but the even log is full of this:
Its only started happening today at about 9:50am and afaik no-one changed anything
Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4e7
Faulting module name: ZSDDMUI.DLL, version: 6.1.2623.0, time stamp: 0x45df8736
Exception code: 0xc0000409
Fault offset: 0x0000000000007ce5
Faulting process id: 0xe20
Faulting application start time: 0x01cc1379cbf373d5
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\ZSDDMUI.DLL
Report Id: 41044adc-7f6d-11e0-9b90-00155d020c08
16th May 2011, 09:02 AM #2
Find out what's using "ZSDDMUI.DLL" and either stop it or isolate it and see if the problem still occours, google keeps pointing to a program called SuperPrint by Zenographics, never heard of that though.
16th May 2011, 09:09 AM #3
A quick search find this:
zsddmui.dll is a process belonging to the SuperPrint program . "zsddmui.dll is a ZSDDMUI" "belonging to SuperPrint" "from Zenographics, Inc."
Maybe see if there is an update for this SuperPrint?
16th May 2011, 09:32 AM #4
its the 2600 HP laserjet driver. I renamed zsddmui.dll to zsddmil.dead and its stopped the spooler from crashing.
I tried reinstalling the 2600 driver but am getting another error now..
16th May 2011, 09:35 AM #5
Cant you set that driver to be isolated? Should mean only that printer stops working in the event of a problem.
16th May 2011, 10:04 AM #6
Change the version of the driver you are using. like pcl5 for pcl6.
Sometimes I have had to chnag drivers several times before I fond one that will not crash
16th May 2011, 10:12 AM #7
@rikki any experience with the 2600's on x64 win7/r2 ?
These seem to have given us no end of problems
16th May 2011, 10:21 AM #8
will they work with hps universal print driver?
27th May 2011, 02:23 PM #9
After upgrading our servers to 2K8 r2 64 last August I had exactly the same problem you described above despite using new drivers and/or using the PCL 5 versions.
We have 45 laser printers mostly HP devices on the curriculum network and so, rather than keep trying to force them to work we set up a 2K3 print server instead. I know its a backward step but since then there havent been any issues like this.
13th June 2011, 09:27 PM #10
I am using a windows 2003 as a print server I admit its 32 bit with no problems. I have been told that some printers do not deploy all the time with windows 7 clients but I have not seen this yet. I have seen lots of printer spooler crash because of bad drivers. I have also seen windows 2008 machines crash on the nic card and come up with 2012 errors which can crash the connectivity and so the spooler.
If I remember rightly to fix a couple I had to update the firmware.
Yes I have used hp2600 printers.
14th June 2011, 09:32 AM #11
- Rep Power
give you the good news i also have a fleet of 40+ hp 2600 printers, well over a year ago my main "ps01" print server started fecking about... found the fault to be a windows update which when you have 2600 hp drive installed it sends the print spooler loopy. lucky did a quick swap to hyper v "Ps02" server for all machines which are not hp 2600s (e.g. the rest of the 112 unit fleet) and then set up a second "ps03" server just for the hp 2600 machines running windows 2k3 sp2 with out any updates past 2009. this worked for a while till on reboot it updated or was updated while i was off sick for 3 months. now i have to set the print spooler to have a restart every 30 minutes.
i have also got issue with windows 7 64 bit drivers for the hp 2600's as well, even thou windows has made a new driver, which was via windows update i have 2 machines running this update one works, one does not... need to sit down and spent many an hour to find the fault.
i do not to this day know which windows update causes the problem after uninstalling many updates off my "ps01" machine. which was win 2k3 sp2. i hope to one day throw them all way and do away with GDI based printers and never see them again !!!!
they dont work with my equictrac, as they are gdi printers, saying 1 page is 1400 pages long...
14th June 2011, 09:40 AM #12
That is what you need to do ^^
Originally Posted by mrbios
14th June 2011, 09:50 AM #13
- Rep Power
@ chirs or mr bios
how and i could test it here
14th June 2011, 04:03 PM #14
Driver isolation issue - as pointed out (find this in Print Management Console). HP have produced a document on driver isolation, more often than not the default isn't suitable (shared IIRC) and it needs to be isolated so that it doesn't affect spoolsv.exe. I had the issue with a 2600, just one at first then all went the same way within an hour or so. I have moved employment so no longer have access to the ticket resolution I'm afraid.
Originally Posted by ChrisH
But the HP paper did help. (!)
By RabbieBurns in forum *nix
Last Post: 13th January 2010, 05:16 PM
By jmair in forum Windows
Last Post: 29th August 2008, 09:35 AM
By burgemaster in forum Windows
Last Post: 22nd May 2008, 08:50 PM
By drewinc in forum Windows
Last Post: 22nd May 2007, 10:02 AM
By Nij.UK in forum Windows
Last Post: 16th May 2006, 11:13 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)