"Fatal Exception" Error Suspending and Resuming with MSDLC32Last reviewed: July 22, 1997Article ID: Q171195 |
The information in this article applies to:
SYMPTOMSIf you are using the Microsoft 32-bit Data Link Control protocol (MSDLC32) and you suspend Windows 95 (using power management features), you may receive a "Fatal Exception 06" or "Fatal Exception 0E" error message when you resume Windows 95. The error message may be similar to the following message:
A fatal exception 0E has occurred at 0028:<xxxxxxxx> in VxD VMM(06) + <xxxxxxxx>. CAUSEMSDLC32 does not reinitialize a certain variable correctly when the computer is suspended and resumed. This variable may contain random data, resulting in unpredictable behavior when you resume the computer.
RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and Windows 95 OEM Service Release 2:
Dlc.vxd version 4.10.994 (dated 6/4/97) and laterTo install this update, follow these steps:
~ Dlc32upd.exe (size: 212640 bytes)For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q119591 TITLE : How to Obtain Microsoft Support Files from Online Services MORE INFORMATIONFor additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q170737 TITLE : Windows 95 MSDLC32 Does Not Receive Broadcast Packets ARTICLE-ID: Q170736 TITLE : Windows 95 MSDLC32 Does Not Receive Multicast Packets ARTICLE-ID: Q159344 TITLE : Fatal Exception in DLC Running Program from NetWare Server ARTICLE-ID: Q148765 TITLE : Availability of DLC Update for MSDLC32 ProtocolFor additional information about MSDLC32, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q139561 TITLE : Availability of MSDLC32 and Support Boundaries |
Additional query words: 95
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |