Fatal Exception 0E Errors

If you have arrived here through a search engine, and there’s no menu to the left click here!

Resolving occasional or persistent Fatal Exception 0E (that’s zero E) Errors can be extremely difficult, and at times, even impossible, to resolve. At times, resolution can be a simple matter of a software conflict or bad drivers, while at others it could result in a complete hardware teardown in order to determine if hardware components such as the motherboard, memory or processor are at fault.

By providing the following information, we are not implying that we have assembled all the answers to your questions regarding these Fatal Exception Errors. All we have done is to assemble a list of resources we have used to combat this issue for our customers and made it available to all who visit our Knowledge Center.

First, what are Fatal Exception Errors? Rather than placing a large explanation here, the Microsoft Knowledge Base contains a reasonable article that describes these errors. Click the link to review a pop-up of the Knowledge Base article What Are Fatal Exception Errors – Q150314.

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

1. 16-Bit DMA May Cause Static or System Hang Q127022
2. Fatal Exception Errors and Random Characters Using ATI Mach 32 Q139771
3. A fatal exception 0E has occurred at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx
   Fatal Exception in VMM(06) Caused by Damaged Registry Q145836
4. Err Msg: An Exception 0E Has Occurred in Rpcss.exe… Q148804
5. An exception 0E has occurred at 00XX:XXXXXXXX in VxD VNETBIOS
   Fatal Exception 0E in VNETBIOS Using NetWare Login Script Q149606
6. Fatal exception 0E at 0028: in VxD IOS(01)+
   Fatal Exception 0E in Ios.vxd with SCSI Printer Q149563
7. Error Message: “Exception 0E in VPOWERD” During First Boot Q153395
8. Fatal exception 0E at 0028:C433442B in VXD octk16.sys (01) + 0000342B. This was called from 0028:C003C47C in VXD NDIS (01) + 00000D7C. It may be possible to continue normally.
   Fatal Exception Error Using DHCP Q158713
9. Windows Sockets Programs Using WSIPX May Not Work Q159254
10. Fatal exception 0E at 0028:C16AC573 in VXD DLC(01) + 0001C3EF. This was called from 0028:C003C47C in VXD NDIS (01) + 00000D7C.
    Fatal Exception in DLC Running Program from NetWare Server Q159354
11. “Fatal Exception 0E” May Occur During Critical Suspend Q162211 (Win95 power management)
12. A fatal exception 0E has occurred at in VxD WSIPX(01) + . The current application will be terminated. An exception 0E has occurred at in VxD WSIPX(01) + . This was called from in VxD NDIS(01) + . It may be possible to continue normally.

    Fatal Exception 0E in WSIPX Using Windows Sockets Program Q163329

13. “Exception 0E” Using MSNDS Over Dial-Up Connection Q163673 (Dial-Up Networking).
14. Fatal exception 0E at 0028: in VXD VREDIR (04) + 00005A8D. The current application will be terminated.
    Fatal Exception Error in VREDIR with DCOM Program Q167712
15. A fatal exception 0E has occured at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx
    Windows 95 Setup Problems with Plug and Play Program Active Q168444
16. A fatal exception 0E has occurred at 0028: in VxD VMM(06) + .
    “Fatal Exception” Error Suspending and Resuming with MSDLC3 Q171195
17. A fatal exception 0E has occurred at 0028: in VxD VNETBIOS(01) + 5EB.
    0E Exception in VNETBIOS if NetBIOS Commands Are Issued Quickly Q175092
18. Fatal exception 0E at 0028: in VXD VREDIR (04) + 00005A8D
    Fatal Exception Error in VREDIR with DCOM Program Q176446 (Microsoft Windows 95)
19. A fatal exception 0E has occurred at 0028:C029F7A1 in VXD IFSMGR(04) + 0000D4F1 A fatal exception 0E has occurred at 0028:c0274274 in VXD IFSMGR(03) + 000CF7C A fatal exception 0E has occurred at 028:C0282dB0 in VxD IFSMGR(03) + 0000 CF7C

    Fatal Exception Error When Opening or Closing Control Panel Q175211 (HP Scanner software)

20. A fatal exception 0E has occurred at 0137:BFF9A3C0 A fatal exception 0E has occurred at 0137:BFF9A07C

    “Fatal Exception 0E” Error Message Attempting to Open Folder Q176446 (Microsoft Internet Explorer for Win95)

21. A fatal exception 0E has occurred at 0028:C0003C72 in VXD VMM(01) + 00002C72
    “Fatal Exception 0E” Error Message When Running McAfee VirusScan Q177672 (Video = Tseng Labs ET6000 chip set)
22. A fatal exception 0E has occurred in VxD Dsound(03)
    Dilbert Err Msg: Fatal Exception 0E in VxD Dsound(03) Q178616 (Norton AV + Auto-Protect enabled)
