|
 |
|
|
Adare Enterprises Inc.
151 Lincoln Hts. Road,
Ottawa,Ontario
K2B 8A5
Tel: 613-596-1312
|
|
|
| WINDOWS ERRORS |
FATAL EXCEPTION APPEARING IN:
Windows 95
Windows 98
Windows 98 second edition
Windows Millennium Edition
**Please note**
This information is here only to help you in discovering possible reasons for the "FATAL EXCEPTION ERROR" you are receiving. As with everything, there are multiple possiblities and these are only a few of the more common ones.
|
ERROR
Windows reports random "Fatal Exception Error 0x:xxxxxxxx" error messages even
though your previous version of Windows or Windows for Workgroups did not.
CAUSE
A common cause for these error messages is faulty memory (RAM) on the computer. The following are reasons why your previous version of Windows may appear to run smoothly while Windows may report random "Fatal Exception Error" error messages:
* All operating systems use memory differently. In Windows 3.1, the "bad" memory may be used for holding rarely used data. In Windows, the "bad" memory is used for holding frequently run program information.
* Windows 3.1 contains comparatively little 32-bit code. Windows 9X uses much more 32-bit code. Furthermore, there are subtle differences between the way memory is accessed if it is being
accessed for code or if it being accessed for data. Because Windows runs much more 32-bit code, these subtle errors show up more often.
In particular, all the 32-bit code in Windows 3.1 resides in one place: at the low-end of physical memory. If the first 4 megabytes (MB) of memory can handle 32-bit code, Windows 3.1 works without errors. This is true even if the topmost physical memory cannot run 32-bit code because Windows 3.1 does not run 32-bit code outside the first 4 MB of RAM.
Windows runs 32-bit code in all portions of memory. Therefore, when Windows runs 32-bit code in a section of RAM that cannot run 32-bit code well, you may receive "Fatal Exception Error
0x:xxxxxxxx" error messages.
* Windows 9X interacts with hardware differently than previous versions of Windows. This is due partly
to Plug and Play and partly to new drivers that take advantage of the additional capabilities of
interface adapters. These features may uncover anomalies in the hardware that never appeared
in previous versions of Windows because earlier versions did not attempt to exploit these
features.
* Many new computers do not have memory chips that perform parity checking; therefore, you may
have been encountering parity errors in Windows 3.1 without realizing it because the errors were
in relatively harmless sections of memory. For example, in a Microsoft Word for Windows
document, the word "the" is changed to "tie."
|
ERROR
You receive a "Fatal exception 0E" error message when the Windows Start sound event is played during startup.
or
When you play a Windows Sound (.wav) file, you hear static.
or
When you play a .wav file, your computer restarts.
or
When you play a .wav file, your computer stops responding (hangs).
or
When you play a .wav file, nothing happens (you hear no sound at all).
or
Your computer reboots after playing the Windows startup sound.
CAUSE
This behavior can be caused by a lack of support for 16-bit direct memory access
(DMA) on your computer.
|
ERROR
After you install Windows, you may receive the following error message when Windows
starts:
A Fatal Exception 0E has occurred at 0028:XXXXXXXX in VXD
SYMEvent(02)+XXXXXXXX.
CAUSE
This behavior can occur if an older version of a Symantec program (such as Norton
AntiVirus) is installed.
|
Invaild Page Fault Errors Windows Protection Errors Stop Messages
|
|
[HOME] [SYSTEMS] [ABOUT US][CONTACT INFO]
|
  
|
|
