5 replies
by thechas
One or more of the virtual device driver files are corrupt.
This happens most often when Windows has problems with the system memory.
If the system has more than 511MB of RAM, you likely need to remove some to escape a Windows bug.
If less than 511MB, either 1 DIMM may be going bad, or if there are 2 DIMMs, they don't get along with each other.
It is not impossible that a DIMM or CRIM is comming loose.
If the user just added RAM, check for a BIOS upgrade for the MB.
The above is to prevent the problem from re-occouring.
Now, to get the system repaired, and booting;
If you can boot to safe mode, remove hardware, and delete the .vxd files from the system32 folder.
If not, attempt to delete the files from DOS.
I have a hot swap bay on my main system so that I can temporarily install reluctant drives and delete suspect files.
After deleteing the .vxd files, you may need to re-install Me over the top of itself to repair the files. (This will leave the users files,settings, and application program installations in place.) At a minimum, you will need to re-install a few device drivers.
Chas
by europanorama
by europanorama
by europanorama
by europanorama
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending