STOP 0xA Due to Buffer Overflow in NDISWAN.SYS

Last reviewed: November 20, 1997
Article ID: Q163251
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

You may experience a STOP 0x0000000A on a Windows NT computer when copying files via RAS over a SLIP (Serial Line Interface Protocol) connection.

CAUSE

If the SLIP client sends a packet that is greater than MAX_MRRU, Windows NT does not check for it and the buffer allocated overflows causing the trap.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following time stamp:

   11/17/97  04:35p                57,744 Ndiswan.sys  (Intel)
   11/17/97  04:32p               103,728 Ndiswan.sys  (Alpha)

This hotfix has been posted to the following Internet location:

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP3/wan-fix/

NOTE: The above link is one path; it has been wrapped for readability.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.


Additional query words: 4.00
Keywords : kbbug4.00 kbfix4.00 NTSrvWkst ntstop kberrmsg
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpatch


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: November 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.