Print Spooler Crashing ntdll.dll - Terminal Services
i saw thread print spooler crashing here:
http://social.technet.microsoft.com/forums/en-_us/winserverprint/thread/fc1e72b0-59e4-47a5-94e1-2343d310ea5e
my issue though, bit different. might bad configuration in our servers, because all printer drivers in ntdll.dll.
background
ts #1 reported spooler error.
c:\programdata\microsoft\windows\wer\reportqueue\report167e1cb4\report.wer shows:
version=1 eventtype=appcrash eventtime=129627825090020852 reporttype=2 consent=1 response.type=4 sig[0].name=application name sig[0].value=spoolsv.exe sig[1].name=application version sig[1].value=6.0.6002.18294 sig[2].name=application timestamp sig[2].value=4c6aa29a sig[3].name=fault module name sig[3].value=ntdll.dll sig[4].name=fault module version sig[4].value=6.0.6002.18327 sig[5].name=fault module timestamp sig[5].value=4cb74dd3 sig[6].name=exception code sig[6].value=c0000005 sig[7].name=exception offset sig[7].value=0000000000048c32 dynamicsig[1].name=os version dynamicsig[1].value=6.0.6002.2.2.0.16.7 dynamicsig[2].name=locale id dynamicsig[2].value=1053 dynamicsig[22].name=additional information 1 dynamicsig[22].value=9cb5 dynamicsig[23].name=additional information 2 dynamicsig[23].value=145d9fbf1f8a9ac1efbf3328efe8a163 dynamicsig[24].name=additional information 3 dynamicsig[24].value=1092 dynamicsig[25].name=additional information 4 dynamicsig[25].value=8cbce6630aef0464e4c05a38e802223c ui[2]=c:\windows\system32\spoolsv.exe ui[5]=check online solution (recommended) ui[6]=check solution later (recommended) ui[7]=close ui[8]=spooler subsystem app stopped working , closed ui[9]=a problem caused application stop working correctly. windows notify if solution available. ui[10]=&close file[0].cabname=spooler.xml file[0].path=spooler.xml file[0].flags=8454146 file[0].type=5 file[1].cabname=spooleretw.etl file[1].path=spooleretw.etl file[1].flags=8454146 file[1].type=5 file[2].cabname=version.txt file[2].path=werfca6.tmp.version.txt file[2].flags=65538 file[2].type=5 file[3].cabname=appcompat.txt file[3].path=werfcb7.tmp.appcompat.txt file[3].flags=65538 file[3].type=5 file[4].cabname=memory.hdmp file[4].path=werfde0.tmp.hdmp file[4].flags=2097152 file[4].type=3 file[5].cabname=minidump.mdmp file[5].path=wer1bad.tmp.mdmp file[5].flags=2162690 file[5].type=2 friendlyeventname=stopped working consentkey=appcrash appname=spooler subsystem app apppath=c:\windows\system32\spoolsv.exe
c:\windows\system32\printing_admin_scripts\en-us>cscript prndrvr.vbs -l |findstr /i /c:"driver name" /c:ntdll.dll
gives me installed printer drivers:
driver name zebra lp 2844,3,windows x64 driver name zdesigner tlp 2844,3,windows x64 driver name terminal services easy print,3,windows x64 driver name sharp mx-5001n ps,3,windows x64 driver name sharp ar-m451n pcl6_t1,3,windows x64 driver name sharp ar-m450 pcl6,3,windows x64 driver name sharp ar-m316 ps_t1,3,windows x64 driver name sharp ar-m316 pcl6_t1,3,windows x64 driver name rumborak pdf-writer plus,3,windows x64 driver name pdfcreator,3,windows x64 driver name pdf redirect pro,3,windows x64 driver name okipage 20plus,3,windows x64 driver name microsoft xps document writer,3,windows x64 driver name microsoft shared fax driver,3,windows x64 driver name hp universal printing pcl 5 (v5.0),3,windows x64 driver name hp laserjet professional cm1410 series pcl 6,3,windows x64 driver name hp laserjet 6p,3,windows x64 driver name hp laserjet 1100 (ms),3,windows x64 driver name hp color laserjet 4500 ps,3,windows x64 driver name hp color laserjet 2800 series ps,3,windows x64 driver name hp business inkjet 2800 ps,3,windows x64 driver name hp business inkjet 2800 pcl 5,3,windows x64 driver name hp business inkjet 1200,3,windows x64 driver name generic / text only,3,windows x64 driver name custpdf writer,3,windows x64
ideas on might going on?
really hard find out printer or driver causing error no way trace back.
hi,
please take memory footprint once clients start connecting. of memory used in spooler process talking client machines. net sess list the connecting clients or use mmc snapin shared folders.
memory go down when dump bunch of clients have printed application used print not closed , still holds active handle spooler.
have server 2008 r2 machine up for 90 days using 32mb after 619,000 print jobs 400 printers active client count minimal.
server 2003 r2 300 printers after 2 days using 8mb 1500 jobs , 8 clients.
server 2003 sp2 with 12 printers after 2 days using 16mb 300 jobs , 25 clients
so, there many factors involved.
#2
when print job causes the spooler service fail, driver related. can track down 1 failing job in cases let print driver vendor take there.
can copy jobs spool directory , restart spooler old jobs printed. if there specific job causes spooler crash during rendering, spooler happily reprint job , crash again. if restart spooler , crashes second time mark job deletion , see event 54 (i think) stating job corrupt.
drwtsn32.log , user.dmp files track down problem. not take long.
in log file fault , check match case
find fault , have file names. associated stack trace debugging user.dmp file more productive not necessary if driver file pops out @ you.
in eventlog 6162 print error, indicate gdi resource leak. 6161 error can some.
ps can stabilize print server if control printer models / drivers installed. sure delete any x86 unused print drivers (if have added x64 on x86 don't delete these) , standard tcp/ip ports.
hope helps.
如果您对我们的论坛在线支持服务有任何的意见或建议，请通过邮件告诉我们。
Windows Server > Print/Fax
Comments
Post a Comment