I have no doubt that most other K6-II users do not encounter this problem. That's probably why I could barely find any info on it.
The only info I gathered in my previous searches was from this site:
http://www.infinisource.com/techfiles/fatal-0e-errors.html
Quote:
===========================================
AMD & Temperature
We've received information that running the (older) AMD K6-2 chips over 60ºC (140ºF) will produce a FATAL EXCEPTION OE ...0028:C0005338 IN VXD VMM(01)+00004338 (or similar) errors. So if you are running a K6-2 chip, it's another area to check!
----------------
Here's another short list of things to try:
Check to see if you have the latest drivers installed for your motherboard.
Check to see if you have the latest drivers installed for your video card.
Turn off the external cache in BIOS.
Replace RAM chips.
Reinstall the OS. Do a clean install, by formatting the drive/partition.
===========================================
I basically ran through that checklist:
1) New and increased RAM
2) Latest drivers already installed
3) Tried the external cache switch, nope.
4) Reinstallation of the OS was out of the question. Done that too many times before. I'd rather figure out how to fix specific problems.
5) Cooling improvements...BINGO
Again, since I took those small steps to try to increase cooling in my system, I have not seen the error. Before, if I was working on the PC for say more than 45 minutes, I would get this error causing a reboot+scandisk. After reboot, same error as soon as I logged in OR the PC would just simply reboot all on its own again.
The PC is in a warm environment with no A/C for over a year and the case used to be completely enclosed with the exception of the power supply fan vent and the front case fan vent. It was pretty air tight before.
The steps I took above seems to have worked, so I would conclude that the error is precipitated by heat, and the result was the CPU was operating at below 2.2 volts after running for a while in this climate. I make these guesses because there was VIRTUALLY ZERO INFO ABOUT THIS PROBLEM even with a Google search.
When I found Scot's post above, it was happy happy joy joy all over again. If I encounter the same error in the same PC, then I now know what to try. :)