Fatal Exception 0E Errors (HW154) Home Search Article Links

Home
Up
Downloads
Links & FAQ
Suggestions
Manuals
What's New
Submit Solutions
Products

Fatal Exception 0E Errors (HW154) 

KNOWLEDGE BASE LINKS
FATAL EXCEPTION ERRORS
 

Fatal Exception Error messages occur if access to an illegal instruction has been encountered; if invalid data or code is accessed; or if the privilege level of an operation is invalid. The two digits that identify the error are a hexadecimal error code number; thus, for example, “Fatal Exception Error 0E” (Zero-E) is a way of writing “Fatal Exception Error No. 14,” not a reference to Outlook Express. It is technically correct to say that Windows does not, itself, cause these errors, and merely reports them. However, Windows’ memory handling capabilities, interacting with other programs, may be what causes the specific problem. Often, the cause will be a problem with physical RAM; another hardware problem; damaged or missing files; or a damaged Registry. The individual scenario and specific error message references should be consulted to help identify the specific problem.

OVERVIEW. See: What are Windows Fatal Exception Errors. Win95, Win98, Win98 SE, Win ME

bulletBad RAM Causes Fatal Exception Errors Win95, Win98, Win98 SE, Win ME
bulletEXPLORER caused an exception C0010000h in module MSJAVA.DLL Win98, Win98 SE, Win ME
bulletFatal Exception Error Message or USB Devices May Not Work After You Insert PC Card Win98, Win98 SE, WinME (Or, MSGSRV shows as “not responding”)

 
bulletMPREXE caused an exception 03h in module USER32.DLL Win ME
bulletMPREXE caused an exception 03h in module USER32.DLL Win98, Win ME (During Setup, antivirus program is running.)
bulletMSIMN caused an exception C0000006h in module DIRECTDB.DLL Win ME
bulletMSTASK caused an exception 03h in module USER32.DLL Win ME
bulletRUNDLL32 caused an exception 03h in module USER32.DLL Win ME
bulletSCANDSKW caused Fatal exception 03h in module USER32.DLL Win ME
bulletSTATEMGR caused an exception 03h in module USER32.DLL Win ME
bulletUSR32.EXE caused an exception 03h in module USER32.DLL Win98, Win ME (During Setup, antivirus program is running.)
bulletFatal Exception 06 Has Occurred Win98, Win98 SE
bulletFatal Exception 06 at 0028:xxxxxxxx in VXD VMM (06) Win95 (problem in MSDLC32)
bulletFatal exception at 0028:C10297D1 in VxD WSIPX(01) {Q192445} Win95
bulletFatal Exception in CDVSD Starting Windows Win98
bulletFatal Exception in VXD VMM Win95 (damaged Registry)


 

Fatal Exception 0D

Of the many types of Fatal Exception Errors, a Fatal Exception Error 0D is a General Protection Fault. A program has been corrupted in memory. Most often, it is caused by outdated or damaged video drivers, outdated multimedia software, or physically damaged RAM. However, these are not the only causes. Unfortunately, sometimes it can be obscure because any fatal exception condition not covered by any of the other 17 processor exception categories will be called a general protection fault. The specific scenario and specific error message references should be consulted to help identify the specific problem. For updated drivers, check with your hardware manufacturer (usually through their web site), or check here.

OVERVIEW. See: What is an Exception Error 0D?

SEARCH FOR MORE. If you cannot find your Fatal Exception 0D Error Message below, try these links to search the Knowledge Base for others in Win95 Win98 Win ME.

bulletError 0D : 0157 : 00005ED7 {Q307908} Win ME (Quitting Sounds & Multimedia in Control Panel)
bulletException 0D at <memory address> Win95
bulletException 0D at VXD VMM(0H)+00005B01 0028:C0006B01 Win98 SE (BSOD during startup with some AMD chips)
bulletFatal 0D has occurred at 0028:C001539A or 0246:013F47FB Win95, Win98, Win98 SE, Win ME (with McAfee Clinic installed)
bulletProgram Has Caused a Fatal Exception 0D at 00457:000040B1 & Will Be Terminated Win95, Win98 BSOD with Adobe Type Manager & some video drivers.


 

