Fatal Exceptions W9x

The Fatal Exception errors related to 0E (that's zero E) are hard to track down.

Here is a list of Microsoft Knowledge Base Articles dealing with these types of errors:

What Are Windows 95/98 Fatal Exception Errors When you attempt to start Windows or an application inside of Windows, you may encounter errors similar to the following: A fatal exception has occurred at xxxx:xxxxxxxx Fatal exception errors are codes returned by a program in the following cases... An exception 00 has occurred at 0028: in VxD ESDI_506(01) + 00000476. This was called from 0028: in VxD VPICD(01) + .
Fatal Exception 06 Has Occurred at... During Windows 98 Setup, you may receive the following error message: A fatal exception 06 has occurred at : .
Error Message: An Exception 00 Has Occurred... When you start Windows 95, you may receive the following error message on a blue screen: An exception 00 has occurred at 0028: in VxD ESDI_506(01) + 00000476. This was called from 0028: in VxD VPICD(01) + .
Error Message: This program has caused a Fatal Exception 0D... When you start Windows (95/98), you may receive the following error message on a blue screen: WINDOWS This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated. Pressing any key causes the screen to turn black and the computer to stop responding (hang).
Error Messages Encountered with Low Disk Space When you start Windows 98, you may receive the following error message: Windows encountered an error accessing the system registry. Windows will restart and repair the system registry for you. If you then click OK, you may receive the following error message: Explorer caused an invalid page fault in module Kernel32.dll at 015f:bff711be. This program has performed an illegal operation and will be shutdown.
Fatal Exception 03H... Error Message During Windows 98 Setup When you install Windows 98, you may receive one of the following error messages when your computer first restarts during Setup: MPREXE.EXE caused an exception 03H in module USER32.DLL at USR32.EXE caused an exception 03H in module USER32.DLL at
Fatal Exception 0D Error Message Installing Program When you are installing any program that uses the Windows Install wizard or the InstallShield installation program, you may receive the following error message: A Fatal Exception Error 0D has occurred in VxD VMM(01) + 00001840
Fatal Exception 0E Error Message Attempting to Open Folder When you try to open a folder on your computer, you may receive one of the following error messages: A fatal exception 0E has occurred at 0137:BFF9A3C0 -or- A fatal exception 0E has occurred at 0137:BFF9A07C You may also receive one of these error messages when you start your computer.
Fatal Exception 0E Error Message When Running McAfee VirusScan When McAfee VirusScan95 with VShield scanning software detects a virus on your computer, you may receive the following error message: A fatal exception 0E has occurred at 0028:C0003C72 in VXD VMM(01) + 00002C72. The current application will be terminated. NOTE: In addition to this error message, your computer may stop responding (hang) or restart when a virus is detected.
Fatal Exception 0E Error Message When You Start Windows 95 When you start Windows 95, you may receive the following error message: A Fatal Exception 0E has occurred at 0137:. The current application will be terminated. If you press a key to continue, one of the following symptoms may occur: You receive the following error message: A Fatal Exception 0C has occurred at 0137:. The current application will be terminated. Your computer is restarted. NOTE: This error message also occurs in Safe mode.
Fatal Exception 0E May Occur During Critical Suspend On a computer equipped with advanced power management (APM), a "Fatal Exception 0E" error may occur in VPOWERD if a critical suspend occurs while the computer is already in the process of suspending normally.
Fatal Exception Error in VREDIR with DCOM Program When you are running a DCOM (Distributed Component Object Model) client program in Windows 95 in a mixed Novell NetWare and Microsoft Windows NT networking environment, a blue screen with the following error message may occur when you are connecting to a DCOM server program running on a Windows NT server or workstation: Fatal exception 0E at 0028:in VXD VREDIR (04) + 00005A8D. The current application will be terminated.
Fatal Exception Error Suspending and Resuming with MSDLC32 If 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: in VxD VMM(06) +
Fatal Exception Error When Opening or Closing Control Panel If a scanner is installed in your computer, any or all of the following symptoms may occur: When you attempt to open or close Control Panel, or when you remove Network components in Network properties and then restart Windows 95/98, you receive on of the following error messages: A fatal exception 0E has occurred at 0028:C029F7A1 in VXD IFSMGR(04) + 0000D4F1. or: A fatal exception 0E has occurred at 0028:c0274274 in VXD IFSMGR(03) + 000CF7C.
Fatal Exception Error with Iomega IDE Zip Drives When you are using an Intel motherboard with an AMI/Intel BIOS or an Iomega IDE Zip drive installed on the secondary IDE channel, you may receive a "Fatal Exception Error" error message when you start the computer without a disk in the Zip drive or you eject the disk from the Zip drive.
Fatal Exception in CDVSD Starting Windows 98 When you start your computer, you may receive the following error message on a blue screen: An exception 0E has occurred at 0028:C143EADA in VXD CDVSD(01) + 00001CFA. This was called from 0028:C18413E8 in VXD voltrack(04)+ 00000A18. It may be possible to continue normally.
Random Fatal Exception Errors While Running Windows 95/98 Windows reports random "Fatal Exception Error 0x:xxxxxxxx" error messages even though your previous version of Windows or Windows for Workgroups did not.

If you are running with an AMD or Intel chip, you should also note that there have been quite a number of reports of a faulty L1 cache (the cache on the chip).

Go into your computer's BIOS (see your handbook for instructions), and disable the Level 1 cache. If this resolves your problems, consider buying a new CPU.

Some (older) AMD K6-2 chips over 60ºC (140ºF) will produce a FATAL EXCEPTION OE ...0028:C0005338 IN VXD VMM(01)+00004338 (or similar) errors. So if you are running a K6-2 chip, it's another area to check!

A common cause for these error messages is faulty physical memory (RAM) on the computer. It is possible that you have had faulty RAM in your computer, without it affecting you. But because Windows 9x uses your memory in a different way, it is possible that the fault may show up.