//flex table opened by JP

Click to See Complete Forum and Search --> : Can't Re-install---VXD.VMM error driving me mad


Lancelot2
01-30-2001, 02:53 AM
I was trying to help fix my nephews computer which kept crashing to the BSOD with the error message"Fatal exeption OE has occured at 0028:c000 5338 in VXD.VMM(01), so I tried to fix a number of ways but no go. I then upgraded to 98SE and after installing all the way, just as it got to to the last stage of configuring settings, same error as above. I tried this twice but no go. I then re-installed windows in a new directory(win2) but same thing. So finally I thought time for FormatC. I did this and installed 98SE full version and blow me down, it went a lot further but this time crashed with a message of "Fatal 0028-in VXD VFAT(01). I rebooted and it got into windows and started installing new hardware but after installing a few the same ogiginal error message came up(VXD.VMM). Can anyone offer any help or clues as to what is going on and what I should try.

wizofid
01-30-2001, 04:12 AM
I had something similar happen to me last year on an HP p133. Took me a week to get it to load any OS. It was crashing on a reg basis - OS was win95a with pluspak. no other upgrades. When the smoke cleared, It would not load 95a, 95b or 98se. Finally got it to load win98fe and found that my disk was missing [I think] the very file name that yours is crashing on. I did a file name search and found the file on another machine - using dos - I loaded it back into the same spot on the machine that was crashing and luckily it ran.

Just maybe? wiz

BFlurie
01-30-2001, 08:24 AM
This is most likely a hardware problem, occurring in one or more of the virtual hardware devices embedded in vmm.vxd or vmm32.vxd. Do any problems (exclamation marks) show up in Device Manager? Make sure to look @ System Devices.

During a reboot, hold down the Ctl key just before "Starting Windows...." appears, continue holding until the startup menu appears, and choose "Bootlog.txt". Continue, then when finished booting, view the C:\Bootlog.txt file & search for instances of "Fail". Post back.

[This message has been edited by BFlurie (edited 01-30-2001).]

Lancelot2
01-31-2001, 02:36 AM
Thanks for your tips guys, I will give both a try.
BFlurie,I will post the text result back soon.

Lancelot2
02-02-2001, 02:49 AM
Thanks for the tips so far guys. This system was mine once and I did have a good stick of good Apacer PC100 ram but when my nephew bought the Mobo and CPU off me, he used his own 64 meg stick of ram. The thing is that it was working flawlessly for 6 months with no probs until summer came along and the machine kept crashing due to heat. He then installed an extra case fan and moved the machine into an air-con room and it ran well again for a month until this latest VMM.VXD error which keeps popping up sometimes just after a short while after boot and sometimes after about an hour. It is so frustrating trying to find the problem as it was working great!
BTW. It is a K6/2 550, M577 mobo, V3 2000 agp, 64meg PC100 ram, 10gigHD.
Any further help or tips will be appreciated. I will try the replacement ram next but as I said it was working for 7 months with this Ram.