Computing.Net > Forums > Windows 95/98 > VXD VMM Error

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

VXD VMM Error

Reply to Message Icon

Name: Keith
Date: November 5, 1999 at 21:36:58 Pacific
Comment:

I installed windows 98 and i was getting an SU Error, i ignored the error and got passed it. Then I got into win98 and it crashed with an OE error that said something around, "OE ERROR... VXD VMM(1)". I added these lines to config.sys (got crazy) and hoped this would fix it.

DEVICE=C:\Himem.sys
DEVICE=EMM386
DOS=HIGH,UMB

well it got passed the configuration then it went to the desktop and crashed suddently with an error (explorer) and shortly after, an oe error.


Does anyone know howto fix this? I've removed everything from the config.sys except what is needed.



Sponsored Link
Ads by Google

Response Number 1
Name: jason
Date: November 5, 1999 at 21:54:01 Pacific
Reply:

Keith, I'm getting the same error...

"Fatal Exception Error OE has occured at 0028:C0005338 in VXD VMM(01) + 00004338"
It just did it as I was typing this.
If you hear anything about this let me know.
I'm still searching as well.


0

Response Number 2
Name: bone
Date: November 5, 1999 at 22:31:51 Pacific
Reply:

you shouldn't need anything in the config.sys file. can you boot into to Safe Mode without any problems? what kind of hardware? is it a clean install?, upgrade? without more info, i'd say turn off virus protection in the BIOS and do a clean install with only the video card in the system.


0

Response Number 3
Name: Jason
Date: November 5, 1999 at 23:05:30 Pacific
Reply:

I searched for this one back to August.
This is the final solution according to this guy...

--------------------------------------------------------------------------------
RE:- FATAL EXCEPTION 0028:C0005338 IN VXD VMM(01)+00004338
I have now found the the cause and the cure of the error message, its to do with the AMD processor getting overheated, all that needs to be done to solve this problem is to get a some better cooling to the CPU, all I have done is add a case fan and heavy duty heatsink (and fan) now windows 98 runs like a dream.

Regards
Dave Mac

**I had an extra fan that (after testing the 2) is twice as effective as the first. I swapped them, and mounted the original fan vertically off of the heat sink. So 2 fans cooling the heatsink. I'll let you know how this goes...
Jason

check out 32bit.com tech forum.


0

Response Number 4
Name: Keith
Date: November 6, 1999 at 06:55:40 Pacific
Reply:

Well I don't have an AMD so this might be a different problem:)
I'm pretty sure I can boot into safe mode, and i'm doing a clean install (even did a low-level format for no reason:). Now the motherboard is old, 93 and I dont know if this one has a virus protection on it.. It's an AM board.


0

Response Number 5
Name: Chris
Date: November 6, 1999 at 22:42:19 Pacific
Reply:

Well my bootlog consistantly shows these errors... some shd be familiar to someone
out there.
8:43 PM 11/6/99

(more)
[00037605] Loading Vxd = ndis2sup.vxd
[00037608] LoadFailed = ndis2sup.vxd

[00037641] Loading Vxd = C:\WINDOWS\system\VMM32\ebios.VXD
[00037643] LoadFailed = C:\WINDOWS\system\VMM32\ebios.VXD
[00037644] Loading Vxd = vshare
[00037644] LoadFailed = vshare

[0003764A] Loading Vxd = C:\WINDOWS\system\VMM32\EBIOS.VXD
[0003764B] LoadFailed = C:\WINDOWS\system\VMM32\EBIOS.VXD

[00037664] DEVICEINIT = MTRR
[00037664] DEVICEINITFAILED = MTRR

[000376A9] Dynamic load device
[000376AB] Dynamic load failed : [000376AC] File not found

LoadStart = ATILCD.DLL
LoadFail = ATILCD.DLL Failure code is 0002


0

Related Posts

See More



Response Number 6
Name: bone
Date: November 7, 1999 at 01:17:48 Pacific
Reply:

i checked my BOOTLOG and found some of the same errors you have:

Loading Vxd = ndis2sup.vxd
LoadFailed = ndis2sup.vxd

