STOP: 0x0000000A During Client Socket Disconnect

This article was previously published under Q156208
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
A computer running Windows NT 3.51 Server running client/server-basedapplications may result in a Blue Screen when the processing client socketdisconnects. You may see an error message such as:
STOP: 0x0000000A (0x000020b5, 0x00000002, 0x00000001, 0x8010da81) IRQL_NOT_LESS_OR_EQUAL
NOTE: The first parameter may differ, but the fourth parameter will be thesame on a uniprocessor system.
CAUSE
This problem has been identified in the Afd.sys driver. For instance, theNwLink Nwlnkspx.sys driver makes a reference to close a connection, and AFDdereferences the connection and sets the counter to zero. However, incertain instances Afd.sys does not handle the dereference properly andAfd.sys later tries to dereference the connection object again. This causesthe machine to stop.
RESOLUTION
Obtain the hotfix mentioned below. This problem does not occur underWindows NT version 4.0.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51.

A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specificproblem. Unless you are severely impacted by this specific problem,Microsoft recommends that you wait for the next Service Pack that containsthis fix. Contact Microsoft Technical Support for more information.
SPX 0xa 0x1e prodnt
Properties

Article ID: 156208 - Last Review: 10/01/2013 04:35:37 - Revision: 1.1

  • Microsoft Windows NT Server 3.51
  • kbnosurvey kbarchive kbinterop KB156208
Feedback