Help and Support
 

powered byLive Search

Fatal Exception 0E in WSIPX Using Windows Sockets Program

Retired KB ArticleThis 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.
View products that this article applies to.
Article ID:163329
Last Review:November 15, 2006
Revision:1.2
This article was previously published under Q163329

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.

Back to the top

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.

Back to the top

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).

Back to the top

APPLIES TO
•Microsoft Windows 95

Back to the top

Keywords: 
kbhotfixserver kbqfe kberrmsg kbnetwork kbprb KB163329

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.