Fatal Exception 0E

This is a Page Fault interrupt. It typically occurs when Windows tries to access virtual memory on a demand-paged basis and the requested page of memory is missing or damaged, or when a paging protection rule is otherwise violated. Many of the Knowledge Base articles for these problems address specific hardware or settings issues.

OVERVIEW. See: What is an Exception Error 0E?

SEARCH FOR MORE. If you cannot find your Fatal Exception 0E Error Message below, try these links to search the Knowledge Base for others in Win95 Win98 Win ME.

bulletMisc. 0E Exception Errors
bulletFatal Exception 0E with Multiple MS-DOS Device Names in Path Win95, Win98, Win98 SE
bulletError 0E: 0028:C000EC99 Win ME
bulletFatal Exception 0E 06 at 0028: xxxxxxxx Win95, Win98, Win98 SE, Win ME (while browsing, after ZoneAlarm uninstall)
bulletFatal Exception 0E at 0157:BFF9A25B Win95 (at startup: RealJukeBox + AOL 6)
bulletEMU10K1
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD Emu10k1 Win95, Win98, Win98 SE, Win ME
bulletIFSMGR.VXD
bulletException 0E at 00XX:XXXXXXXX in VxD IFSMGR {Q153598} Win95, Encarta World Atlas ’96
bulletException 0E at 0028:C0035A67 in VXD IFSMGR Win98
bulletFatal Exception 0E at 0028:c0036671 in VXD IFSMGR(01)... Win98 SE (when using XCOPY)
bulletFatal Exception 0E at 0028:C0026416 in VXD IFSMGR Win95
bulletFatal Exception 0E in VXD IFSMGR Win95, Win98 (When opening or closing Control Panel)
bulletIOS.VXD
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD IOS Win98
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD IOS (01) Win95 (with SCSI printer)
bulletFatal Exception 0E at 0028:C02A0201 in VXD IOS (04) Win95, Win98, Win98 SE, Win ME (with Corel CD Creator 2.0)
bulletNDIS.VXD
bulletException 0E at 0028:0000000C in VXD called from 0028:C001d188 in VXDNDIS... {Q300021} Win98, Win98 SE, Win ME (during Internet connect, with EnterNet 300)
bulletSCSI1HLP.VXD
bulletFatal Exception 0E at xxxx:xxxxxxxx in VxD SCSI1HLP {Q250005} Win ME
bulletSYMEVENT.VXD
bulletFatal Exception 0E at 0028:<xxxxxxxx> in VXD SYMEvent Win95, Win98, Win ME
bulletVCACHE.VXD
bulletFatal Exception 0E 0028:c004df6c in VXD VCACHE(01) Win98, Win98 SE, Win ME (when upgrading to Win ME: damaged RAM)
bulletVMM32.VXD
bulletException 0E at 0028:C00082CD in VXD VMM {Q253241} Win98, Win98 SE, Win ME (with some Matrox video drivers)
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD VMM (06) Win95 (problem in MSDLC32)
bulletVNETBIOS.VXD
bulletFatal Exception 0E in VNETBIOS Win95 (with NetWare login script)
bulletVPOWRD.VXD
bulletFatal Exception 0E in VPOWRD Win95
bulletVREDIR.VXD
bulletFatal Exception 0E at 0028:???????? in VXD VREDIR Win95, Win98, Win98 SE, Win ME
bulletVSERVER.VXD
bulletFatal Exception 0E at 0028:XXXXXXXX in VXD VSERVER Win95, Win98
bulletVWIN32.VXD
bulletFatal Exception 0E at 0028:c028bac6 in VXD VWIN32 Win98
bulletWMAX.EXE
bulletException 0E Access Violation in Module WMAD.EXE at xxxx:xxxxxxxx {Q312931} Win95, Win98, Win98 SE, Win ME (“Yo Mama, Osama” trojan)
bulletWSIPX.VXD
bulletException 0E at 0028:C1029F6C in VxD WSIPX(01)... called from 0028:C0043174 in VxD NDIS(01) {Q192445} Win95

