Article ID: 191756 - View products that this article applies to.
This article was previously published under Q191756
This article has been archived. It is offered "as is" and will no longer be updated.
When a child window of the main window is created in a separate UI thread and the child window has the WS_SYSMENU style, when you switch to the child window's system menu by pressing the right arrow, the system stops responding and, eventually, after switching between other applications, the following blue screen STOP message may occur:
For example, if an MDI child window is running on a separate thread and you select a menu item, such as the File menu, and then press the right arrow key, the frame or application's system menu will appear (that is, where you move, size, minimize, maximize, and so on). If you press the right arrow key again, the child window's system menu will appear. After you arrow down, the menu items are not highlighted as expected. When you switch (press ALT+TAB) to another application, the system menu remains on top and does not redraw properly.
STOP: 0x0000001E (0xC0000005, 0xA000E0DC, 0x00000001, 0x000000E4)
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:
(https://support.microsoft.com/kb/152734/EN-US/ )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: 191756 - Last Review: October 10, 2013 - Revision: 2.2