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

ID: Q228538

The information in this article applies to:

Microsoft Windows NT Server version 4.0
Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server versions 4.0, 4.0 SP4, Terminal Server Edition

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.

RESOLUTION

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/

Q152734 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://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Service Pack 6.

Additional query words:

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0,4.0 SP4
Platform : winnt
Issue type : kbbug