Stop 0x0000000A in Tcpip.sys Caused by Invalid Fragment Bit

 Last reviewed: February 3, 1998
Article ID: Q164409
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

A computer running Windows NT may display one of the following blue screen STOP error messages while it processes a datagram packet: 

   STOP 0x0000000A IRQL_NOT_LESS_OR_EQUAL

   -or-

   STOP 0x00000019 BAD_POOL_HEADER

CAUSE

A router incorrectly set the packet fragmentation bit on a browser broadcast datagram packet. The Tcpip.sys driver attempts to reassemble this packet and causes pool memory corruption.

RESOLUTION

To resolve this problem, obtain the fix mentioned below. The new Tcpip.sys driver will now check the length field on the packet to prevent it from processing fragments that do not exist.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was 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
Microsoft has confirmed this to be a problem in Windows NT version 3.51. 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: 0x19 0xa 0x0a
Keywords : kbbug3.51 kbbug4.00 kbfix3.51 kbfix4.00 ntdriver NTPROTOCOL NTSrvWkst
Version : WinNT:3.51,4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbfix

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