Trap 0x50 and Trap 0xA Under Heavy Stress

 Last reviewed: September 7, 1996
Article ID: Q151448
The information in this article applies to:

- Microsoft Windows NT Workstation versions 3.5 and 3.51 - Microsoft Windows NT Server versions 3.5 and 3.51

SUMMARY

Trap 0x50 and 0xA occur as network connections are being torn down. The traps appear to be timing-related issues. The stackback trace should have routines contained in Afd.sys. These traps occurred under very high-stress conditions.

MORE INFORMATION

The problem occurs on Compaq multiprocessor computers and appears to be a synchronization issue processing through AFD. In one instance, a trap occurred while processing the same IO Request Packet (IRP) a second time. The IRP data was no longer valid and the associated memory had been freed. In a second instance, the failure occurred while a TCP receive indication on an aborted connection was being handled.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory:
KBSubcategory: ntdriver NTSrvWkst
Additional reference words:kbbug3.51 kbfix3.51 prodnt

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 7, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.