Windows Fatal Exception OE

Topic

New Reply

Hi,

I am having considerable trouble running Microsoft Office 2000 (Professional) – Word in particular! with my version of Windows (Windows 98, dated 4/10/98). I usually only last about 5 minutes in Word before the machine crashes – usually in one of three ways: Screen just completely freezes, screen colors go crazy with vertical black lines running down it, or the screen goes crazy with horizontal black lines running through it. Usually after this happens and I restart the computer, I get a windows fatal exception error OE at 015F:xxxxxxxx. I don’t know if the 015F location is significant, but I would say at least 80% of the time, it occurs at 015F. I have searched the Microsoft web site for answers and asked numerous friends, but no one has an explanation. It is extremely frustrating.

Does anyone out there have any idea about what might be going on?

I keep a log of all the crashes now (to justify my loss of productivity during the day), so could probably provide more relevant information if I knew what I should be looking for.

Thanks in advance for any help out there!

Susan

Reply | Quote

Replies

Susan, the easiest thing to try first is to do a reinstall of Office, it may just be a corrupted file. Do you have the SR-1 release of Office 2000? If not then download and install it as well.
Let me know if this doesn’t solve it.

Reply | Quote

Thanks for your suggestions. I did as you said, including downloading the SR-1a and Installed that and then when it went to reboot my computer, the monitor died. Eventually I swapped my monitor with someone who is off sick (sneaky, I know), whose monitor worked fine, confirming that mine has died. However, after all this I went in to work on a word document and within 5 minutes, the screen went funny with the usual black lines going throughout.

After rebooting, yet again, I had my usual windows fatal exception error OE @ 015F:xxxxxxxx! I had such great hopes, but alas have wasted almost an entire day – again!

Any more suggestions greatfully appreciated. I really would like to get the problem sorted!

Reply | Quote

The description of your problem sounds like it’s something more serious than a corrupt file. I’m guessing to a certain extent but I’d check:
1) first I’d do a thorough scan disk
2) my graphics card
3) my graphics driver

I’m also wondering if this happens with other programs. You ought to have someone open the case & clean it out & check the connections. It sounds sort of like a TV that warms up & then goes out–i.e. like a hardware problem.

Reply | Quote

I would look at the CPU, it could be the cooling fan has failed. From the description it could be the video card, check it that has a cooling fan and if it has, does it work.

Definately sounds like a hardware problem

Reply | Quote

I read in another forum about a hardware problem where the fan was still running, but too slowly. Replacing it with a more powerful fan cured the problem.

Reply | Quote

I was fascinated by this post because I have been chasing similar demons in 4 machines in my own environment. My scenario has a slightly different twist – they are all Windows98 running SR1 and one of them additionally with SP2 as a hopeful remedy. Word performs fine until they attempt to use the File | New procedure to access templates and then BLAM the BSOD and they’re down for the count. In all of our machines the User Template path is mapped to a network directory unique for each user. Except these 4 machines, all other machines with this setup are doing fine. Deleting the registry keys for User data, options and common momentarily cleans up Word’s act but as soon as they reboot and hit File | New they are back to square one with the BSOD. Interestingly though these same machines can use Start| New Office Document and dump straight into the template selection menu with no problem and work just fine.

As for your particular situation, could it be a bad video driver on your machine? I’ve seen this happen before with WP8 and it was a video driver conflict with the software. Weird but true.

Any ideas on my situation will be greatly appreciated.

Reply | Quote

P.S. The IT guys here say you could be experiencing a stack flow error? That’s greek to me since I’m not hardware but perhaps it will mean something to you.

Reply | Quote