Terminal Server STOP 0xA When Remote Clients Log Off

Article translations Article translations
Article ID: 214440 - View products that this article applies to.
This article was previously published under Q214440
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

You may experience the following blue screen error message when a high number of Terminal Server clients have active sessions and a client is in the process of logging off:
STOP: 0x0000000A (00000008 0000001c 00000000 80117f9c)

NOTE: The parameters in the STOP code may be different depending on your system configuration.

CAUSE

A file system notification was being freed incorrectly.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

For additional information, see the following article or articles in the Microsoft Knowledge Base:
186416 System Hang Results from Large Number of Notify Syncs

Properties

Article ID: 214440 - Last Review: October 14, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB214440

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com