Applications May Appear Hung or Unresponsive on Windows NT 4.0
This article was previously published under Q185736
This article has been archived. It is offered "as is" and will no longer be updated.
An application running on Windows NT 4.0 may appear to be in anunresponsive state, yet no apparent error has occurred.
A multithreaded application may use critical sections for threadsynchronization. Failure by the application to release the critical sectioncleanly, or correctly handle a failed release, may result in it retaining alock on this section. Windows NT will continue to retain this criticalsection lock because it has never been properly informed to release by thethread owner.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Article ID: 185736 - Last Review: 10/08/2013 02:46:33 - Revision: 2.2
Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB185736