PATCH: Stop 0x0000000A in Wind32k.sys xxxDDETrackWindowDying

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

SYMPTOMS

Occasionally, Stop 0x0000000A occurs in Win32k.sys during DDE cleanup as a window is closing.

CAUSE

During window termination, the current thread posted the DDE conversation partner that it was terminating. The partner thread immediately gains control and performs cleanup. The original thread regains control and attempts to use a pointer to the partner[ASCII 146]s structures to update indicators. This pointer is null because the partner already performed cleanup.

RESOLUTION

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 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 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.

Properties

Article ID: 187392 - Last Review: October 9, 2013 - Revision: 4.1
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kboswinnt400fix kbqfe kbpatch kbhotfixserver KB187392

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