Ever so often, while I am doing something on the CPU, I will get a blue screen & a statement that reads:

A fatal exception 0D has occurred at 032f:00002D02. The current application will be terminated.

It goes on to tell me to press any key to restart. When I do press any key to restart, this gives me another window that is full of dots all over the screen.

The only way that I have found to clear this is to turn OFF the CPU & reboot it.

Does anyone out there have a clue as to what causes this?

Is there an INDEX somewhere on the NETWORK that one can boot up that tells one what these fatal error message mean?

How Stuff Works - What causes things like Fatal Exception Errors?

Windows 98 and Windows Me Error Message Resource Center

Error message index

Usually re-installing the program that causes the error will fix it. You might try checking with the programs Web site to see if they have any "fixes". You can usually determine what program causes the error by noting which program is running when the problem occurs. You may need to close all others one-by-one to find the faulty one.

I hope something here will help!

Dwight

To Dwight:

Thanks for the Links, however, none of them threw any light on the topic I discussed, however I found lots of help on other Error Messages that I have had troubles with in the pass.

I even went to the Microsoft Knowledge Base & querried there.

The answer they gave me was that:

We currently have no Document that matched my Search.

To Anyone else:

Still searching for an answer. How about TomGL2?

It is listed under Windows 98 and Windows Me Error Message Resource Center It would seem to cover the problem you reported.

http://support.microsoft.com/common/canned.aspx?R=d&H=Windows%2098%20Fatal%20Exception%200D%20Articles&LL=kbwin98search%20or%20kbwin98sesearch&Sz=kbfatalexerr0d

This link is directly to the Windows 98 Fatal Exception 0D Articles.


Dwight

To Dwight:

(1) As I said in my last communications to you, the:

"Windows 98 and Windows Me Error Message Resource Center"

shed no light on the Topic I raised.

(2). The article:

"Windows 98 Fatal Exception 'OD' Articles"

also did not shed any light on the Topic.

(3) I also found no answer in the article:

"Windows 98 and Windows Me Message Resource".

(4) Look at my review from the Microsoft Knowledge Base querry of 12-11-2002 @ 03:02 PM.

The Knowledge Base people said they DID NOT have any current Document that matched my Search.

I also had a lot of problems with Fatal Exception Errors for a while. Couldn't find anything helpful in Microsoft's Knowledge base site or through an email contact with them. I ended up unplugging everything, uninstalling all my programs and doing a complete reformat. Hah- Didn't help at all. I've a HP so finally made a phone call to their tech support and here is what I was told to do.
Go to Start, Programs, Acessories, System Tools, System Information, Tools, System Configuration Utility, Start up -- and disable the following:
Taskbar display controls, hpsysdrv, a second load power profile that was listed, iomega start up options, micros. wks. calendar reminders, HP updates, iomega watch and zip disk icons.
This did the trick for me - - not sure that it would in your case but it may be worth a try.
Best of luck...

I notice that when you typed in:

"Windows 98 Fatal Exception 'OD' Articles"

You used the character "O" instead of "0". That is actually a 0 (zero) character. Likewise, the "0E" Fatal Exception Error is "zero E". Typing a O instead of Zero will of course make searches invalid.

Here is a page that you may find helpful:

http://www.aumha.org/kbefe.php

Read the section under the heading: Fatal Exception 0D

The following is from this page:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q150314#1

Definition of "0D" Error Messages:
General Protection Fault (Number 13 in the list of explanations)

Any condition that is not covered by any of the other processor exceptions will result in a general protection fault. The exception indicates that this program has been corrupted in memory, usually resulting in immediate termination of the program.

Troubleshooting Fatal Exception Errors

Clean Boot Your Computer

Because there are many conditions that can cause a fatal exception error, the first step in resolving the issue is to narrow the focus. To narrow the focus, try a "clean boot" of your computer.

Clean-boot troubleshooting refers to methods of reducing problems that may occur because of your computer's environment. Many problems 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 linked below to view the articles in the Microsoft Knowledge Base: http://support.microsoft.com/default.aspx?scid=kb;EN-US;192926

If after running the "Clean Boot" procedure, you still cannot find the problem, consider the possibility that the RAM memory may be at fault. Read more about this here.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q138788

Hopefully, something here will help.

Dwight

[This message was edited by Dwight on 12-12-02 at 10:10 PM.]

Dwight:

The O's were just typograghical errors in the statement I made. I actually used "0" Zeros in the search.

Your link:

'http://www.aumha.org/kbefe.php'

is similar to one I found, the link of which is:

'http://www.generation.net/~hleboeuf/fatlexer.htm'

However, my statement regards to the Topic I started still stands, Nothing in these two documents give any answer to the Topic I raised, because it has NOT been answered by Microsoft, as I said in the second communication with you.

I am aware of the General Protection Fault information regards to Memory. I do not believe that Memory is my trouble as I have the maximum of 256-Mb in my IBM 2153 E4N CPU.

I am going to try looking at Q192926 & Q138788 & see if they have any effect on the problem. I will get back to you regards to this matter, one way or the other to let you know if these Q's helped.

[This message was edited by donaldekliros on 12-13-02 at 05:35 PM.]

"I do not believe that Memory is my trouble as I have the maximum of 256-Mb in my IBM 2153 E4N CPU."

In this instance, the problem is not lack of memory, it is the memory itself...bad memory cards, or a hardware problem with the memory slots.

I would think if this were the problem, you would see the Fatal Exception Error more frequently, but it is a possible cause.

Dwight

Dwight:

I did a Norton Diagnostics of my Memory & it all checked out OK.