How to fix a fatal exception error

Updated: 12/20/2017 by Computer Hope

Microsoft Windows and

software use exceptions, which allow Windows or other software to
communicate in layers and communicate errors or exceptions. If a
program is given an exception that is invalid or unknown, you'll
encounter a fatal exception. Fatal exceptions are also commonly
referred to as a Fatal 0E, or improperly as a Fatal OE.
When a fatal exception is encountered, the error will be in the below format.
A fatal exception <YZ> has occurred at xxxx:xxxxxxxx

In the above example, the YZ represents the actual processor exception, this
can range from 00 to 0F. Each of these processor exceptions are explained
under extended information.
After the processor exception is the enhanced instruction pointer to the code
segment and the 32-bit address, which is where the error exception has
occurred.
Search for the error
Often the easiest and fastest method to locate the cause of a fatal exception
is to search for the error. However, for some users, it may be difficult to
know exactly what to search for because of the cryptic fatal exception
messages. Below are tips on how to search for these errors.
1. As mentioned above, the fatal exception has a two character code. For example, if the
"0E" is present, use this as part of your search.
2. Next, the error message should contain a pointer (e.g., "0028:c001e36"). Although
this may be found in a search, it is usually unique to your computer. If you're not
finding any search results, exclude this from your search.
3. Finally, many fatal exception error messages also contain a file that generated the
error, which is almost always a VXD file. If the fatal exception error contains a
reference to a .VXD file, definitely include this as part of your search. The VXD file
may also be listed as "VXD VWIN32", which is "vwin32.vxd".
If searching for the fatal exception error does not return results or help
resolve your issue, continue to the following sections.
Revert Windows back to an earlier copy
If this has just started occurring and you're running Windows XP or
later, restore Windows back to an earlier copy.
Update software or check for software patches
If you are experiencing invalid page faults in only one program, verify that
the software program is compatible with the operating system on the
computer. Also, check with the manufacturer or vendor of the software
program to see if there are any available patches or updates for the program
that may help to resolve your issue.
It is also important that you have all the latest Windows updates.
Hardware drivers
If fatal exceptions happen when using a hardware device (e.g., when you
print), the drivers related to that device are either conflicting with another
device, corrupt, or have other errors.
Video drivers are also notorious for causing fatal exception error messages.
Because your video card is being used all the time, it's difficult to know for
certain if it's the cause of the error. Therefore we always recommend having
the latest video drivers on your computer.
Visit the manufacturer's website and get the latest software and drivers from
them. See the computer drivers page for a listing of hardware companies.
Recently installed software or hardware
If you have recently installed new software or hardware, uninstall or reinstall
that software or hardware to verify it is not causing your issue. With a
hardware device, instead of installing the software or drivers that came with
the device, visit the manufacturer's website and get the latest software or
drivers from them. See the computer drivers page for a listing of hardware
companies.
Remove all TSRs
Disable any TSRs or programs running in the background, since fatal
exception errors can be caused by conflicts between two or more open and
running programs.
Delete all program temporary files
Delete all temporary files that may still be residing on the hard drive from
currently or previously running programs.
Overclocked computer
If you have overclocked any component in the computer, set the computer
to its factory settings to verify that the overclocked component is not
causing the issue.
Verify your computer has more than 200 MB available
If your computer is running low on hard drive space, your Windows swap
file will be unable to increase in size when needed, which can cause errors.
 Determining available hard drive space.

Run ScanDisk and Defrag

Run ScanDisk and run Defrag on the hard drive, as it could be possible your
hard drive may have an issue causing the swap file or data files to become
corrupt or invalid.
Heat related issue
Verify that all fans in your computer are properly working. If not all fans are
working or you do not have enough fans and your computer is overheating,
multiple issues, including fatal exceptions, can occur.
 Is there a way to tell how hot my CPU is running?

Disable External Cache in CMOS

If the option is available, enter your computer's CMOS setup and
disable the external cache. If this resolves your issue, it is likely
that you are encountering a heat related issue.
CPU Core Voltage
If available, verify in your CMOS Setup or by jumper that your CPU core
voltage is set to the factory specification. Consult your motherboard
documentation, which can be found at the website of your motherboard
manufacturer.
Bad Memory, invalid bits or physically bad memory
Bad computer memory is also a common cause for fatal exception errors. If
you have recently added memory to the computer, it is recommended that it
first be removed to verify that you are not experiencing conflicts with the
recently installed memory.
If no memory has been recently added to the computer and you have tried
all the above recommendations, test your computer memory for errors.
Extended Information
Below is a listing of the more commonly experienced processor exceptions
ranging from 00 to 0F.
00 = Divide Fault
Occurs if division by zero is attempted or if the result of the operation does
not fit in the destination operand.
02=NMI interrupt
Interrupt 2 is reserved for the hardware non-maskable interrupt condition.
No exceptions trap through interrupt 2.
04=Overflow trap
Occurs after an INTRO instruction has executed and the OF bit is set to 1.
05=Bounds Check fault
The array Index is out of range
06=Invalid Opcode fault
Caused by one of the below conditions.
1. Processor attempting to decode a bit pattern that does not correspond to any legal
computer instruction.
2. Processor attempts to execute an instruction that contains invalid operands.
3. Processor attempts to execute a protected-mode instruction while running in virtual
8086 mode.
4. Processor attempts to execute a LOCK prefix with an instruction that cannot be
locked.
07=Copressor not available fault
This error can occur if no math coprocessor is present. This error can also
occur when the math coprocessor is used and a task switch is executed.
08=Double Fault
This error occurs when processing an exception triggers a second exception.
09(OD)=Copressor Segment Overrun
Floating point operand is outside the segment.
10(0Ah/0A)=Invalid Task State Segment Fault
Multiple possible causes, as Task State Segment contains multiple
descriptors.
11(0Bh)=Not Present Fault
The not present interrupt allows the operating system to implement virtual
memory through the segmentation mechanism. 0B fault occurs when this
segment is not available.
12(0Ch)=Stack Fault
Occurs when instruction refers to memory beyond the limit of the stack
segment.
13(Odh)=General Protection Fault
Caused by any condition that is not covered by any of the other processor
exceptions. The exception indicates that this program has been corrupted in
memory, resulting in the immediate termination of the program.
 How to fix a general protection fault.

14(Oeh)=Page Fault
Occurs when a paging protection rule is violated (when the retrieve fails,
data retrieved is invalid or the code that issued the fault broke the protection
rule for the processor).
16(10h)=Coprocessor error fault
Occurs when an unmasked floating-point exception has signaled a previous
instruction.
17(11h)=Alignment Check Fault
Only used on 80486 computers. Caused when code executing at ring
privilege 3 attempts to access a word operand that is not divisible by four, or
a long real or temp real whose address is not divisible by eight.