Microsoft KB Archive/228538

= STOP 0x1E in Rdr.sys When DormantFileLimit Set to 0 =

Article ID: 228538

Article Last Modified on 2/26/2007

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q228538



SYMPTOMS
If you change the redirector's (Rdr.sys) registry entry for DormantFileLimit to 0, a Stop:0x0000001E blue screen error message similar to the following may be displayed:

STOP:0x0000001E(C0000005,0xFEF68219,0x00000000,0x00000008) KMODE_EXCEPTION_NOT_HANDLED *** Address fef68219 has base at fef55000 - rdr.sys.

The addresses may vary.



CAUSE
This problem occrus because Windows NT 4.0 throws an unhandled access violation when attempting to push a context record that does not exist. This unhandled access violation occurs in kernel mode (because it is in Rdr.sys), which causes Windows NT to trap with a Stop 0x0000001E error message.



Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:


 * http://www.microsoft.com/windows/servicepacks/ -or-


 * 152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for 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 the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB228538

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.