Brian is da man for stuff like this (having solved a print spooler crashing 
issue for me in the past, which I was eternally grateful for)

In the interim I've used AppSense Performance Manager to great effect in 
limiting the available CPU cycles to the Spooler service - doesn't solve the 
issue but certainly reduces the pain :-)

Cheers,


JR


Sent from my Blackberry, which may be an antique but delivers email RELIABLY

-----Original Message-----
From: Brian Desmond <[email protected]>
Sender: [email protected]: Wed, 31 Jul 2013 16:25:15 
To: [email protected]<[email protected]>
Reply-to: [email protected]
Subject: [NTSysADM] RE: Print Spooler Troubleshooting

Same offer I made last week. If you capture a hang dump (using adplus) of the 
process when it is spinning at 100%, I can have a look.

Thanks,
Brian Desmond
[email protected]<mailto:[email protected]>

w - 312.625.1438 | c - 312.731.3132

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kelsey, John
Sent: Wednesday, July 31, 2013 9:32 AM
To: '[email protected]'
Subject: [NTSysADM] Print Spooler Troubleshooting

Since the list is so quiet, here's one that I'm stuck on.

Windows 2003 server hosting a pile of printers, about 150 of them.  For some 
reason now out of the blue, the print spooler service is sucking up 100% of the 
CPU.  Print jobs eventually print, but they take f o r e v e r.  I suspect a 
bum driver somewhere, but I'm not aware of any recent changes.  Even when I 
cycle the service, it jumps to 100% within a few seconds even if its not 
currently processing a job.

Is there a way to see which printer/driver is causing the spooler service to 
spike to 100% ?  Or any other suggestions are welcome!

Thanks all!

*************************************
John C. Kelsey
DuBois Regional Medical Center
*:  814.375.3073
*  :   814.375.4005
*:   [email protected]<mailto:[email protected]>
*************************************


This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.


Reply via email to