 Talk about a scary sight. No one likes to see error messages on their personal computer, but some Windows messages are downright alarming:
"A fatal exception 0E has occurred at 0028: xxxxxxxx in VXD IFSMGR(04) + 0000D4F1. The current application will be terminated."
FEEs (fatal exception errors) don't mean that anything has died—not your computer and unfortunately not even that annoying paper clip in Microsoft Office. They do mean that Windows 9x/Me/XP has encountered an error so severe that the application or the OS can't continue to run. An error message like the one above can show up in its own window or in a full-screen announcement often called a Blue Screen of Death (for more on the dreaded BSOD, see "Big, Bad &Blue" on page 7.
Usually, you can bring the computer back to life with a reboot. Unfortunately, the problem that caused the error could remain unsolved. Sleuthing out a solution can be tricky, so it pays to learn about FEEs and why they occur. Read on for a deeper understanding of FEEs and for tips to help you troubleshoot your system.
 Post-Mortem
Microsoft says that FEEs happen most often when you're launching an application or starting or shutting down Windows. Several things can cause them, the company says, such as:
"Access to an illegal instruction has been encountered." The application has an error in its programming or is trying to do something that the OS or processor can't logically let it do.
"Invalid data or code has been accessed." Some data or part of the application may be corrupted or written incorrectly.
"The privilege level of an operation is invalid." The application is trying to do something without permission.
Most often, buggy software is to blame for these problems. Applications often have programming mistakes that ask the computer to do something it can't or shouldn't, which the OS will report as an FEE. Occasionally, applications that work fine by themselves may conflict with each other to cause trouble like this. Viruses and worms can also muck things up.
Some hardware problems can also spawn FEEs. Your computer's RAM modules store the OS, applications, and data the PC is currently using as electric charges within solid-state memory chips. These memory chips need constant electronic refreshing, as they can't retain data for long without power. If the RAM isn't of the highest quality, it doesn't take much to disrupt the delicate balancing act of storing 150MB or more data in a typical computing session. Heat buildup can also affect RAM's ability to properly store data, which is why a computer without good ventilation will typically have more errors than a cooler-running PC.
Microsoft's Knowledge Base has grown into a highly useful resource. This particular article (search for 150314) discusses all the fatal exception errors common to Windows 9x/Me. |
Because Windows uses some hard drive space as extra room for the RAM, calling it virtual memory, any problems on your drive can crop up as FEEs. Hard drives tend to be susceptible to excessive heat, just like RAM modules. They can also be physically damaged if they're dropped or even set down roughly.
The same goes for your PC's motherboard, or main circuit board. If any memory modules or device cables aren't completely connected, you'll see at least some errors. Dirty electrical contacts, kinked cables with broken wires inside, faulty capacitors, and hairline cracks in the motherboard are some of the most elusive sources of maddeningly intermittent errors.
All of these causes mean that there can be a wide variety of FEEs. Windows offers a helping hand by breaking these down into types. Let's have a closer look at the Win9x/Me error message above.
"A fatal exception 0E has occurred at 0028:xxxxxxxx in VXD IFSMGR(04) + 0000D4F1."
The 0D is a hexidecimal number code that tells you the type of FEE you're dealing with. These codes range from 00 (0) to 09 (9) and from 0A (10) to 11 (17). Microsoft offers a list of technical descriptions of each kind of FEE (go to support.microsoft.com and search for article 150314). You can also search for specific types of FEEs in WinXP, such as general protection faults, in Microsoft's Knowledge Base. We've listed the main errors below in the Customary FEEs section of this article.
"VXD IFSMGR" names the file involved in the error, with the file extension switched around to the front. In other words, it's Ifsmgr.VXD.
The parts of the error message with numbers, such as "0028.xxxxxxxx," designate things such as the part of the program's code (the list of instructions that makes up the application) that triggered the error. These numbers are probably only of interest to the software developer.
WinXP tells you the type of error in a more plain-English way. Here's an example from Microsoft. This error happens when someone tries to run AOL 4.0 on WinXP:
"WAOL caused a General Protection Fault in module SUPERSUB.DLL at 0001:325B"
Customary FEEs
Some FEEs are much more common than the others, so we'll hit the highlights here.
A GPF (general protection fault; [type 0D]) is kind of the catch-all category among FEEs, so you'll probably see it the most. This also makes its root cause harder to pin down. However, Microsoft says that GPFs often stem from a memory problem.
Besides buggy applications, hardware device drivers are often to blame for fatal exception errors. Video card drivers top the rogues' gallery, so if you encounter FEEs, you may need to spend some time browsing the FAQ section on the Web site of the manufacturer that produced your card. |
Data corruption in RAM should be your chief suspect here. That could mean faulty RAM modules, memory sticks not seated properly, and/or too much heat.
Microsoft also says that GPF errors can also happen if the computer's video adapter has a faulty or corrupted driver (software that lets an OS use a hardware device, such as a printer or sound card). Some software that expects certain video adapter driver settings, such as Hardware Acceleration set to Full, can cause a GPF if the drivers are set otherwise. Old multimedia applications can also be to blame, as well as missing system files, the company says.
A page fault (0E) happens when the OS can't find the data it's expecting to discover in virtual memory on the hard drive. A page refers to the section of RAM or virtual memory storing a piece of data. A page fault can also occur if the OS tries to access data in the wrong way or if a VXD (virtual device driver) file is located in the wrong folder on the hard drive.
A stack fault (0C) occurs when an application tries to access data that it thinks is stored outside its assigned stacks or areas of memory allocated to it.
Resurrection
Click the Details button in the error window if one is offered. Jot down the first line or two of the error message so you can look it up later. You don't have to include all the "Press any key to continue" parts, but you should write down the type of error and filename, such as:
"A fatal exception 0E has occurred at 0028: xxxxxxxx in VXD IFSMGR(03) + 000CF7C"
Sometimes you can close an error window and try to continue your computing session. If you can, run an antivirus scan. Some nasty bugs can get a better toehold on your system during the boot-up period before antivirus and anti-spyware software starts to run, so it's a good idea to first try to root out any possible nasties before you shut off your PC.
More often after an FEE, you'll have to reboot. This is especially true if your error message came in the form of a blue screen. To do this, press CTRL-ALT-DEL, press your PC's reset button, or shut the computer off and turn it back on again after a few moments.
If Windows suggests that you start it in Safe Mode, do so for now. Safe Mode starts the OS with only essential drivers and processes. This may let you more easily troubleshoot the problem that led to the FEE, especially if a third-party app or driver is to blame.
Windows will probably offer to run ScanDisk to check for errors resulting from the reboot, as Windows can only properly end all its processes when you shut down the normal way (click Start, Shut Down, and OK or Shut Down). Let the disk scan run a complete check of your drive.
If you didn't see any FEEs before you installed a new program, there's a strong likelihood that the new application is at least partly to blame. Uninstall it and reinstall it. Also, check its manufacturer's Web site for a list of FAQs (frequently asked questions), one of which may describe the problem you're having. If so, try the remedy the FAQ suggests. For example, if the application is known to conflict with another one, you may need to uninstall one of them or download a newer version.
The software vendor site's Tech Support or Downloads sections may offer updates or patches you can download and install. Even if an update's description doesn't specifically mention your problem, it may still fix a bug in the software that indirectly affects your situation. Likewise, if you suspect your video card or other hardware, look for a new driver or FAQs at the manufacturer's site.
If your FEE seems to have come out of the blue, try looking it up in Microsoft's Knowledge Base for troubleshooting help. Try keywords such as the type of error and the file name, such as "fatal exception 0E IFSMGR," rather than the strings of numbers in the message.
On the hardware side, make sure that your computer's fans are all working and that ribbon cables aren't blocking the airflow through the case. With your computer off, remove and reinstall your RAM modules to make sure they're seated properly. RAM from a quality manufacturer, such as Corsair, Micron/Crucial, or Kingston, is generally more trouble-free than cheaper brands.
Finally, check your hard drive for errors using ScanDisk or CheckDisk and defragment it using Disk Defragmenter. If your drive has very little free space, uninstall apps or delete data you don't need or upgrade to a bigger drive.
Fatal exception errors can be tricky to diagnose, but now you know that you don't have to let them kill your computing fun. 
by Marty Sems
|
Email This
Print This
Talk about a scary sight. No one likes to see error messages on their personal computer, but some Windows messages are downright alarming: 
