Exception Errors - Windows 98 | Windows98
General Information -
Fatal Exception Errors are codes returned by programs when there is a problem. They can be caused by "Invalid data or code", or by an instruction in the program that has performed an illegal operation. Illegal does not mean "unlawful" (nobody will call the police) but rather performing an operation which is not allowed by the program, or one that the program does not know how to handle.
They happen wither then you attempt to shut down your computer, when you start Windows or when running a program.
They can also be caused by device drivers or applications, like video drivers, which are not properly de-bugged. In such cases its best to look at the troubleshooting or support section of the device manufacturer and see if the problem is mentioned and perhaps there exists a newer driver that you can download.More information -
You can read more about Exception Errors on the Microsoft site KB article Q171195.
Also the Microsoft KB article Q150314 "What Are Fatal Exception Errors?" has additional information.
Finding an error on our site -
*** Please Read This ***
Because so many people, every day, use download programs to download our whole site (over 60000 pages), we have decided to no longer add any more content to this HTML based site. Instead, the new content is added to our database and will ONLY be accessible by running searches. This might turn out to be better anyway because its easier to update and many times faster to find information.
If you have any comments one way or the other use the contact-us link on the bottom of the page to let us know what you think.
|xxxx:yyyyyyyy ( Fatal Exception Error <xy> at xxxx:yyyyyyyy in ...|
Typically this error comes in the form...
A fatal exception <XY> has occurred at xxxx:yyyyyyyy in ABCD
ABCD if it is shown, could indicate the program which caused the problem.
xxxx:yyyyyyyy is a numeric value of the error code. Many times you can find the exact number in the errors shown below which would help you to determine the cause of the problem. Other times this number can vary even when the error happens repeatedly with the same program.
<XY> represents the actual processor exception and is a value ranging from 00 to 0F (zero F). A description of these codes is shown below.
- 00: Divide Fault
- 02: NMI interrupt
- 04: Overflow trap
- 05: Bounds Check Fault
- 07: Coprocessor not available fault
- 08: Double Fault
- 09: Coprocessor Segment Overrun
- 10 (0Ah): Invalid Task State Segment Fault
- 11 (0Bh): Not Present Fault
- 12 (0Ch): Stack Fault
- 13 (0Dh): General Protection Fault
- 14 (0Eh): Page Fault ( possibly driver related)
- 16 (10h): Coprocessor error Fault
- 17 (11h): Alignment Check Fault
The lower case h (as in 0Ah), which indicates the number is uses the "hex" number system is typically omitted from error codes.
|You are at the www.techadvice.com site which is not associated with the company or products shown on this page.|
copyright www.techadvice.com All rights reserved