Fatal Exception 0E Errors
A HelpWithWindows TechFile
The Fatal Exception errors related to 0E (that's zero E) are hard to track down. We won't pretend to have all the answers for you here, but we'll attempt to list some things that have fixed this problem for a number of users.
First, what are Fatal Exception Errors? There's a good article in the Microsoft Knowledge Base, describing these errors. See MSKB article 150314.
Here is a list of Microsoft Knowledge Base Articles dealing with these types of errors:
- 16-Bit DMA May Cause Static or System Hang 127022
- Fatal Exception Errors and Random Characters Using ATI Mach 32 139771
-
A fatal exception 0E has occurred at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx
Fatal Exception in VMM(06) Caused by Damaged Registry 145836 - Err Msg: An Exception 0E Has Occurred in Rpcss.exe... 148804
-
An exception 0E has occurred at 00XX:XXXXXXXX in VxD VNETBIOS
Fatal Exception 0E in VNETBIOS Using NetWare Login Script 149606 -
Fatal exception 0E at 0028:<xxxxxxxx> in VxD IOS(01)+<xxxxxxxx>
Fatal Exception 0E in Ios.vxd with SCSI Printer 149563 - Error Message: "Exception 0E in VPOWERD" During First Boot 153395
-
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 158713 - Windows Sockets Programs Using WSIPX May Not Work 159254
-
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 159354 - "Fatal Exception 0E" May Occur During Critical Suspend 162211 (Win95 power management)
- 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.
Fatal Exception 0E in WSIPX Using Windows Sockets Program 163329 - "Exception 0E" Using MSNDS Over Dial-Up Connection 163673 (Dial-Up Networking).
-
Fatal exception 0E at 0028:<address> in VXD VREDIR (04) + 00005A8D. The current application will be terminated.
Fatal Exception Error in VREDIR with DCOM Program 167712 -
A fatal exception 0E has occured at 0028:xxxxxxxx in VxD VMM(06) + xxxxxxxx
Windows 95 Setup Problems with Plug and Play Program Active 168444 -
A fatal exception 0E has occurred at 0028:<xxxxxxxx> in VxD VMM(06) + <xxxxxxxx>.
"Fatal Exception" Error Suspending and Resuming with MSDLC3 171195 -
A fatal exception 0E has occurred at 0028:<xxxxxxxx> in VxD VNETBIOS(01) + 5EB.
0E Exception in VNETBIOS if NetBIOS Commands Are Issued Quickly 175092 -
Fatal exception 0E at 0028:<address> in VXD VREDIR (04) + 00005A8D
Fatal Exception Error in VREDIR with DCOM Program 176446 (Microsoft Windows 95) -
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 175211 (Scanner software) -
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 176446 (Microsoft Internet Explorer for Win95) -
A fatal exception 0E has occurred at 0028:C0003C72 in VXD VMM(01) + 00002C72
"Fatal Exception 0E" Error Message When Running McAfee VirusScan 177672 (Video = Tseng Labs ET6000 chip set) -
A fatal exception 0E has occurred in VxD Dsound(03)
Dilbert Err Msg: Fatal Exception 0E in VxD Dsound(03) 178616 (Norton AV + Auto-Protect enabled) -
A Fatal Exception 0E has occurred at 0137:<address>. The current application will be terminated.
"Fatal Exception 0E" Error Message When You Start Windows 95 179347 -
A Fatal Exception 0E has occurred at 0028:C0231810 in VXD VMM(0D) + 00001810.
Fatal Exception Error Accessing Windows NT Share From Windows 95 181866 - "Fatal Exception 0E" Error Message When Ejecting Laptop 182856
- Err Msg: A Fatal Exception 0E Has Occurred at 0028:C02A0201 in VXD IOS(04)+00001FC9 187214 (Corel CD Creator 2)
- Novell Client32 Does Not Work After Upgrading to Windows 98 188168 (Novell Client32)
- Setup Hangs in Plug and Play Detection Upgrading Over Client32 189185 (Novell intraNetWare Client)
- A Fatal Exception 0E has occurred at 0028:C001AEEB 189329 (Compaq FX-Series Monitors)
- Err Msg: A Fatal Exception 0E Has Occurred at 0028:XXXXXXXX in VXD SYMEvent(02)+XXXXXXXX 189655 (Norton AntiVirus or other Symantec program)
- Fatal Exception 0E at 0028:c028bac6 in VXD Vwin32 05 +000281a 190915 (Desktop Management Interface (DMI) Start utility)
-
A fatal exception 0E has occurred at 0028:<XXXXXXXX> 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 191195 (IBM Aptiva 2168-A92 or Acer computer with earlier model IBM Mwave sound card drivers) - DSS80: Fatal Exception 0E When Forcing Standby Mode 191724 (Microsoft Digital Sound System 80)
-
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 192445 -
An exception 0E has occurred @ 0028:C0035A67 in vxd ifsmgr (01)
Computer Hangs After Upgrade to Windows 98 with EtherFast Card 192844 (Linksys EtherFast 10/100 network adapter) -
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 192901 - A Fatal Exception 0E has occurred at 0028:xxxxx in VXD IOS(04) 192925 (Sb16.vxd file is located in the Windows\System\Iosubsys folder)
-
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 197004 (SCSI DVD drive) - A Fatal Exception 0E has occurred at <address> 198811 (Okidata OL-600e)
-
A Fatal Exception 0E has occurred at 015F:BFF9DBA7
General Protection Fault or Invalid Page Fault During Setup 209321 (problem in the Dblbuff.sys file) -
A Fatal Exception 0E has occurred at <address>
Removing DIGI Datafire Components Cause Fatal Exception Error 227159 (DataFire) -
Fatal Exception 0E has occurred at 0028:C027F417 in VxD IFSMGR(04) + 00006AEF
Fatal Exception 0E When Creating Sub-Folder on an HPFS Volume 235711 - Error Message: Fatal Exception 0E in VxD IOS (04) 243037 (Iomega Tools and Iomega Backup software)
-
A Fatal Exception 0E has occurred at 0028:C0026416 in VXD IFSMGR (01) + 00003672
"Fatal Exception 0E" Error in IFSMGR When Starting Windows 95 248886 (win95 Network errors) - Error Message: A Fatal Exception 0E Has Occurred in VxD SCSI1HLP 250005 (Hewlett Packard 8100i SureStor CD-Writer / Compaq Presario model 5716 with a "DVD 113R" DVD ROM drive)
- Fatal Exception OE Has Occurred in VXD mrtRate (01) When Printing 252414 (Conflict between your printer driver and Quicken)
- Error Message: Fatal Exception 0E has occurred at 0028:C00082CD in VxD VMM(01) +000072CD 253241 (incompatible or early version of a Matrox video driver)
-
A fatal exception 0E has occurred in vxd ndis(01)
"A Fatal Exception..." Error Message When You Undock Your Laptop 255121 - Windows Media Player May Cause Fatal Exception 0E When Using Suspend Mode in Windows 98 Second Edition 257845
- Fatal Exception 00 has occurred in module WSIPX.VXD 260284 (Epson Stylus Photo 870 printer)
- VServer(01) + 00004d75 - Error: 0E: 0028:XXXXXX 272991 (Windows Me Networking)
-
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 271754 (drive mapping)
-
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)
Fatal Exception 0E with Multiple MS-DOS Device Names in Path 256015
-
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 242937 (Audio, USB) -
IFSMGR(04) + 000076A1 ERROR: 0E:0028 : C02AF8E1
X:Drive v2.0 Install Prior to WinMe Upgrade Produces ErrMsg 266268 (X:Drive version 2.0 installed prior to upgrading to Windows Me) -
NDISFILT(01) + 00000650 Error: 0E : 0028:C14796F0
Problem Installing Windows Me with Norton Internet Security 2000 268240 - Error Message: A Fatal Exception 0E Has Occurred in VxD SCSI1HLP 250005 (Hewlett Packard 8100i SureStor CD-Writer with the Easy CD Creator, the Easy CD Audio/Copier, or the Direct CD program)
-
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 214522 -
A Fatal Exception 0E has occurred at 0028:XXXXXXXX in VXD VSERVER(01) + XXXXXXXX.
Fatal Exception Error When Adding File and Print Sharing 244229 -
Fatal exception 0E at 0028:C00BC6B0 in VXD VINESIFS(01) + 000342C
Error Message When Viewing Banyan VINES Network Properties 206506 - Windows 98 Shutdown Generates "Fatal OE" Error Messages 200692 (Compaq)
- Fatal exception 0E has occurred at 0028:C02B9568 in VXD IFSMGR(04) + 00012AEC 273918 (running the Sysinternal Filemon.exe program during Win Me Setup.)
-
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 278033 -
A fatal exception 0E has occurred at <xxx>:<xxxxxxxx> in VxD SCSI1HLP
Fatal Exception 0E in Scsi1hlp.vxd After Upgrading to Windows Me 281252 (Compaq computer + DVD drive) - Fatal Exception Error Is Displayed in the Vredir.vxd File 261927 (Adaptec DirectCD versions 2.0, 2.0a/s, 2.5a, and 2.5d)
-
Err Msg: Fatal Exception 0e 0028:c004df6c in Vxd Vcache 293299 (bad RAM)
Fatal exception 0e 0028:c004df6c in vxd vcache (O1) + 00000b20 -
Exception 0E in Vredir Error Messages Opening Network Files 293793
Windows 98: An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) + ????????. This was called from 0028:C0034184 in VxD IFSMGR(01) + 00001094.
Windows 98 SE: An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) + ????????. This was called from 0028:C0034A74 in VxD IFSMGR(01) + 00001094.
Windows Me: An exception 0E has occurred at 0028:???????? in VxD VREDIR(01) + ????????. This was called from 0028:C0033AE8 in VxD IFSMGR(01) + 00001098. -
"Fatal Exception OE" Err Msg When Connecting to the Internet 300029 (Quicken 2000 & Compaq USB modem, or certain U.S. Robotics & Lucent products)
Fatal Exception 0E has occurred at 0028:C00283FE in VXD VCOMM(01) +00000106 The current application will be terminated.
Fatal Exception 0E has occurred at 0028:C00283FE in VXD UNIMODEM(01) +00000106 The current application will be terminated.
Fatal Exception 0E has occurred at 0028:C02A7903 in VxD VCOMM(04)+00000E67 -
Err Msg: Fatal Exception OE Has Occurred in Vxd Vserver 302826
Fatal Exception Error 0E has occurred at 0028:<address> in module VxD VServer (01)+00004fd7 -
"Fatal Exception" Err Msg After You Install Age of Empires 303117 (Age of Empires)
Fatal Exception 0E at 015f:<address>
Fatal Exception 06 - Err Msg: Fatal Exception 0E Has Occurred at 0028:c02c1085 in Vxd IOS(04) + 000020f9 306324 (Upgrading Windows 98 > Windows 98 SE with scanner connected through another device on the same LPT port)
If you are running with an AMD 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.
We noticed that this part is being quoted by several sources on the Internet as "News"; just realize that this is old information, going back around 1 year (beginning of 2000). We are no hardware experts, but we have had reports similar to the post by "HumanHunter" (Mar/07/2001 6:09 PM).
AMD & Temperature
We've received information that running the (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!
Here's another short list of things to try:
- Check to see if you have the latest drivers installed for your motherboard.
- Check to see if you have the latest drivers installed for your video card.
- Turn off the external cache in BIOS.
- Replace RAM chips.
- Reinstall the OS. Do a clean install, by formatting the drive/partition.
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.
For a more extensive explanation, see Microsoft Knowledge Base Article 138788.