OE VDX VMM errors

[apollo97]

I brought my system
back from the place that upgrades computers (for the sixth time yesterday) and had another blue screen
fatal error.

The system has a brand new AMD K6 II 450 Mhz processor, a DFI BV3 +(rev.C)
motherboard, a Creative Labs DVD ROM (2nd Gen.), an hp 7200i cd burner, an EIDE WD 4.0
slave drive (01/98) hooked up to a brand new Seagate 4.3 HD, decoder card, USR 56K modem
(08/97), decoder card, sound blaster AWE64 sound card, and a brand new Matrox G 200 8mb
graphic card.

Have you ever come across an error msg. named > OE 0028: xxxxxxxx in VXD VMM (01) +
00004338 ?


It will ask me to push any key and then after I do that, the entire system will either shut down or
give me another series of OE "screen of death". The Tech. told me that sometimes you need to shut
down the entire system (not restart) and then turn it back on after a new program has been loaded.
He said ms is now recommending this. I always clear everything out in the "close program" window
except systray & explorer before I load new programs.

They replaced the system ram three times on the oe VXD VMM error msg. but that error msg. is still occurring. They replace the graphics card 2x.
too. They ran every diagnostic test possible on the hardware and everything check out fine except
their diagnostics
can't check the decoder card. Ever hear of a Creative Labs MPEG Dxr2 decoder card in conflict
with other hardware ?
.....possibly a Matrox G200 graphics card. I'm connecting a ms wheel mouse, hitachi 17" (brand
new) monitor, and an hp 722c printer to the computer - that's it.

Two weeks ago, I had NTKERN fatal msgs and the VDX VMM error messages. they moved the
decoder card from a slot shared by the USB port and I'm not getting the OE NTKERN blue screen
anymore, although, I'm getting repeated VDX VMM error msgs. every time I install a piece of
software or sometimes even when I click on the DUN icon.

At one point, I had a black screen with vertical lines on it - something I've NEVER seen before. I'm
now thinking that the 8MB of memory on the G200 Matrox is defective - even though their diagnostics
said it was okay.

I am at a total loss here and obviously they are too. Any other thoughts you may have ?

Thanks,

Mike (in Ohio)

[MadMax]

Long Post...

If you have a backup set, wipe the hdd and reinstall the OS. If you don't, make one and wipe/reinstall.

If you still have probs, wipe the drive again and take out all non essential components (modem, sound, extra ram, extra hdd, extra cd, etc.) and reinstall a clean OS.

If you still have probs, one of the components that's left is the problem child. Recheck all Bios/jumper settings (make them defaults/standard) on mainboard/drives. Could be a crappy win driver, check for updates for all components.

If you don't have probs with the bare-bones reinstall, add ONE component at a time (with new drivers)and give your OS a workout after each installation. If the system flakes out, you'll know what the problem part is.

If you don't have probs after all components are back in place, your old OS was the problem. Reinstall (NOT restore) ONE application at a time and give your sys a workout, checking for problems.If it flakes, you will know which app caused it.

If still no probs, restore data ONLY from your backup set and deep scan all these data files for viri.

That is my poor man's troubleshooting method if I'm totally stumped by a sys bug and don't have any parts to swap readily available. Someone here can probably put you on track to fixing your prob quicker than that, but this method works everytime if you really can't figure out the problem. I have found it particularly useful when dealing with shops that have sold you bad or incompatible parts yet insist that the work they performed did not create or contribute to the sys error.

Remember, be methodical and systematically eliminate subsystems (software and hardware) from your list of possible trouble makers.

I'm sorry for all the wind.....Good Luck http://www.sysopt.com/forum/smile.gif



[This message has been edited by MadMax (edited 05-26-99).]

[MrEd]

Look at my reply under the post "Fatal Exception Problems" in this thread.

I was having the same problems until I found the fix for it.

-MrEd