Fatal Exception 0E in WSIPX Using Windows Sockets Program |
Q163329
The information in this article applies to:
- Microsoft Windows 95
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.
RESOLUTION
This issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:
WSIPX.VXD version 4.00.954 dated 01/29/97 14,545 bytes WSOCK32.DLL version 4.00.953 dated 01/29/97 67,072 bytes
Versions of these files that also resolve this problem are included in the Windows Sockets 2.0 Update for Windows 95. For information about obtaining this update, see the following article in the Microsoft Knowledge Base:
Q182108 Availability of Windows Sockets 2.0 for Windows 95
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.
This issue is resolved in Microsoft Windows 98.
MORE INFORMATION
For additional information about issues resolved by updates to these components, please see the following articles in the Microsoft Knowledge Base:
Q170619 Windows 95 ServiceProvider Priority Values Not Applied
Q169035 Windows 95 WinSock Update to Improve Multihoming Support
Q157944 Domain Name Service in DUN Connection Does Not Work
Q157930 Multiple DNS Server Addresses Not Assigned Properly with DHCP
Q141211 Memory Leak with Multithreaded Winsock Programs
Q171352 Large Data Transfer Using WinSock Over SPX May Not Work
Q163378 Microsoft Exchange Hangs Sending Message Using SPX
Q161179 WinSock Zero-Length Packet Not Sent on Network
Q155675 IPX Headers Not Returned to WinSock Program
Q159254 Windows Sockets Applications Using WSIPX May Fail
For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:
Q161020 Implementing Windows 95 Updates
Keywords : kberrmsg kbnetwork win95
Issue type : kbprb
Technology : kbWin95search kbWin95
Last Reviewed: December 15, 2000 |