KNOWLEDGE BASE LINKS
FATAL EXCEPTION ERRORS
Last updated March 31, 2002
Click here to refresh this page & its menu bar.


 

Fatal Exception Error messages occur if access to an illegal instruction has been encountered; if invalid data or code is accessed; or if the privilege level of an operation is invalid. The two digits that identify the error are a hexadecimal error code number; thus, for example, “Fatal Exception Error 0E” (Zero-E) is a way of writing “Fatal Exception Error No. 14,” not a reference to Outlook Express. It is technically correct to say that Windows does not, itself, cause these errors, and merely reports them. However, Windows’ memory handling capabilities, interacting with other programs, may be what causes the specific problem. Often, the cause will be a problem with physical RAM; another hardware problem; damaged or missing files; or a damaged Registry. The individual scenario and specific error message references should be consulted to help identify the specific problem.

OVERVIEW. See: What are Windows Fatal Exception Errors. Win95, Win98, Win98 SE, Win ME
bulletBad RAM Causes Fatal Exception Errors Win95, Win98, Win98 SE, Win ME
bulletEXPLORER caused an exception C0010000h in module MSJAVA.DLL Win98, Win98 SE, Win ME
bulletFatal Exception Error Message or USB Devices May Not Work After You Insert PC Card Win98, Win98 SE, WinME (Or, MSGSRV shows as “not responding”)

 
bulletMPREXE caused an exception 03h in module USER32.DLL Win ME
bulletMPREXE caused an exception 03h in module USER32.DLL Win98, Win ME (During Setup, antivirus program is running.)
bulletMSIMN caused an exception C0000006h in module DIRECTDB.DLL Win ME
bulletMSTASK caused an exception 03h in module USER32.DLL Win ME
bulletRUNDLL32 caused an exception 03h in module USER32.DLL Win ME
bulletSCANDSKW caused Fatal exception 03h in module USER32.DLL Win ME
bulletSTATEMGR caused an exception 03h in module USER32.DLL Win ME
bulletUSR32.EXE caused an exception 03h in module USER32.DLL Win98, Win ME (During Setup, antivirus program is running.)
bulletFatal Exception 06 Has Occurred Win98, Win98 SE
bulletFatal Exception 06 at 0028:xxxxxxxx in VXD VMM (06) Win95 (problem in MSDLC32)
bulletFatal exception at 0028:C10297D1 in VxD WSIPX(01) {Q192445} Win95
bulletFatal Exception in CDVSD Starting Windows Win98
bulletFatal Exception in VXD VMM Win95 (damaged Registry)


 

Fatal Exception 0D

Of the many types of Fatal Exception Errors, a Fatal Exception Error 0D is a General Protection Fault. A program has been corrupted in memory. Most often, it is caused by outdated or damaged video drivers, outdated multimedia software, or physically damaged RAM. However, these are not the only causes. Unfortunately, sometimes it can be obscure because any fatal exception condition not covered by any of the other 17 processor exception categories will be called a general protection fault. The specific scenario and specific error message references should be consulted to help identify the specific problem. For updated drivers, check with your hardware manufacturer (usually through their web site), or check here.

OVERVIEW. See: What is an Exception Error 0D?

SEARCH FOR MORE. If you cannot find your Fatal Exception 0D Error Message below, try these links to search the Knowledge Base for others in Win95 Win98 Win ME.
bulletError 0D : 0157 : 00005ED7 {Q307908} Win ME (Quitting Sounds & Multimedia in Control Panel)
bulletException 0D at <memory address> Win95
bulletException 0D at VXD VMM(0H)+00005B01 0028:C0006B01 Win98 SE (BSOD during startup with some AMD chips)
bulletFatal 0D has occurred at 0028:C001539A or 0246:013F47FB Win95, Win98, Win98 SE, Win ME (with McAfee Clinic installed)
bulletProgram Has Caused a Fatal Exception 0D at 00457:000040B1 & Will Be Terminated Win95, Win98 BSOD with Adobe Type Manager & some video drivers.


 

Fatal Exception 0E

This is a Page Fault interrupt. It typically occurs when Windows tries to access virtual memory on a demand-paged basis and the requested page of memory is missing or damaged, or when a paging protection rule is otherwise violated. Many of the Knowledge Base articles for these problems address specific hardware or settings issues.

