Exception OE

Hi,
Since there appears to be no specific Microsoft article relating to your fatal exception error then there probably isn't a quick and easy "fix". From Microsoft:
What Are Windows 95/98 Fatal Exception Errors

SUMMARY
When you attempt to shut down your computer, start Windows or an application inside of Windows, you may encounter errors similar to the following:

A fatal exception has occurred at xxxx:xxxxxxxx
Fatal exception errors are codes returned by a program in the following cases:

Access to an illegal instruction has been encountered

Invalid data or code has been accessed

The privilege level of an operation is invalid

When any of these occur, the processor returns an exception to the operating system, which in turn is handled as a Fatal Exception Error. In many cases the exception is non-recoverable and the system must either be restarted or shutdown, depending upon the severity of the error.

In the following example of a Fatal Exception error

A fatal exception has occurred at xxxx:xxxxxxxx

the represents the actual processor exception from 00 to 0F (the h that is listed after the 0E, 0F and so on in the explainations below is frequently omitted from the error message). The xxxx:xxxxxxxx represents the enhanced instruction pointer to the code segment and the 32-bit address is the actual address where the exception occurred.

Windows does not cause these errors, but has the exception handling routine for that particular processor exception, which displays the above message.

14 (0Eh): Page Fault

The Page Fault interrupt allows the operating system to implement virtual memory on a demand-paged basis. An interrupt 14 usually is issued whenever an access to a page directory entry or page table with the present bit set to 0 (Not present) occurs. The operating system makes the page present (usually retrieves the page from virtual memory) and re-issues the faulting instruction, which then can access the segment. A page fault also occurs when a paging protection rule is violated (when the retrieve fails, or data retrieved is invalid, or the code that issued the fault broke the protection rule for the processor). In these cases the operating system takes over for the appropriate action.

Troubleshooting Fatal Exception Errors
Due to the various conditions that can cause a fatal exception error, the first step in resolving it is to narrow the focus. To narrow the focus, try a clean-boot of your computer.

Clean-Boot
Clean-boot troubleshooting refers to methods of reducing problems that may occur because of your computer's environment. Many problems running Windows or programs occur because of conflicting drivers, terminate-and-stay- resident programs (TSRs), and other settings that are loaded when your computer starts. For additional information about how to clean-boot your computer, click the article numbers below to view the article in the Microsoft Knowledge Base:
Troubleshooting Fatal Exception Errors

Before you proceed with the Trouble Shooting process you could run System File Checker to see if there are any corrupted files that could be causing the error. Since the error shows up in your email program, you could reinstall that application. The error is occuring in Ifsmgr.VxD which is a virtual device manager in Microsoft VM so you might consider updating to the latest version of this from:
Microsoft VM
Hope that this gives you some help in solving your problem.
Steve