FOr those of you that have the AMD processor, and are getting:
Fatal Exception Occured 0E at 0028:C0005338 in VXD VMM(01)+ 00004338
I spoke to AMD about 15 minutes ago. THey suggested changing the voltage on the motherboard from 2.2v to 2.3v.
I did this, and I cannot recreate the problem!!

Hi Scott,

If you read this, pleas tell me how to change the voltage to 2.3V !I can only find 3.2, 2.9, 2.8, 2.2 and 2.1 in my mobo's manual.

Tim,
Hard to say.... I have an ASUS P5A-B motherboard. It has it in the manual. I would call AMD and let them tell you what you should set it to depending on your mobo.

Thanks Everyone... But Scott you helped me the most, Stoped 8 months of tearing my hair out.. simple voltage change and so little...
Thanks All
HUGzzzz PJ

I have a Aopen AX59Pro motherboard with an AMD 500 Mhz processor - same problem. I took Sco's suggestion and and set the jumpers on my motherboard to define my CPU with 2.3 volts (core) instead of 2.2 as noted in the specs. Making this change solved my problem. Thanks Scot!!!!!!!!!!

I get the VXD errors usually at startup and I am useing a amd 350mhz processor.. theres usually the extension VMM after the VXD though sometimes its different like LOGFILE etc...errors. Does my problem have to do with the voltage as well?

got the same problem myself,
did you also have trouble when insatalling
windows(98)??.
gonna try the voltage thing, hope it works
any feedback would be appreciated.

Scot thanks for the tip...
I attempted it but my crappy motherboard...i got it for free when i got the chip, what can you expect :) .. would not allow me to change the voltage... it was set at 2.4v..i was overclocked to 500mhz hehe... but i lowered my bus down from 100mhz to 95mhz...when i restarted, i ran final reality..the benchmarks were incredible...faster than ever...as i looked on with jaw dropped i still didnt believe it..so i ran the mad onion 2000 benchmark...the results were astounding...major improvements...AND THIS WAS WITH STANDARD PCI VIDEO DRIVERS... AND IM RUNNING A VOODOO 3 CARD...but the moral of the story is ... if you are overclocking ...or dont want to move the voltage...lowere that bus speed...you might get as lucky as I did...Oh by the way ..after installling the new voodoo 3 drivers... I am a VERY happy camper...again...thanks scot...eventhough i have been around the block with computer hardware...for about 10 years now, i started as a child...lol....this one had me stumpped...but thanks to your tip I found my way around this one....

Oh by the way the vxd errors absolutly dissapeared..........i guess THAT is the moral of the story.....

Thanks, Scott...
This simple jumper switch worked like a charm...(AMD K6-2 500Mhz+ASUS P599-VM)

thanx dude i did that and the error went away!!

AMD 500Hz - When I run a game from the CD drive - rewritable RW:
I get "Fatal Exception Occured ?? at 0028:C0002C1D in VXD VMM(01)+ 00001C1D,
Then every thing freezes - ctrl+alt+del doesn't work and I can't even turn off the PC. Please help!

ANOTHER SOLUTION - SIMPLER?!

Hope this helps some of y'all! I have had the same problem on my system running Win98 and a AMD K62 450 processor - to the point that I've given up on it for weeks at a time. We even underclocked the processor to 400 which worked for a while - 'til I moved the box and put it into a computer desk and those pesky messages kept popping up again!

Well, I stumbled upon a site (http://www.waynescomputerworld.com/win98.htm Thanks bunches, Wayne!) which suggested disabling the external cache in the BIOS. I thought, nah - too simple, no way is this going to work! Well, I tried it and have had no blue screens since I did it on Wednesday - and I couldn't do ANYTHING before - got a blue screen everytime I booted up - could never shut down properly. So, since I searched every site imaginable looking for a solution and found that there are literally hundreds of folks having the same problem, I wanted to share this! Hope it works for all as well as it did for me!

Who woulda' thunk it!

Same problem here. I tried a k6-2, 500 and a k6-2, 550 - changed ram, motherboard, you name it. Who would have thought if I would have misread the voltage by .1 would fix it?

hehe, Thanks! :o)

Well, I know my voltage is 2.3, and I am running a truely purchased 550 AMD, but I still get the VSC messages. Never at the same offset, and frequently not in the same area. (Once was NTKERN? - not running NT, only 98) Anyway, Not sure what to do, but will try the disable external cache. If anyone has any other suggestions, let me know, otherwise, I will return this for my money back, and I guess I will go with Intel.

Well, I know my voltage is 2.3, and I am running a truely purchased 550 AMD, but I still get the Vxd messages. Never at the same offset, and frequently not in the same area. (Once was NTKERN? - not running NT, only 98) Anyway, Not sure what to do, but will try the disable external cache. If anyone has any other suggestions, let me know, otherwise, I will return this for my money back, and I guess I will go with Intel.

I have a AMD K6-2 500 AFX CPU & a Jetway J-542C motherboard. I used to have the same problem but now I set the core to 2.3v and it`s working fine, thanx a lot Scot. But still I`m not sure. On the CPU it writes 2.2v core & 3.3v I/O. But on my board there isn`t 3.3v I/O option, only available I/O options are 3.45v & 3.52v. So what should be my correct I/O v? 3.45v or 3.52v? Thanx a lot...

Please copy this message everywhere!
MANY people are having this problem and there are specious "solutions" all over the place. It is the core voltage. I was having the same XXD VMM(01) +00004338 error, and read about the core voltage fix, but when I checked my actual AMD k6-2 450 cpu, it's voltage listing was the same as what was set on my mobo and what the manual suggested. I tried disabling the external cache in the BIOS (another purported solution). No dice. I tried keeping the machine cooler. No dice. Finally after months of frustration, I decided to revisit the core voltage idea, went to get my mobo manual, and a loose piece of paper feel out of the back. It was an (obviously ignored) addendum that specified the core voltage must be set contrary to all other indications. Check for a similar addendum with your manuals, or, if you have the same processor as me, move from 2.3v to 2.4v. Worked like a charm!

For any of you who receive this error intermittently, you may also want to check your cooling fan. The voltage issue seems to resolve this problem in most cases, but a bad or slow-turning cpu cooling fan can cause the same error.

Hope this helps

My brother-in-law has a AMD K6-2 500 AFX CPU & a Jetway J-542C motherboard. I spent several hours trying to figure out Fatal Exception Occured 0E at 0028:C0005338 in VXD VMM(01)+ 00004338. But once I found this post and tried it, everything started working properly. THANKS SCOT