Spooler Uses 92%+ CPU When a Lexmark TCP/IP Printer Goes Offline

 Last reviewed: December 2, 1997
Article ID: Q163219
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0 -------------------------------------------------------------------------

SYMPTOMS

When using a Lexmark TCP/IP network port to print to a printer that goes offline (due to being out of paper, a paper jam, and so on), CPU usage will spike to between 92-100 percent. The process that grabs the processor time is SPOOLSS.

RESOLUTION

To avoid this excessive amount of CPU usage, do either of the following:

  • Use Lexmark DLC ports or Microsoft TCP/IP printer ports (LPR) instead of Lexmark TCP/IP.

    -or-

  • Contact Lexmark's Support line at (606) 232-3000 for a new Lexbcelm.dll file that resolves this problem.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: prodnt spooler lexmon tcpip
Keywords : ntprint NTSrvWkst kbprint
Version : 4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpending

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.