Discussion Locked

Fatal Exception 0E Win98SE w/ Profiles

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm getting the followng after Windows logon using a profile:

Fatal Exception 0E at 0177:BFF9DFFF

Just preceeding this a "progress bar" flashes that says "Copying" but I can't read the rest.

This only occurs using a profile at logon. If "Cancel" is selected for a "no profile" logon, the system works file. This has happened each and every time a profile is used.

This is a new system being set-up for first use.

6 replies

by vertex

There are numerous posting on Fatal Exception on this Q&A. Some contribute the error message to bad video RAM and etc. My solution have always been the RAM and I will stick to that. Least to say that you have bad SDRAM, it's most likely that your program is trying to write something on the RAM and your OS is denying the access. One way is just to take it out, wait for awhile and replace it again. I have read somewhere that you can go around this problem by resetting your CMOS, I can recall exactly what you should reset.

by mike

Decided to "blow away" the OS and installed Win2k (which works just fine).

by redshift

While bad RAM is a common cause of Fatal Exceptions, many other factors can contribute - I've seen overheating processors, overclocked processors, faulty applications, and bad HDD settings cause this also.

I'd start with disabling the profiles onthe PC and running it for a while to see if that truly solves the problem, or just hides it.

Most likely there's something happening during the profile creation that shouldn't. Try deleting all of your user profiles (or renaming them if they're at a point where that would be bad) and log in under a previously unused name.

Next, I'd reformat and reload. This is a new PC, so the hour that would take is nothing compared to the hours of frustration you face otherwise.

by mike

Decided to "blow away" the OS and installed Win2k (which works just fine).

by mike

Several profiles have been tried, and all have been "nuked" as per a MS KB article on removing profiles.

New profiles behave precicsely the same way, same FE at the same address.

This discussion is closed to new replies.