DEVICEINIT = MTRR
DEVICEINITFAILED = MTRR

Dynamic load device
Dynamic load failed : File not found

the first 2 are common and supposedly "normal" (whatever that means...). MTRR stands for Memory Type Range Registers and i believe it depends on your processor or chipset. i'm not sure about the 3rd one though, and i also had other failures that you don't list. at any rate, i haven't had any problems for some time with my machine, so it looks like those EBIOS.VXD errors you have are the problem. i searched my system and did not find that file. it may be motherboard specific. i hope that helps at all, good luck.


0

Response Number 7
Name: Landon
Date: November 7, 1999 at 18:56:56 Pacific
Reply:

Check out the page http://support.microsoft.com/search/default.asp

It may shed some light on your problems. Choose windows 98, leave it on keywords, and put ndis2sup.vxd in the search engine


0

Response Number 8
Name: browser
Date: November 8, 1999 at 09:39:22 Pacific
Reply:

From: windrivers.com

Field Notes - May 1999

VXD Blue Screen of Death Fix
Windows 98 installation builds a generic driver that is named VMM32.VXD at the time of installation.
The vmm32.vxd file is not necessarily the most optimal driver to use with any given hardware that you might own. This is the reason that some users of 98 will never experience a problem related to the 7 vxd's that installation fails to extract, and some will be plauged by continuous BLUE SCREEN's OF DEATH screaming out to users: A FATAL EXCEPTION HAS OCCURED AT blah blah blah in SOMEFILENAME.VXD yada yada yada.
It is important to note here that not ALL Fatal Exceptions will cease in all cases. However, in almost all cases where users were getting Fatal Exceptions related to VXD's the situation is corrected immediately, and does not continue or return later. Fatal Exceptions that contain errors not related to VXD files may continue to haunt you, and in fact might get worse, although not through any action of the VXD_FIX.BAT file, but rather because the problem that is causing the F.E. in the first place, if un-corrected may deteriorate system stability even further.
What are .VXD's and why does Windows 98 need a fix?
Windows 98 has a small glitch in it's installation routine that fails to copy 7 .VXD files to your computer.
The results for many users of Windows 98 are:
1. System instablity
2. BSOD's (Blue Screen Of Death)
3. Mouse lockups
4. Problems during Shut Down.
5. Screen suddenly freezes, ALT+CTRL+DEL will not recover.
If YOU have experienced these problems, this fix alone may eliminate them completely!!

http://www.mcs.net/~revolutn/win98_vxd_fix.htm


0

Response Number 9
Name: Jacques Kreitmann
Date: July 11, 2000 at 00:59:58 Pacific
Reply:

I'm plagued with VXD VMM BDOD errors on an old box I reinstalled with W98, and I hoped to find help on the http://www.mcs.net/~revolutn/win98_vxd_fix.htm URL... but I get the NOT FOUND message. Any alternative ? Thanks in advance !


0

Response Number 10
Name: Peter
Date: July 15, 2000 at 10:56:26 Pacific
Reply:

Hi...

I have been lucky enough to find that the
http://www.mcs.net/~revolutn/win98_vxd_fix.htm URL for some reason has changed to:
http://www.mcs.net/~revolutn/win98_vxd_fix.htm

I have tried to follow the instructions on the pages without any luck - but perhaps it will work for some of you...


0

Response Number 11
Name: Peter
Date: July 15, 2000 at 10:58:20 Pacific
Reply:

... sorry didn't get the right URL pasted. Here's the right one:
http://users.megapathdsl.net/~revolution/vxdfaq.html


0

Sponsored Link
Ads by Google
Reply to Message Icon

wininet.dll and kernel32.... Driver for sd6425



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: VXD VMM Error

k6-2-450 vxd vmm error www.computing.net/answers/windows-95/k62450-vxd-vmm-error/9764.html

Suggestion If You Get BSOD/VXD.VMM Error www.computing.net/answers/windows-95/suggestion-if-you-get-bsodvxdvmm-error/68862.html

VXD VMM Error???? www.computing.net/answers/windows-95/vxd-vmm-error/3161.html