NPMCA.SYS Causes STOP 0x0A in TCPIP.SYS

Last reviewed: September 14, 1995
Article ID: Q126724

The information in this article applies to:

Microsoft Windows NT Workstation version 3.5
Microsoft Windows NT Server version 3.5

SYMPTOMS

The following error message appears when you use TCP/IP:

   STOP 0x0A (Ox14,0x2,0x0,0xf1583318)

CAUSE

NDIS set up a send request and handed the Network Peripherals FDDI network interface card (NIC) driver the packet descriptor with a Callback Completion routine. The NIC completed the send and called NDIS but returned a NULL pointer to the descriptor (that ARP tries to free).

RESOLUTION

To correct this problem, obtain an updated NPMCA.SYS FDDI NIC driver from Network Peripherals Inc. at (408) 321-7300).

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 3.5. 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: kb3rdparty kbnetwork kbhw kbbug3.50 kbfix3.50.sp3
KBSubcategory: ntdriver ntstop nttcp
Additional reference words: prodnt 3.50

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