|Posted on Wednesday, March 1, 2000 - 9:33 am: |
When I boot, I get constant beeping and a keyboard or, now, a memory error. When I unplug and replug the keyboard, generally the computer comes up to windows and runs fine. Sometimes however, I get an VxD___ Error - Something lie 0E 0028:002ABDF5 in VxD__; VxD VMM(13) = 000005D5.
What does this mean? This conflict has existed since I built the machine, about a year ago. But the VxD error is new and forces a reboot without being able to shut down window (and all the annoying things that result).
Thanks for your help. As always, you are indispensible.
|Posted on Wednesday, March 1, 2000 - 10:21 am: |
well. i had the same problem yesterday. i attribute it to one of three things. one, i added a new video card, two, i have a removable hard disk as my "c" drive; it's in a removable rack, and three, it could have been a bug from the y2k stuff for the leap year of feb. 29, 2000. it took me awhile to figure it, but i think either it was a y2k bug, or i didn't have my "c" drive connected (pushed in all the way).
anyway, the problem went away after i shut down for about 10 minutes. this was around 11am. no problems after that. it's working fine today.
as far as the error codes. oe means "output expected" and the first string 0028: is your hard disk. i believe you had a problem with trying to access the hard disk using the virtual device driver for the virtual machine. if this continues, you MAY have to reinstall either the virtual machine or windows. once it gets corrupt enough, forget it. reinstall windows.
but for now, see what happens. it might be ok. just a glitch. i hope this has been helpful.
|Posted on Sunday, March 5, 2000 - 11:01 am: |
Actually, this is a chronic problem, not just on the 29th.
Any other thoughts. Also, how do I reinstall the virtual machine. I have already reinstalled windows and that helped some, but it appears to be getting more corrupted again.
Thanks for any help.
|Posted on Wednesday, April 19, 2000 - 1:03 pm: |
I think that perhaps the problems are unrelated.
You may have a keyboard sending a key stuck message. Have you tried another keyboard?
As well, VXD errors are usually well documented on the Microsoft Knowledge base.
www.microsoft.com/kb will forward you to it. Do as search for the exact error.
If you get inconsistent ram errors, I would try other ram, your's may be overheating, or not true PC 100 (if your system requires it.)
|Posted on Saturday, April 14, 2001 - 11:27 pm: |
Not a 'Doze guru, but after assembling a comp I
once got KB errors that were due to using an
older keyboard than the mobo shipped with. Fixed
it by entering the CMOS setup and disabling AUTO
CONFIG and changing the KB controller from 9.5MHz