STOP 0x1E in RDR.SYS When DormantFileLimit Set to 0

ID: Q228538

The information in this article applies to:

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

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. 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
The English version of this fix should have the following file attributes or later:

   Date      Time     Size      File name Platform
   -------------------------------------------------------------
   03/18/99  10:41p   264,944   Rdr.sys   x86
   03/18/99  10:40p   512,240   Rdr.sys   Alpha

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0.

Additional query words: 


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

Last Reviewed: July 2, 1999