Random Stop 0x0000000A When Running IPX over Token Ring

This article was previously published under Q188414
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
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 adaptersusing the Ibmtrp.sys driver. Olicom PCI Token Ring adapters have hadreports of similar problems.

The Stop 0x0000000A seems to occur most often following an IPX send packetin the packet clean up routines. At times, the system may seem stablebefore experiencing the problem. Other times the system may fail duringstartup immediately following the load of the NWLNKSPX driver when thefirst packet attempts to be sent.
CAUSE
The cause of the problem is NDIS packet corruption caused by poolcorruption. Most often, the NDIS packet header was found to be corruptfollowing the send of the packet on the wire. In particular, the"pNdispacket->protocolReserved->srConnFile" field was found to becorrupted.
RESOLUTION
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
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.
Properties

Article ID: 188414 - Last Review: 10/09/2013 17:40:35 - 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
Feedback