Discussion Locked

Fatal Exception Error at...

0 helpful

8 replies

by shuja52 Dec 10, 2002 last reply Feb 1, 2003 1 view

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

I have a PC PIII 1.13 GHz, 128 MB RAM, 40 GB HDD, Intel Based Chipset Motherboard and ATX Cabinet, Dual Booting with Windows 98 and XP, I have a blue screen of death in windows 98 several times with the messahe A Fatal Exception 0D occur at 0028:c02402f1/f6 VXD VMMC0ej + 000012f1/f6 .. and in Woindows XP it simply hangup.

any suggestion for troubleshooting?

8 replies

by cglrcng9 Dec 11, 2002

Only thing I can tell you is it is a VXD or Virtual Device Driver hanging the system up. Go to C:\Windows file and find the Bootlog.txt file in each OS, open it up, read thru or print it (warning, this will be a long print process, have plenty of ink, paper & patience on hand if you do) & look for a failed VXD device (device that tries to load & fails during the boot up sequence in both OS's as they attempt to load). Once you determine the device, try reloading the drivers for the device or uninstalling the software that loads (or calls for the loading) of the VXD (virtual device).

One more thing, is it possible you use the free Zone Alarm firewall and upgraded while the firewall was open & running? Sometimes that causes the symptom youcall out of a failed VXD hanging up the system, if so, there's an easy fix of just deleting the VXD file, uninstalling the software for the firewall, downloading & installing it anew.

Good Luck!

by shuja52 Dec 13, 2002

I have stand alone PC, I have not installed any firewall as such.
I have checked logged files, but failed to find the particular device fail information, any other way?

by shuja52 Dec 13, 2002

Point value changed by question poster.

by cglrcng9 Dec 13, 2002

Yes....Click Start>Run...Type msconfig & Hit Enter. When the MS Configuration window opens, click the Selective Startup button uncheck the startup items box for a start, click Apply, then OK. Then reboot the computer. Does it start & run normally? If so it is a startup file program that is causing the problem, check the startup list. If not, then through a little trial & error you can find the problem device by unchecking another box (try win ini next)and playing the restart game repeatedly until the problem goes away. Once the process is found then go to that tab & look for a device marked as "=load device" or "=load VXD" or ="load failed".

This is a process that can take a while but is worth the time in the end when you do. It is simply time consuming trial & error.

The failed VXD is also using (or trying to use)the address f1-f6. Tracking which device it is isn't easy as it is a virtual device, not actual hardware.

Again, Good Luck.