OVERVIEW. See: What is an Exception Error 0E?

SEARCH FOR MORE. If you cannot find your Fatal Exception 0E Error Message below, try these links to search the Knowledge Base for others in Win95 Win98 Win ME.
bulletMisc. 0E Exception Errors
bulletFatal Exception 0E with Multiple MS-DOS Device Names in Path Win95, Win98, Win98 SE
bulletError 0E: 0028:C000EC99 Win ME
bulletFatal Exception 0E 06 at 0028: xxxxxxxx Win95, Win98, Win98 SE, Win ME (while browsing, after ZoneAlarm uninstall)
bulletFatal Exception 0E at 0157:BFF9A25B Win95 (at startup: RealJukeBox + AOL 6)
bulletEMU10K1
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD Emu10k1 Win95, Win98, Win98 SE, Win ME
bulletIFSMGR.VXD
bulletException 0E at 00XX:XXXXXXXX in VxD IFSMGR {Q153598} Win95, Encarta World Atlas ’96
bulletException 0E at 0028:C0035A67 in VXD IFSMGR Win98
bulletFatal Exception 0E at 0028:c0036671 in VXD IFSMGR(01)... Win98 SE (when using XCOPY)
bulletFatal Exception 0E at 0028:C0026416 in VXD IFSMGR Win95
bulletFatal Exception 0E in VXD IFSMGR Win95, Win98 (When opening or closing Control Panel)
bulletIOS.VXD
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD IOS Win98
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD IOS (01) Win95 (with SCSI printer)
bulletFatal Exception 0E at 0028:C02A0201 in VXD IOS (04) Win95, Win98, Win98 SE, Win ME (with Corel CD Creator 2.0)
bulletNDIS.VXD
bulletException 0E at 0028:0000000C in VXD called from 0028:C001d188 in VXDNDIS... {Q300021} Win98, Win98 SE, Win ME (during Internet connect, with EnterNet 300)
bulletSCSI1HLP.VXD
bulletFatal Exception 0E at xxxx:xxxxxxxx in VxD SCSI1HLP {Q250005} Win ME
bulletSYMEVENT.VXD
bulletFatal Exception 0E at 0028:<xxxxxxxx> in VXD SYMEvent Win95, Win98, Win ME
bulletVCACHE.VXD
bulletFatal Exception 0E 0028:c004df6c in VXD VCACHE(01) Win98, Win98 SE, Win ME (when upgrading to Win ME: damaged RAM)
bulletVMM32.VXD
bulletException 0E at 0028:C00082CD in VXD VMM {Q253241} Win98, Win98 SE, Win ME (with some Matrox video drivers)
bulletFatal Exception 0E at 0028:xxxxxxxx in VXD VMM (06) Win95 (problem in MSDLC32)
bulletVNETBIOS.VXD
bulletFatal Exception 0E in VNETBIOS Win95 (with NetWare login script)
bulletVPOWRD.VXD
bulletFatal Exception 0E in VPOWRD Win95
bulletVREDIR.VXD
bulletFatal Exception 0E at 0028:???????? in VXD VREDIR Win95, Win98, Win98 SE, Win ME
bulletVSERVER.VXD
bulletFatal Exception 0E at 0028:XXXXXXXX in VXD VSERVER Win95, Win98
bulletVWIN32.VXD
bulletFatal Exception 0E at 0028:c028bac6 in VXD VWIN32 Win98
bulletWMAX.EXE
bulletException 0E Access Violation in Module WMAD.EXE at xxxx:xxxxxxxx {Q312931} Win95, Win98, Win98 SE, Win ME (“Yo Mama, Osama” trojan)
bulletWSIPX.VXD
bulletException 0E at 0028:C1029F6C in VxD WSIPX(01)... called from 0028:C0043174 in VxD NDIS(01) {Q192445} Win95

 

 

BY: MRA - 04/2002

    

Questions or problems regarding this web site should be directed to Michael A.
Copyright © 2009 Compulink Business Systems. All rights reserved.
Last modified: 01/07/10.