23. A Fatal Exception 0E has occurred at 0137:. The current application will be terminated.
    “Fatal Exception 0E” Error Message When You Start Windows 95 Q179347
24. A Fatal Exception 0E has occurred at 0028:C0231810 in VXD VMM(0D) + 00001810.
    Fatal Exception Error Accessing Windows NT Share From Windows 95 Q181866
25. “Fatal Exception 0E” Error Message When Ejecting Laptop Q182856
26. Err Msg: A Fatal Exception 0E Has Occurred at 0028:C02A0201 in VXD IOS(04)+00001FC9 Q187214 (Corel CD Creator 2)
27. Novell Client32 Does Not Work After Upgrading to Windows 98 Q188168 (Novell Client32)
28. Setup Hangs in Plug and Play Detection Upgrading Over Client32 Q189185 (Novell intraNetWare Client)
29. A Fatal Exception 0E has occurred at 0028:C001AEEB Q189329 (Compaq FX-Series Monitors)
30. Err Msg: A Fatal Exception 0E Has Occurred at 0028:XXXXXXXX in VXD SYMEvent(02)+XXXXXXXX Q189655 (Norton AntiVirus or other Symantec program)
31. Fatal Exception 0E at 0028:c028bac6 in VXD Vwin32 05 +000281a Q190915 (Desktop Management Interface (DMI) Start utility)
32. A fatal exception 0E has occurred at 0028: in Vxd Vmwaudio (01) MMSYSTEM257 Invalid MCI device ID. Use the ID returned when opening the MCI device. MMSYSTEM296 The file cannot be played on the specified MCI device. The file may be corrupt, or not in the correct format.

    Problems Using Media Player to Play .avi Files Q191195 (IBM Aptiva 2168-A92 or Acer computer with earlier model IBM Mwave sound card drivers)

33. DSS80: Fatal Exception 0E When Forcing Standby Mode Q191724 (Microsoft Digital Sound System 80)
34. An exception 0E has occurred at 0028:C1029F6C in VxD WSIPX(01) +00000DBC. This was called from 0028:C0043174 in VxD NDIS(01) +00000D7C A fatal exception has occurred at 0028:C10297D1 in VxD WSIPX(01)+00000621

    Fatal Exception Errors in Wsipx.vxd Q192445

35. An exception 0E has occurred @ 0028:C0035A67 in vxd ifsmgr (01)
    Computer Hangs After Upgrade to Windows 98 with EtherFast Card Q192844 (Linksys EtherFast 10/100 network adapter)
36. A fatal exception 0E has occurred at 0028:FF027A60 in VXD HIDCLASS(01)+00000F40 Fatal exception in Windows. You must restart your computer

    Fatal Exception When You Connect SideWinder Precision Pro Q192901

37. A Fatal Exception 0E has occurred at 0028:xxxxx in VXD IOS(04) Q192925 (Sb16.vxd file is located in the Windows\System\Iosubsys folder)
38. 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.
    Fatal Exception in CDVSD Starting Windows 98 Q197004 (SCSI DVD drive)
39. A Fatal Exception 0E has occurred at 015F:BFF9DBA7
    General Protection Fault or Invalid Page Fault During Setup Q209321 (problem in the Dblbuff.sys file)
40. A Fatal Exception 0E has occurred at
    Removing DIGI Datafire Components Cause Fatal Exception Error Q227159 (DataFire)
41. Fatal Exception 0E has occurred at 0028:C027F417 in VxD IFSMGR(04) + 00006AEF
    Fatal Exception 0E When Creating Sub-Folder on an HPFS Volume Q235711
42. Error Message: Fatal Exception 0E in VxD IOS (04) Q243037 (Iomega Tools and Iomega Backup software)
43. A Fatal Exception 0E has occurred at 0028:C0026416 in VXD IFSMGR (01) + 00003672
    “Fatal Exception 0E” Error in IFSMGR When Starting Windows 95 Q248886 (win95 Network errors)
44. Fatal Exception OE Has Occurred in VXD mrtRate (01) When Printing Q252414 (Conflict between your printer driver and Quicken)
45. Error Message: Fatal Exception 0E has occurred at 0028:C00082CD in VxD VMM(01) +000072CD Q253241 (incompatible or early version of a Matrox video driver)
46. A fatal exception 0E has occurred in vxd ndis(01)

    “A Fatal Exception…” Error Message When You Undock Your Laptop Q255121

47. Windows Media Player May Cause Fatal Exception 0E When Using Suspend Mode in Windows 98 Second Edition Q257845
48. Fatal Exception 00 has occurred in module WSIPX.VXD Q260284 (Epson Stylus Photo 870 printer)
49. A Fatal Exception 0E has occurred at Q198811 (Okidata OL-600e)
50. VServer(01) + 00004d75 – Error: 0E: 0028:XXXXXX Q272991 (Windows Me Networking)
51. A fatal exception 0E has occurred at 0028:???????? in VXD VREDIR(??) + ????????. The current application will be terminated.

    An error has occurred. To continue: Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart your computer. If you do this, you will lose any unsaved information in all open applications. File Name: VREDIR(06) + 00006C54 Error: 0E : 0028:C02D2770

    Exception 0E in Vredir.vxd on Remote DCOM Server Q271754 (drive mapping)

