Windows Forum·65,705 discussions

Fatal exception

Locked

Occasionally one of my users on a Win95 machine gets a blue screen with the following message:

A fatal exception 0E has occurred at 0028:C006CAED in VXD SYMEvent(02)+ 00003A21

The advice from Dell was to disable some background apps but it is stillhappening about once a week.

I think this has something to do with drivers for Symantic products. I have downloaded the latest Symevent update from them but have not loaded it. I guess I’m looking for confirmation from someone before I proceed.

Any help would be appreciated.

Rob

Topic

Fatal exception

In reply to Fatal exception

A Fatal Exception 0E has occurred at 0028:XXXXXXXX in VXD
SYMEvent(02)+XXXXXXXX.
This is caused from norton products. Uninstall( antivirus) is my guess. Check scheduler whether you have a virus scan or if ver 5.0,
live update.At Microsoft’s technet site find article Q189655 The fix involves a reg hack so read the article first.

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

we had a similar problem particularly after starting dos programs. If you look on the symantec homepage under symevnt you’ll find something about some old programs (particularly DOS) which call interrupt 21. This causes the fatal exception. You can try to delete the symevnt entry in your registry in the hkey_local_machine section, system, CurrentControlSet, Services, VXD. Be sure to export this registry control first, so you can import it again if it doesn’t work. If you are using norton antivirus, you’ll probably get a couple of error messages when you start the pc next time. If you don’t, then the symevnt probably comes from pcAnywhere. From that you won’t get any error messages.
hope this helps,
Markus

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

I had a problem recently with fatal errors.
I had the hard drive and mother board replaced(under warranty) finally they checked my ram and discovered i had a faulty ram chip, it was replaced and i haven’t had a problem since.

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

I have to agree with answer 3, the ram chips are 99% at fault. Either check the ram chips individually if this happened all os a sudden or if you recently added another memory chip check that it is of the same configuration as the previous as interchanging various types of ram chips has an adverse effect on the PC without anything actually been physically wrong.

Hope this helps,
Regards, NICHOLAS.

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

Rob,
I had the same problem after upgrading to Win98 from Win95. I was using Norton Utilities and PCAnywhere. I was unable to determine which wa the cause and updates did not solve the problem. I uninstalled both and had to delete all referencesfrom the registry to Norton, NU and Sym(antic). I then reinstalled (after verifying through a week or so of use, that the problem was solved) and updated. The problem has not re-occured. It was a pain to resolve, but worked.
Hope this helps – I know it’s been a while since your posting (just joined),
Steve

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

Rob,

My “magic bullet” fix of the decade, and you can check out my reply to another NT 4/Win 95 client shut down problem elsewhere in this forum, is ScanDisk and Defrag. Have had many users encountering the same “Blue Screen of Death” problems, and SD and Defrag has worked more often than not. Just make sure you follow all the steps I outlined. Or you can e-mail me and I’ll be happy to send you the instructions…

Good Luck!

Chuck

Fatal exception

In reply to Fatal exception

The question was auto-closed by TechRepublic

Fatal exception

In reply to Fatal exception

This question was auto closed due to inactivity

[Author]

Replies