Windows Sockets Program Generates Errors In WSIPX

Last reviewed: November 26, 1997
Article ID: Q145651

The information in this article applies to:

Microsoft Windows 95

SYMPTOMS

When you are running a multi-threaded Windows Sockets program using the IPX protocol, Windows 95 may stop responding (hang), or you may receive an error message similar to the following on a blue screen:

   An exception 0E has occurred at [segment]:[address] in VxD
   WSIPX(01) + [offset].  This was called from [segment]:[address]
   in VxD NWLINK(01) + [offset].  It may be possible to continue
   normally.

CAUSE

When a multi-threaded Windows Sockets program uses the IPX protocol, a page fault can occur if an invalid pointer to a buffer used by Windows Sockets over IPX is used.

Note that this error occurs only with multi-threaded Windows Sockets programs; it does not occur with single-threaded programs.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

KBCategory: kbnetwork kbpolicy
KBSubcategory: win95
Additional reference words: 95
Keywords : win95 kbnetwork kbpolicy
Version : 95
Platform : WINDOWS

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: November 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.