Stop 0x0000000A in NDIS.SYS on a Multi-Processor Computer

Last reviewed: September 7, 1996
Article ID: Q147204

The information in this article applies to:

Microsoft Windows NT Server version 3.51

SYMPTOMS

If a Windows NT lower level network driver completes calls asynchronously on a multiprocessor computer, the following STOP error message appears:

   STOP: 0x0000000A (0x00000015, 0x00000002, 0x00000000, 0xf94f332c) -
   NDIS.SYS

CAUSE

If the lower level network driver completes calls asynchronously, a null pointer is pushed on the stack, which causes the STOP error message above. This problem occurs at boot time or when you change the network configuration.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 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

KBCategory: kbnetwork
KBSubcategory: ntnetserv ntstop NTSrv
Additional reference words: prodnt 3.51 trap 0xA

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