STOP 0x50 in Rdr.sys If Pathname Too Long in SMB

 Last reviewed: July 23, 1997
Article ID: Q163620
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

When you use Windows NT to access a file with an extremely long file name that is nested in a long path, the following blue screen STOP error message may occur: 

   STOP 0x00000050 (0xff737000 0x00000001 0x00000001 0x00000000)
Note: The first parameter will vary, but the last three should always be the same.

CAUSE

The Redirector (Rdr.sys) does not check the path name before sending a Query_Information server message block (SMB).

RESOLUTION

To resolve this problem, use one of the following methods:

  • Reduce the length of the path and/or the length of the filename of the file being accessed on the server.
  • Apply the Windows NT service pack mentioned in this article.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem is corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words: 4.00 0xa nwrdr hotfix
Keywords : kbfix4.00.sp3 NTSrvWkst ntstop kbbug4.00 kbbuglist kbfix4.00 kbfixlist
Version : 4.0
Platform : WINNT
Issue type : kbbug
Resolution Type : kbservicepack

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.