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" (922643)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition SP6
SYMPTOMSA 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:
PAGE_FAULT_IN_NONPAGED_AREA (50)
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.
Arguments:
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:
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
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 CAUSEThis 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
RESOLUTIONA
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. PrerequisitesYou must have installed Windows NT Server 4.0 Terminal Server
Edition SP6 to apply this hotfix. Restart informationYou must restart your computer after you apply this hotfix. Registry informationYou 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. |
| Ntkrnlmp.exe | 4.0.1381.33765 | 1,004,288 | 07-Aug-2006 | 09:12 | x86 | | Ntoskrnl.exe | 4.0.1381.33765 | 983,168 | 07-Aug-2006 | 09:12 | x86 |
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Major | Last Reviewed: | 8/22/2006 |
|---|
| Keywords: | kbfix kbQFE kbhotfixserver kbpubtypekc KB922643 kbAudITPRO |
|---|
|