Random Stop 0x0000000A When Running IPX over Token Ring

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


Random STOP 0x0000000A error messages may occur in NDIS, NWLNKIPX, NWLNKSPX, or NTOSKRNL when running the IPX/SPX protocol over token ring.

NOTE: These problems have been experienced with IBM PCI Token Ring adapters using the Ibmtrp.sys driver. Olicom PCI Token Ring adapters have had reports of similar problems.

The Stop 0x0000000A seems to occur most often following an IPX send packet in the packet clean up routines. At times, the system may seem stable before experiencing the problem. Other times the system may fail during startup immediately following the load of the NWLNKSPX driver when the first packet attempts to be sent.


The cause of the problem is NDIS packet corruption caused by pool corruption. Most often, the NDIS packet header was found to be corrupt following the send of the packet on the wire. In particular, the "pNdispacket->protocolReserved->srConnFile" field was found to be corrupted.


To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack


Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.


Article ID: 188414 - Last Review: October 9, 2013 - Revision: 1.2
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB188414

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