Win 98 Crash!

I run Win98 (1st Edition) with an AMD K6-2 500. 128mb Ram, Voodoo3 2000 (AGP) and Soundblaster 16. (ISA) No other cards installed.. Reinstalled Windows lastnight, and installed all the latest drivers.
It keeps blue screening, with a VMM32.vxd error. (tried the fix).
Then crashes saying "Invalid VXD dynamic link call from VMM(09) + 0000B24C to device 43E3 service EA77. Your Windows Configuration is Invalid....

Any ideas, before I buy a new system???

------------------
A General Protection Error has occured - Time to go home...

oops. sorry./

Mobo is an FIC 530+.... with 128 single sdram dimm. (100mhz). It's not over clocked.... Any ideas, before I spend some savings on a new beast!>!??!

------------------
A General Protection Error has occured - Time to go home...

Look at your system proprties and check your monitor drivers for all installed if you see any (xxx.vxd) you can try and extract from cab files

the files that windows fails to extract are

VFLATD.VXD
NTKERN.VXD
VVD.VXD

Win95b in cab.6
Win98 ????
Win98se they are in win98_cab.54
Place in windows\systems restart computer

All the .VXD's I've seen have the same size/date in all of the above O/S
JAT.... https://forums.windrivers.com/

[This message has been edited by sly69 (edited February 13, 2001).]

Thanks for your help.... still crashes out, and hangs.. Ended up ordering an Athlon 900, mobo, and case.. Just hope it's not the memory!

------------------
A General Protection Error has occured - Time to go home...

the VMM driver is the virtual machine manager - in this case the device xxxx is missing - you need to find this device driver and reinstall it - ps. I cannot find a list of device drivers that go above the 04xx range. sorry - try going into safe mode, deleting all devies and restart. You may be using an old non-win98 compat driver - try to obtain new drivers for all your non-standard devices (video card, modem, sound card, NIC, etc...)

------------------
Death is lighter than a feather - duty heavier than a mountian.

To give you more information:

Invalid VXD dynamic link call from VMM(09) + 0000B24C to device 43E3 service EA77

the VMM is the Virtual Machine Manager device 43e3 is a required system driver that is missing (do not know which one) however it does not appear to be anything simple (probably a 3rd party driver). Also try reinstalling the VMM.VXD (may be damaged) also making sure that the version of VMM.VXD is the same as the kernel that you are using (may have occured from a newer version of directx being partially installed or from a newer IE).

Look at the ms knowledge base articles : Q137335 and Q140441

------------------
Death is lighter than a feather - duty heavier than a mountian.

Very likely a driver issue. However trying to isolate which driver causes the problem can be VERY time consuming.

I would consider having Windows re-detect ALL hardware device drivers.

The simplest way to do this is to delete the "Enum" tree in the Registry under "HKEY_LOCAL_MACHINE". Then upon reboot, ignore the "display problem" message and use "Add New Hardware" in the control pannel to re-detech all hardware devices.

Before doing this, make sure you copy all your device drivers and Windows source files on to your hard drive, as you will not have CD-ROM access until after the IDE controller device drivers have been detected and activated.

- James.

Quote:

---

<font face="Verdana, Arial" size="2">Originally posted by Schui:
oops. sorry./

Mobo is an FIC 530+.... with 128 single sdram dimm. (100mhz). It's not over clocked.... Any ideas, before I spend some savings on a new beast!>!??!

</font>

---

You sure you don't mean FIC VA503+? If yes then it probably is the mem stick, as I've ran into that several times already.

What chip sets are on the mem sticks?

Upgrade to SE before you try to extract files with SFC as that is broke in 98 gold!! Something to do with the .sfc log, its in the knowledgebase at MS.