Intermittent print spooler crash or Print jobs stuck in the print queue
Intermittent Print Spooler Crash or Print Jobs Stuck in the Print Queue
Issue description
Affected products
- Any supported Windows operating system using UPD 2.6 or lower (PCL 5, PCL, XL, and PS).
- Any older product-specific drivers.
What you will see
- Intermittent or random print spooler crash or hang that requires a restart of the print spooler service to recover printing functionality.
- Print queue shows "Printing" or “Sent to printer” withnoresponse from the printer.
- Print queue shows "spooling printing deleting" or “Sent to printer” and the job is stuck.
"Sent to Printer"
messages are normal and dependent upon the driver's language monitor. This message can appear for up to five minutes.Solution
To resolve this issue, the language monitor must be disassociated from the print driver.
How to disable the language monitor
Step | Action |
|---|---|
1 | To open the Registry Editor, right-click or tap-and-hold the Start button and then choose Run . |
2 | In the search box or Run window, type the following:
|
3 | When the Registry Editor opens, go to:
|
4 | Locate the registry key labeled Monitor , then double-click to open it. |
5 | Delete the value data and make sure its blank then click OK . |
6 | Restart the Spooler . |
How to delete the language monitor DLL from the system (Optional)
Step | Procedure |
1 | To delete the Dynamic-link library or DLL files, type the following in the search box or Run window,
|
2 | Then delete the DLLs named:
|
- Lexmark Communication Service (LCS)-dependent app (e.g., Lexmark Status Messenger ) may cease to function.
- Use Local Printer Management Agent (LPMA).
Related article
See Lexmark 3.0.3.0 Universal Print Driver release notes for the latest release notes.
Escalation
Requirement | Relevance | How to obtain |
|---|---|---|
Driver type and version | This information is used for simulation and analysis. |
|
Driver setup (Point-and-Print, Direct IP, or Local port, indicate what port type) | This information is used for simulation and analysis. | End user provided |
Customer's printing environment:
Example: Windows Server 2008 Enterprise R2 SP2 x64 with Windows 7 Professional SP1 x86 clients | This information is used for simulation and analysis. |
|
Menu Settings Page | This document contains all the printer settings and running firmware code. | a. Using the printer Control Panel – On the printer, press Menu > Reports > Menu Settings Page .b. Using the Embedded Web Server (EWS ) – Access the printer's EWS, go to Reports > Device Settings . Copy and paste the displayed information to a notepad or text editor. |
Event Log Information (System, Windows Activity, Event Logs) | This information is used for simulation and analysis. | Windows Logs (.evt or .evtx): For example: Navigate to Administrative Tools > Event Viewer > Windows Logs , and then:
Click here for more information on archiving Event logs. |
EV Ticket References
Driver performance issues should be escalated to the software engineering team for evaluation. Unconfirmed driver fixes should not be distributed without engineer approval.
EV Escalation Ticket # | Symptoms |
|---|---|
287712 | LMUD associated language monitor crashes Event Viewer example showing Langmon crash:
|
280661 |
See Slow Driver Responsiveness when Opening Printing Preferences or Print Dialog for more information. |
Additional information
Other Print Spooler Hangs or Crashes
- Drivers updated via New Driver: http://support.microsoft.com/kb/2009820
- Incorrect Non-Lexmark Print Processor selected
LEGACY ID:
SO821