Article ID: 243232
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
This article was previously published under Q243232
SYMPTOMS
The NTVDM for a 16-bit program may max out the PagedPool usage, which results in a "Stop 0x00000050" error message.
CAUSE
This behavior occurs when the relevant VDM's stack is modified while emulating a 16-bit Trap B. The stack is not paged in. The following list shows some of the possible stop error messages that you may encounter:
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
A fix for this issue is available for Windows NT 4.0, Terminal Server Edition, by contacting Microsoft Product Support Services.
STATUS
Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 1.
Keywords: kbhotfixserver kbqfe kbbug kbfix kbnetwork kbqfe kbwin2000sp1fix KB243232