The information in this article applies to:
SYMPTOMSOver a period of time, the Windows NT Spooler service stops responding (hangs) because of a lack of memory. Also, if you monitor Pool Paged Bytes with Performance Monitor, the counter shows an increasing amount of paged bytes until the Windows NT Spooler service stops responding. CAUSEThis problem occurs because of a problem in the Windows NT Graphics Device Interface that causes a memory leak when printing to the Generic Text print driver. The problem is most frequently observed when printing with SNA Server, but the leak may also occur when printing with legacy programs that use the Escape API to send data directly to the Generic Text print driver. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0. Additional query words:
Keywords : kbprint kbtool kbbug4.00 |
Last Reviewed: November 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |