Exception OE error

I get the following error message on boot-up:
"An exception OE has occurred at 0028:Coo32787 in VxD VFAT (01) + 00009D7B This was called from 0028:Coo326C2 in VxD VFAT (01) + 00009CB6 It may be possible to continue normally"

Sometime I can hit any key and it boots just fine from that point on, but sometimes that message pops up 3 or 4 times and all is fine then and sometimes it freezes and requires a hard boot. I am at my wits end trying to figure this out, here is what I have tried so far.
I have removed everything from the startup (MSCONFIG) one thing at a time and test then remove another one and test again. Then when I get a normal boot I try a couple of times to see for sure then add it back and test again. So far I can't seem to narrow this down.

If this turns out to be difficult then I will increase the points as needed.
LVL 17
rayt333Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

iwinCommented:
have you done sfc to see what's gone wrong?
sfc might not even detect the problem.

The generic driver Vmm32.vxd (located in C:\Windows\System) was built when you first installed Win98 on your computer. Depending on your hardware specs, it may contain some or all of the following VXDs (Virtual eXtended Drivers): biosxlat.vxd, configmg.vxd, dynapage.vxd, ebios.vxd, enable.vxd, ifsmgr.vxd, int13.vxd, ios.vxd, parity.vxd, reboot.vxd, vcache.vxd, vcd.vxd, vcomm.vxd, vcond.vxd, vdd.vxd, vdef.vxd, vfat.vxd, vfbackup.vxd, vflatd.vxd, vkd.vxd, vmcpd.vxd, vmouse.vxd, vmpoll.vxd, vpd.vxd, vsd.vxd, vtdapi.vxd, vwin32.vxd, vxdldr.vxd.

Vmm32.vxd is not only slow to load (because of its huge size), but if you have added/changed your hardware devices after installing Win98, this old driver might not match your system specs anymore.

Certain system errors, like random lockups, error messages at startup, VMM errors, erratic and/or slow mouse movement, etc, might be resolved by selectively overriding a VXD included within Vmm32.vxd

vcomm.vxd, vdmad.vxd, configmg.vxd, vdd.vxd, vmouse.vxd, ntkern.vxd, vflatd.vxd should be in cab 47 and 48.  Put them in both c:\windows\system and c:\windows\system\vmm32 .

Extracting the vxd's to the system and vmm32 directories provides for loading the newest drivers separately. It has been proven to fix lockups, error messages at start-up, VMM errors, erratic/slow mouse movement and many others.

To check if you need the vxd's for yourself, look in the Driver File Details tabs in your Device Manager ( Control Panel > System > Device Manager ). If you find entries containing 'vmm32', there's a good chance you need to extract these manually. For example, in my Modem Driver details, I had " C:\WINDOWS\SYSTEM\VCOMM.VXD (VMM32) " before, and just " C:\WINDOWS\SYSTEM\VCOMM.VXD "  after I extracted the vxd's.  Note: if you're upgrading, rather than doing a clean install of Windows '98, you might have the old, Windows '95 vxd's in your system.
0
dew_associatesCommented:
Ray, is this PC running a Cyrix CPU?

You may also want to extract a new Ifshlp.sys file to the \Windows\System directory.
Dennis
0
rayt333Author Commented:
AMD 450
Have ran SFC and nothing found
The file Ifshlp.sys is located in the Windows folder not Windows\system. I will try replacing it but first should it be in Win\Sys??
 
PS Happy New Year!!!!
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

rayt333Author Commented:
Also this is not happening on a new or recently updated system, this system has been running for several months with no problems, nothing new installed just suddenly ERRORS!!! After you get by the error at boot it works very well with no problems that I can tell. No more then usual anyway.
0
iwinCommented:
you might be surprised if you'd at least extract vfat.vxd!

Happy 2000!
0
Patricia Siu-Lai HoCommented:
Ray, It sounds like a video cache/PnP extension board error.
Perhaps try to lower the resolution to 600x480 16bit color and remove display adapter in safe mode and reinstall it again.    pslh
0
dew_associatesCommented:
Ray, as long as ifshlp is in the windows directory it should be fine.

I would try and replace it as well as vfat as iwin suggested, and then move onto something that may have changed such as video as pslh suggested.
0
rayt333Author Commented:
OK I have done some searching and the file "vfat.vxd" does not exist on my system.
Could this be the problem??

What folder should this be located in?
0
dew_associatesCommented:
It's only loaded if your system requires it and it's normally part of vmm32.vxd when its is built. I wouldn't worry about it if its not there. Have you run a real thorough disk check on this system?
0
Patricia Siu-Lai HoCommented:
Thank Dennis, My system also does not have this file Vfat.vxd but there is no problem, I just wonder.

Ray, here:-
VFAT.VXD
Virtual File Allocation Table (FAT) Device 32-Bit File Access Provider (VFAT)(Base).
WINDIR\SYSTEM\VMM32
WIN98_48.CAB
0
iwinCommented:
guys, just the fact the you don't see a particular *.vxd doesnot mean it's not there.  It's built inside vmm32 in compressed format if it were needed at setup.  No one have to WORRY the absence of a particular vxd until error occurs such as in your case.  With a "REAL" vxd extracted to the appropriete directory can only speed up process and reduce error.  It's a know bug which Bill did not admit.
0
dew_associatesCommented:
Iwin, read my earlier post please. And as for a known bug, do you just invent this stuff because you have nothing else to say or what? Vfat is a virtual file allocation table used by Windows as a diagnostic to compare against the two fat tables that appear on the system at the beginning and at the end of a drive.
0
iwinCommented:
Denise, I don't invent this out of the blue.  That "known bug" is known to the win98 forums and you or others might not have stumble across.  I happened to have viewed it and saved the posting. I absolutely agree with the technical definition you have depicted above.  Furthermore, extracting just vfat.vxd alone might not cure the problem. Exception OE might have originated from some other virtual devices and domino into vfat.
0
iwinCommented:
Umm, I don't have anything else to say 'cause I believe vmm32.vxd is the major culprit causing the problem.
0
rayt333Author Commented:
OK here is where I stand on this:
I have ran scandisk with no errors found
I ran SFC which found no problems
I have removed everything from startup via MSCONFIG (except Systray)
I downloaded the latest drivers for the video card (no help)

OK here is the worst part, I used SFC to replace the file Vmm32.vxd about half way thriugh an error message poped up say something like it couldn't replace that file (exact wording I can't remember and no way am I going to try again) But anyway when I rebooted I had errors galore, I think every VXD was missing, after going through them all then the computer would just shutdown, I tried in safe mode and same result.
So then I decided to reload win98SE over top of itself to fix the missing files, this was a nightmare since everytime it had to reboot either I get the original errors again or it would just lock up. This has been an all day project so far, I know the easiest way would be to format and do a clean install but this HD has alot of very important (and irreplaceable) programs on it and since it is 18GB no easy way to back them up.
OK after all of this I have it back running but the problem is still there, where did I go wrong and what do I need to do to fix it??
0
rayt333Author Commented:
Another thing too now the error message now is not exact as the first one but simular and it seems to change every few boots to a slightly different number or something, if it is important I can write them down each time but I didn't think it was very important.

On the bright side I haven't lost my temper yet, very close but .....
0
rayt333Author Commented:
iwin
You may be right about the vmm32.vxd but how can I replace it without using SFC ??? Or how do I use SFC without the error??
0
dew_associatesCommented:
Ray, you can sit there until the cows come home and you won't be able to replace the vmm32.vxd file as it is built during the install process. Although Iwin may not agree, I really don't care what the Usenet or Newsgroups have to say as I have a full CD of the bug issues on Win98 from RC1 through Win98SE RTM and this is not an issue.

Iwin, by the way, the name is Dennis, not Denise!

Ray, I would start cleaning up that drive as much as possible and then look at device manager in safemode and look through all the devices listed for problems.

This aside, start from the basics. A Vfat error is not a software error. This error results from a hardware problem.
Dennis
0
rayt333Author Commented:
OK Dennis I will do that and get back to you
0
iwinCommented:
Sorry Dennis, I maybe I'm too used to SE with win98 ..:)

Ray, donot replace vmm32.vxd!  You don't do that, leave it alone and that's never be what I suggested all along.  The way to tackle this is to extract those individual *.vxd from the cab and place them into \systems and \vmm32

These *.vxd should standalone along side with vmm32.vxd so as to override (not overwrite) the  prebuilt *.vxd inside vmm32.vxd !  The whole idea is to let these *.vxd outside of vmm32.vxd to handle the job.  NOTHING might be wrong with those prebuilt vxd inside vmm32.vxd, the problem is vmm32.vxd is too huge and crowded dependent on your intial setup, CALLS to these individual vxd cannot be executed normally so that win98 o/s thought something went wrong.

Again, none of these various vxd errors should occur if everything went well as planned by MS, but they just happen and MS still don't want to put them in KB.

Hey Ray, I admire your confident and patient, keep it up.
0
gonzal13RetiredCommented:
Rayt333: Since I believe you have acess to alot of hardware in your facility, why not use a tape back up, format, install Windows SE, and reinstall everything except the original windows. Also I do not believe the registry would be a problem so I would back that up also.








Ray333: I believe that you have a PC fab shop. In that case whynot back up to a Tape drive the hard drive. Thein reformat, Install Windows SE, and then reinstall everythng except the original windows. Also back up your registry.
Obviously you know to back up your data, e-mail and favorites seperately in case somehow which I have rarely experienced, that the tape is corrupted.


















0
rayt333Author Commented:
gonzal13
Backup and restore is a last resort, but always an option. I am of the school that we fix the problem and not use the "format and install" or use restore disk until that is all that is left or too many problems to fix.

I was thinking this was a software problem but really not sure, I have no hardware problems, at least none that shows up in device manager, this problem only shows up at bootup, after it finally gets booted up then everything runs fine.

OK today I reinstalled Win98 (mostly to see if it would install after having Win98SE) it did, then I installed Win98SE and wouldn't you know it the "blue screen" showed up in the middle of the installation halting it, but it recovered just fine and finished, so far no more problems but I haven't rebooted it since the installation is done. All the Windoze installation was over top of old installation not a clean install.
I really don't believe it is fixed yet so I would appreciate any more suggestions as to what it may be.
0
iwinCommented:
One thing to do is to print this entire post on hard copy and sit down with a beer, digest each comment line by line, 'cause these comments are trying to tackle the problem from different angles, so you never know you might have missed something important.
0
gonzal13RetiredCommented:
Clean installs are the best, when using anoter version of windows. Otherwise when using the same version, you should not have a problem.
0
rayt333Author Commented:
This is to anyone that is still interested, I have not forgotten this question, I have tried several thing with no luck, I finally did a format and a clean install but for some reason in the middle of installing the dreaded "blue window" poped up saying something about a Exception error again and locked the computer up, I did a hard shutdown and restart and setup recovered where it locked up and finished normally. Since this  error showed up after a format and a clean install then I am assuming this may be a memory problem (first step, get new memory chip) or maybe a hardware problem (if so then scrap this one and build a new one with different parts)
I have ran for a few days without any errors but I am still waiting for the memory to try it.

OK now to my next question: I am looking for suggestions on how to close this question out.
1. Should I keep it open for a week or so longer in case of more suggestions (but if error gone then no way to test them)
2. delete the question and split the points between the best comments that may have led to the correct solution if everything was perfect? (as in no computer is exactly the same and a correct solution for one may not work in another)
3. any other ideas???
0
iwinCommented:
I'd like this question to remain open for a while whatever the outcome might be, then post your final result.

thank you.
0
dew_associatesCommented:
Ray, let's see how the memory change shakes out1
Den
0
gonzal13RetiredCommented:
Just remembered. On one machine using the OEM disk, I ran into all sorts of problems including clean installs. Finally, to the amazement of my wife, I was debugging two computers at the same time writing a websit on the third. Oh, it finally worked. The machine I had problems with has an old cd-rom, which could have been the problem.
0
rayt333Author Commented:
OK I think this is been long enough, since I did the format on installed Win98SE clean there has been no problems with the exception OE (except the one during the install where the computers boots to finds installed devices)  Who knows then, maybe it was just a fluke and now it seems everything is fine. I have not changed the memory since the error did not show up again so there would be no way to tell if that helped.
BUT anyway I am ready to delete the question and give points to Dennis and iwin for at least pointing me towards what may have been the problem (vmm32.vxd) it sure make sense but I could not get it replaced except by reinstalling clean. I will leave this open until 1\19\00 then I will delete it unless someone has some objections to that.
0
dew_associatesCommented:
Ray, if its okay with you, you can accept this and I'll create a split with IWIN. I'd like this kept as a PAQ.
Den
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rayt333Author Commented:
Works for me
Thanks for the effort put forward by all
0
dew_associatesCommented:
Anytime Ray...Your should investigate this new Intel OR840 motherboard. This one's going to be a home run!
0
iwinCommented:
all the best to you all!
0
dew_associatesCommented:
iwin, you have points waiting for you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.