Article ID: 179741 - View products that this article applies to.
This article was previously published under Q179741
This article has been archived. It is offered "as is" and will no longer be updated.
If you run SNA Server on a computer with high load and you also experience network problems, the server may stop with a STOP 0x0A error in Ntoskrnl.exe.
NOTE: This problem may also happen in other situations.
In the situation above, there were code paths used in Afd.sys where data structures happened to be freed twice.
Windows NT 4.0To 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:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Windows NT 3.51To resolve this problem, obtain the following fix. This fix should have the following time stamp:
Collapse this tableExpand this table
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.
Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but is not fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.
Article ID: 179741 - Last Review: October 7, 2013 - Revision: 2.2