52. A fatal exception 0E has occurred at (address) in VXD (FSD) + (address). The current application will be terminated.

    Note: The VXD in question is a File System Driver (FSD) from the list below:

    • CDFS (the path references a CD-ROM drive letter)
    • NWREDIR (the path references a network drive mapped by the Microsoft Client for NetWare Networks)
    • UDF (the path references a DVD-ROM drive)
    • VDEF (the path references an unformatted disk drive)
    • VFAT (the path references a floppy disk drive, a hard disk, or an FTL-formatted Linear Flash PCMCIA card (Flash File System)
    • VREDIR (the path references a network drive mapped by the Client for Microsoft Networks)
    • 0028:DEDEDEDE (the path references a network drive mapped by the Novell NetWare Client for Windows 95/98 version 3.1)
    • Unknown (the path references drives managed by third-party, or custom file system drivers and network redirectors)
53. Fatal Exception 0E with Multiple MS-DOS Device Names in Path Q256015
54. A fatal exception 0E has occurred at (address) in VXD WDMAUD(06) + (address) A fatal exception 0E has occurred at 0028:FF02D808 A fatal exception 0E has occurred at 0028:FF027240 in VXD USBD(01) + 00000440

    Windows Driver Model Audio Update for Windows 98 Second Edition Q242937 (Audio, USB)

55. IFSMGR(04) + 000076A1 ERROR: 0E:0028 : C02AF8E1
    X:Drive v2.0 Install Prior to WinMe Upgrade Produces ErrMsg Q266268 (X:Drive version 2.0 installed prior to upgrading to Windows Me)
56. NDISFILT(01) + 00000650 Error: 0E : 0028:C14796F0
    Problem Installing Windows Me with Norton Internet Security 2000 Q268240
57. Error Message: A Fatal Exception 0E Has Occurred in VxD SCSI1HLP Q250005 (Hewlett Packard 8100i SureStor CD-Writer with the Easy CD Creator, the Easy CD Audio/Copier, or the Direct CD program)
58. An exception 0E has occurred at 0028:C0021E77 in VxD IOS(01) + 00001197. This was called from 0028:C00219AF in VxD IOS(01) + 00000CCF
    Fatal Exception in IOS.VXD When Formatting Disk in LS-120 Drive Q214522
59. A Fatal Exception 0E has occurred at 0028:XXXXXXXX in VXD VSERVER(01) + XXXXXXXX.
    Fatal Exception Error When Adding File and Print Sharing Q244229
60. Fatal exception 0E at 0028:C00BC6B0 in VXD VINESIFS(01) + 000342C
    Error Message When Viewing Banyan VINES Network Properties Q206506
61. Windows 98 Shutdown Generates “Fatal OE” Error Messages Q200692 (Compaq)
62. Fatal exception 0E has occurred at 0028:C02B9568 in VXD IFSMGR(04) + 00012AEC Q273918 (running the Sysinternal Filemon.exe program during Win Me Setup.)
63. A fatal exception 0E has occurred at 0028:???????? in VXD VWIN32(??) + ????????. The current application will be terminated.
    Problems Using Video For Windows Program with a USB Camera Q278033
64. A fatal exception 0E has occurred at : in VxD SCSI1HLP
    Fatal Exception 0E in Scsi1hlp.vxd After Upgrading to Windows Me Q281252 (Compaq computer + DVD drive)

AMD Processor Related Issues: There have been a number of reports on faulty L1 cache problems (the cache on the chip) with AMD processors. Restart your computer into its BIOS setup (see your motherboard or computer system handbook for instructions), and disable the Level 1 cache. If this resolves your problem, you may want to consider buying a new processor.

Another brief list of things you can try that you might find helpful:

1. Make certain that your motherboard has the most current BIOS available.
2. Make certain that you have installed the latest drivers for your motherboard.
3. Make certain that you have installed the latest drivers for your video card.
4. Turn off the external cache in BIOS as a test.
5. Replace RAM memory modules as necessary.
6. Reinstall the operating system, and make certain that you do a clean install, by formatting the drive or partition before the installation.

The most common cause for these types of error messages is faulty physical memory (RAM) in the computer. You can have faulty RAM in your computer, without it affecting you all of the time.

For a more extensive explanation, see Microsoft Knowledge Base Article Q138788 – Bad RAM Causes Fatal Exception Errors Running Windows 95/98.

Notice: Windows® 95, Windows® 98, Windows® NT, Windows® 2000 and Microsoft® Office are registered trademarks or trademarks of the Microsoft Corporation.

All other trademarks are the property of their respective owners.