Using Socket Handle with Writefile() API Causes STOP Message

 Last reviewed: October 31, 1995
Article ID: Q138935
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

If a sockets program uses a socket handle with the Writefile() application programming interface (API) for overlapped input/output (I/O), a STOP message appears in Windows NT 3.51 after about 20 to 40 megabytes (MB) of data are transferred.

CAUSE

This problem occurs due to AFD.SYS using non-paged memory and not releasing the memory.

WORKAROUND

To work around this problem, use the SETSOCKOPT function to set the send buffer size (SO_SNDBUF option) to zero.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbprg kbbug3.51
KBSubcategory: nt32ap nt16ap
Additional reference words: prodnt 3.51 Winsock Socket Sock

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: October 31, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.