Microsoft Windows uses programs and exceptions, which allow Windows or other programs to communicate in layers and report errors or exceptions. If an exception program is given invalid or unknown, you will encounter a fatal exception. Fatal exceptions are also referred to as FE 0E, or incorrectly named OE Fatal.
When you encounter a fatal exception, the error will be in the following format.
A fatal error <YZ> occurred at xxxx: xxxxxxxx
In the example above, YZ represents the actual processor exception, and this can range from 00 to 0F.
After the wizard exception is the enhanced help pointer to the 32-bit code and code section, it is where the error exception occurred.
Search for the error
It is often the easiest and fastest way to determine the cause of a killer exception is to look for the error. However, it may be difficult for some users to know exactly what you are looking for because of the deadly exception messages encrypted. Here are some tips on how to find these errors.
As mentioned above, the fatal exception contains a two-letter code. For example, if “0E” exists, use this as part of your search.
Then, the error message must contain a pointer (for example, “0028: c001e36”). Although this may be present in a search, it is usually unique to your computer. If you do not find any search results, exclude that from your search.
Finally, many unusual error messages also contain a file that generated the error, which is always a VXD file. If the fatal exception contains a reference to a .VXD file, include it as part of your search. The VXD file can also be listed as “VXD VWIN32”, which is vwin32.vxd.
If the search for the exceptional error does not produce results or helps solve your problem, proceed to the following sections.
Revert Windows back to an earlier copy
If this has recently occurred, and you are running Windows XP or a later version, Windows reverts to an earlier version.
Update software or check for software patches
If you are experiencing invalid page faults in only one program, verify that the software is compatible with the operating system on your computer. Also check with your manufacturer or software vendor to see if there are any patches or updates available to the software that may help resolve your issue.
It is also important that you have the latest Windows updates.
If critical exceptions occur when you use a device (for example, when printing), the drivers for this device are conflicting with another device, are corrupted, or have other errors.
Video drivers are also known to cause fatal exception error messages. Since your video card is being used all the time, it is difficult to know for certain whether the cause of the error. We therefore recommend that you always use 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 list of hardware companies.
Recently installed software or hardware
If you have recently installed a new program or device, uninstall or reinstall this software or device to verify that it is not causing your problem. Using a 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 list of hardware companies.
Remove all TSRs
Disable any TSRs or programs that run in the background because fatal exception errors can be caused by conflicts between two or more open and run programs.
Delete all program temporary files
Delete all temporary files that may still exist on the hard drive of programs that are currently running or earlier.
If you raise the operating frequency of any component in your computer, set the computer to factory settings to verify that the upgraded component does not cause the problem.
Verify your computer has more than 200 MB available
If your computer is running low on hard drive space, the Windows swap file will not be able to increase its size if needed, which can cause errors.
Run ScanDisk and Defrag
Run ScanDisk and run Defrag on the hard drive, because it may be possible that your hard drive has a problem causing damage to the swap file or data files or is invalid.
Heat related issue
Check that all the fans in your computer are working properly. If not all fans work or you do not have enough fans and your computer is too hot, there may be multiple problems, including fatal exceptions.
Is there a way to find out if my CPU temperature is running?
Disable External Cache in CMOS
If the option is available, enter the CMOS setting for your computer and disable the external cache. If this solves your problem, you may be experiencing a heat problem.
CPU Core Voltage
If available, verify your CMOS setup or via the traffic link from the CPU core voltage setting to the manufacturer’s specifications. Consult your motherboard documentation, which can be found on the motherboard manufacturer’s website.
Bad Memory, invalid bits or physically bad memory
Bad computer memory is also a common cause of fatal exception errors. If you recently added memory to your computer, it is recommended that you remove it first to verify that you are not experiencing conflicts with newly installed memory.
If no recent memory has been added to your computer and you have tried all of the above recommendations, test your computer’s memory for errors.
Below is a list of the most experienced processor exceptions ranging from 00 to 0F.
00 = Divide Fault
This occurs if the division is attempted at zero or if the result of the operation is not appropriate for the destination parameter.
02 = NMI interrupt
Interrupt 2 is reserved for non-hideable state of interrupt. No trap exceptions during interrupt 2.
04 = Overflow trap
This occurs after you perform INTRO instructions and set the bit to 1.
05 = Bounds Check fault
The array index is out of range
06 = Invalid Opcode fault
Because of one of the conditions below.
The wizard tries to decode the bit style that does not comply with any legal instructions for the computer.
The wizard tries to execute an instruction that contains invalid transactions.
The wizard tries to execute a protected mode instruction while running in virtual 8086 mode.
The wizard attempts to execute a LOCK prefix with instructions that can not be locked.
07 = Copressor not available fault
This error can occur if a math helper handler does not exist. This error can also occur when you use the math coprocessor and perform a task key.
08 = Double Fault
This error occurs when an exception is processed by triggering a second exception.
09(OD) = Copressor Segment Overrun
Floating point transactions outside the sector.
10(0Ah/0A) = Invalid Task State Segment Fault
Multiple possible causes, where the task status section contains multiple descriptors.
11(0Bh) = Not Present Fault
The non-existing interrupt allows the operating system to execute default memory through the defragmentation mechanism. Error 0B occurs when this part is not available.
12(0Ch) = Stack Fault
This occurs when Help indicates memory that exceeds the maximum for the stack sector.
13(Odh) = General Protection Fault
Resulting from any condition not covered by any of the other processor exceptions. The exception indicates that this program is corrupted in memory, resulting in immediate termination of the program.
How to Repair a General Protection Fault.
14(Oeh) = Page Fault
This occurs when the migration protection rule is violated (when recovery fails, the data that is retrieved is invalid or the code that issued the error passes the protection rule for the processor).
16(10h) = Coprocessor error fault
This occurs when a non-masked floating-point exception points to earlier Help.
17(11h) = Alignment Check Fault
It is used only on 80486 computers. When you try to execute code when the 3-ring franchise accesses a transactional word that is not divisible by four or real or temporary, it is used to execute an address that is not divisible by eight.
For More : PC Troubleshooting