Exception Errors!

[Chris1259]

Hi all
I am still running an amd 900tb, abit kt7-a raid mb, 256mg sdram, geforce 2 card etc and on a cable modem.

My problem is when downloading clips, mpegs and/or avi's I recieved the following error

"an exception OE has occurred at 0028:C004B87D in Vxd Vfat (01)+00009805. This was called from 0028:C004C09C in VxDFat (01)+ 0000A024"

Popup windows say you may continue normally (YEAH RIGHT).
Sometimes the system just reboots itself and sometimes it just crashes.
In any event I am left with lost cluster files up the ying yang. In order to restart I have to shut the machine complely off, simply choosing a normal restart will not start the computer, I am left with just the post showing.

can someone please help as I am complety fustrated

Thanks
Chris

[strangerstill]

which os?

[ukulele]

Welcome to the Internet. The bigger the file the greater the loss. Sounds like a typical down load crash to me. I hate 'em. If it does it all the time you have a problem. If it is random and unpredictable, and scan disk does not find bad unusable clusters on the harddrive then is is most likely network interference caused by time outs or futile re-transmissions of corrupted data packets. This can be overcome with the three finger salute (Ctrl,Alt,Delete). If you are patient it may let you close the offending application without crashing. Good Luck. If the harddrive is failing get a new one.

[Psycho Logical]

This error has absolutely nothing to do with file sizes, bad hard drive clusters,
a failing hard disk, network interference, time outs, or corrupt data packets.

If you were having disk errors, you'd get messages like "Error writing to Drive C:".

Bad RAM is the only reason for a hardware-generated Fatal Exception OE error.
If it was RAM, you'd get other errors, at times other than just during downloads.

Fatal Exception 0E errors usually occur when a paging protection rule is violated
The retrieve fails, the data retrieved is invalid, or code broke the protection rule.
In these cases the operating system takes over for the appropriate action.

It is most often caused by the website itself using invalid filenames or paths.
VFAT rejects the filename and Windows generates the error message.

Fatal Exception 0E with Multiple MS-DOS Device Names in Path
http://support.microsoft.com/support.../Q256/0/15.ASP

[Chris1259]

I am running win 98 se

[Michael Chiew]

Chris1259

Seems to me that not so long ago you had a PC problem of gigantic proportion. If I remember correctly, some lady owes you big time. I enjoyed the thread tremendously, making capital of your adversity.

How are you, Chris1259. Long time no see.

Have you run SCANDISK to check on your lost clusters.

Let's take a look at VFAT. VFAT.vxd is a 32-bit file access provider. VFAT handles all hard disk requests using 32-bit code. Its job is not limited to file access activities, being tasked with working in an arena known as the block I/O subsystem (input/output devices of one sort or another).

VFAT is a Ring 0 component in the Windows 98 architecture, which makes it very important. It lives in a spot where it's protected from the interference of other would-be intruders into its space. Sort of like being protected as part of an "endangered species", if you will.

In this instance, some buggy thing has encroached on its territory, hence the error message that you've received. If your system returns to normal after a reboot, well and good. But if the problem persists, then you'd be looking at damage that needs to be fixed, pronto.

There are 3 possibilities.

VIRUS
You may have attracted a virus infection with your downloads from the Internet. First thing to do is to check your system for virus. If you're free of it, consider this.

VFAT.VXD
This is a critical component of VFAT. It drives the VFAT project, very important in the Windows 98 architecture hierarchy. If VFAT.VXD is damaged or corrupted, you get the problem you're facing.

The solution, of course, is to extract a clean copy from the cabinet files, running SFC (System File Checker). There is a catch, however.

VFAT.VXD is one of more than 40 vxds that reside in VMM32.VXD which loads these 40-or-more vxds on startup. Put simply, VFAT.VXD is embedded in VMM32.VXD. So how do you get it inside VMM32.VXD. Not possible.

Fortunately, Windows 98 provides you with an alternative route for "lost souls" such as VFAT.VXD. The answer lies in a folder aptly named VMM32. You'll find this folder in C:\WINDOWS\SYSTEM.

Windows loads vxds from VMM32 first before proceeding to activate the vxds in VMM32.VXD. Once VFAT.VXD is loaded from VMM32 folder, VFAT.VXD in VMM32.VXD is ignored from startup.

So when you extract VFAT.VXD with System File Checker, remember to specify C:\WINDOWS\SYSTEM\VMM32 as the place to lodge VFAT.VXD.

If you prefer to work with the extract utility in MS-DOS, here is the syntax for it. Extract in SAFE MODE COMMAND PROMPT ONLY.

Insert your OS installation CD (assuming your CD-ROM drive is D). At the DOS prompt, type

D:
D:\>CD \Win98 (where the cabinet files reside in your CD)
D:\Win98\>Extract /a C:\WIN98\BASE4.CAB VFAT.VXD /L C:\WINDOWS\SYSTEM\VMM32

Of course, the other option is to do a clean re-installation of your OS.

RAM
Ram becomes an issue if all else fails in your road to recovery. Fatal Exception Errors do signify questionable ram as one of its causes.

Chris1259, could this be the beginning of something big, something wild like before.

It's always a pleasure to have you back.

Michael Chiew

[TweakerXP]

Don't know what this guy just said but , GOD you gotta love him!!