STOP 0xA When Using SPX

Article translations Article translations
Article ID: 214624 - View products that this article applies to.
This article was previously published under Q214624
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

When the SPX protocol is used with a network adapter driver that is NDIS 4.0 compliant, a STOP 0xA error message may be displayed in Ndis.sys.

Cause

This problem occurs because the Nwlnkspx.sys driver allocates its own NDIS packets. It does not call the NDIS library routines that allocate NDIS packets for protocol drivers. Because Nwlnkspx.sys allocates its own packets, it does not initialize reserved fields in the NDIS packet structure used primarily by NDIS 4.0-compliant adapter drivers.

Resolution

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • Windows Service Pack Center -or-

  • 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/contactus/?ws=support

Workaround

To work around this problem, obtain the latest driver from the vendor of your network adapter.

-or-

Revert to the NDIS 3.0 driver provided by the vendor of your network adapter.

Status

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Properties

Article ID: 214624 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB214624

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com