You are currently offline, waiting for your internet to reconnect

FIX: Error message on a computer that is running Windows NT Server 4.0 Terminal Server Edition Service Pack 6: "STOP 0x1E" or "STOP 0x50"

This article has been archived. It is offered "as is" and will no longer be updated.
A computer that is running Windows NT Server 4.0 Terminal Server Edition Service Pack 6 may unexpectedly stop several times a day when the load is high. When this issue occurs, one of the following error messages appears on a blue screen:
STOP 0x50:
Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory.
Arg1: a9f92000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 00000000, If non-zero, the instruction address which referenced the bad memory address.
Arg4: 00000001, (reserved)
STOP 0x1E:
This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arg1: c0000005, The exception code that was not handled
Arg2: 801419d3, The address that the exception occurred at
Arg3: 00000000, Parameter 0 of the exception
Arg4: 617470e5, Parameter 1 of the exception
This issue occurs because of a problem in the hotfix that is described in Microsoft Knowledge Base article 831418. After you install the hotfix that is described in article 831418, the memory that is allocated for the Win32Thread object is sometimes released two times.

For more information about the hotfix that is described in article 831418, click the following article number to view the article in the Microsoft Knowledge Base:
831418 You receive a "Stop 0x50" error message when you shut down a Windows NT 4.0-based computer
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


You must have installed Windows NT Server 4.0 Terminal Server Edition SP6 to apply this hotfix.

Restart information

You must restart your computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information

Stack Dump Information

STOP 0x50:f216cde4 8014c3cb 00000000 a9f92000 00000000 nt!MmAccessFault+0x35ef216cde4 801309f7 00000000 a9f92000 00000000 nt!KiTrap0E+0xc7f216ce90 8010b297 a9f92eb0 b1a76ee4 00000000 nt!MmFreeSpecialPool+0x51f216cebc 8010b1ef a9f92eb0 00000000 801a4433 nt!ExFreePoolWithTag+0x25f216cec8 801a4433 a9f92eb0 8015b600 b1a76dc0 nt!ExFreePool+0xbf216cef4 8014913c 0000109f 0012f9cc 00000000 nt!PsConvertToGuiThread+0x25ff45ccf10 f6a6cb42 f6a6cb9b 00000000 00000000 nt!KiEndUnexpectedRange+0xc00000000 00000000 00000000 00000000 00000000 srv!DequeueAndProcessWorkItem+0x5cSTOP 0x1E:eb838d90 8014a01d eb838dac 00000000 eb838e00 nt!KiDispatchException+0x35eeb838df8 80149fcd e264d7a8 00000000 80d13ce8 nt!CommonDispatchException+0x4deb838df8 801419d3 e264d7a8 00000000 80d13ce8 nt!KiUnexpectedInterruptTail+0x1eeeb838e88 8010b422 61746f51 00000001 00000160 nt!PsReturnPoolQuota+0x11eb838ebc 8010b1ef e264d7a8 00000000 801a4433 nt!ExFreePoolWithTag+0x1b0eb838ec8 801a4433 e264d7a8 8015b600 80da3540 nt!ExFreePool+0xbeb838ef4 8014913c 0000109f 0012f9cc 00000000 nt!PsConvertToGuiThread+0x25feb964f10 f6b0cb42 f6b0cb9b 00000000 00000000 nt!KiEndUnexpectedRange+0xc00000000 00000000 00000000 00000000 00000000 srv!DequeueAndProcessWorkItem+0x5c
More information
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
winnt stop 0x50 0x1e error exfreepooltag nt4 termsrv

Article ID: 922643 - Last Review: 10/26/2013 09:17:00 - Revision: 2.0

Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 6

  • kbnosurvey kbarchive kbfix kbqfe KB922643