Article ID: 163329 - Last Review: November 15, 2006 - Revision: 1.2

Fatal Exception 0E in WSIPX Using Windows Sockets Program

This article was previously published under Q163329
Expand all | Collapse all

SYMPTOMS

When you are using a program that uses Windows Sockets over the IPX/SPX protocol, you may receive either of the following error messages in Windows 95:
  • A fatal exception 0E has occurred at <00xx:xxxxxxxx> in VxD WSIPX(01) + <xxxxxxxx>. The current application will be terminated.
  • An exception 0E has occurred at <00xx:xxxxxxxx> in VxD WSIPX(01) + <xxxxxxxx>. This was called from <00xx:xxxxxxxx> in VxD NDIS(01) + <xxxxxxxx>. It may be possible to continue normally.

CAUSE

These errors can occur if a buffer being used by a Windows Sockets program is freed by Windows Network Sockets for IPX (WSIPX) inadvertently and the IPX/SPX-compatible protocol (NWLINK) then tries to access the buffer.

STATUS

This problem no longer occurs in Windows 98. To resolve this problem, install the current version of Windows. For information about the current version of Windows, visit http://www.microsoft.com/windows (http://www.microsoft.com/windows) .

APPLIES TO
  • Microsoft Windows 95
Keywords: 
kbhotfixserver kbqfe kberrmsg kbnetwork kbprb KB163329
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations