STOP 0xA When Using SPX

This article was previously published under Q214624
This article has been archived. It is offered "as is" and will no longer be updated.
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.
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.
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:
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:
To work around this problem, obtain the latest driver from the vendor of your network adapter.


Revert to the NDIS 3.0 driver provided by the vendor of your network adapter.
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.

n100nt.sys, hptxnt.sys, stop 0x0000000a, 4.0, e100b.sys, ndis, intel etherexpress IRQL_NOT_LESS_OR_EQUAL

Article ID: 214624 - Last Review: 11/02/2013 22:04:00 - Revision: 3.0

Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB214624