• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

VXD errors?? WTFudge???

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

newbienerd

Member
Joined
May 26, 2004
Location
Lethbridge, AB
I've been recently getting errors regarding something called VxD??? what is that?? and what does it mean?? is it a hardware problem?? or does it have soemthing more to do with my windows program???? when I try to boot it sometimes restarts on its own... and I keep getting registry errors... with warnings about windows protection error! what does that mean??? I'm so confused right now. and I think I killed a cpu doing a partition to partition clone on the same disk... errrr...
any and all help would be greatly appreciated...
thanks!!
 

JigPu

Inactive Pokémon Moderator
Joined
Jun 20, 2001
Location
Vancouver, WA
Windows 98 or ME right?

A VXD is a Virtual Device Driver. It's a freaky little critter, but when windows starts having issues with them, it's not good. Based on the VXD, registry, and protection errors, I'd say that your system is fairly well hosed.

On the hardware side of things, it could be your hard drive, RAM, motherboard, or CPU (in order of most -> least likely). For software, it it quite possible that something ate your VXDs and registry for dinner then spat them out. Not really sure if software or hardware is more likely (I'm leaning to software, but hardware is easier to check).

I don't know how to fix VXD errors (short of trying to find and replace the file, but I don't think that will work), though you may be able to restore a backup windows made following the instructions here (Win98). This page should help you with the protection error.

JigPu
 
OP
newbienerd

newbienerd

Member
Joined
May 26, 2004
Location
Lethbridge, AB
Nice!!! thanks for the help... it helps to understand what my problem is when i know what the heck things mean. LOL!!! thanks Jigpu! you've been a lot of help for me since I've joined!! I appreciate it!! I'm learning so much.

The hard ware seems kinda funny I'm having problems with issues like booting and Start up disks. I hardly doubt there is a virus, because it is not connected. The only transfer that could occur would be from my floppies, but that would mean a virus on all my other rigs such as this one.... sigh.. i guess it's back to the old drawing board with me...

How can I tell if my cpu's gone bad???
 
OP
newbienerd

newbienerd

Member
Joined
May 26, 2004
Location
Lethbridge, AB
BTW what is a virtual device driver and what does it do?? how does it affect my system?? can a hardware error like cpu of something in the mobo cause VxD errors? I'm confused!! thanks
 

JigPu

Inactive Pokémon Moderator
Joined
Jun 20, 2001
Location
Vancouver, WA
The only real way that I know of to test if a CPU is bad would be to take it out, and stick a known good one in. But unless you have a compatible processor, that's not much help :D

For your boot floppy issues, does/has your floppy drive read other floppies fine? Floppy drives are very known to die in no time from dust getting onto the heads, leaving you to either replace the drive, buy a cleaning kit, or manually clean the heads yourself with a Q-tip and alcohol. If the boot floppy works fine in your other systems, I'd suspect the drive, and replace it with a different one. If the floppy dosen't work in any other system, try making a new one on a different system and see if it will boot more consistantly.

For the hard drive being weird, I'd check if you can boot from it in a different system if you can. That should either show you if it's the HD (if it still dosen't boot half the time) or mobo (if it works in other systems) that's bad. I'm not sure if it will get into windows, but it should at least reliably get to the point where you can press F8 to boot into DOS instead.



As for what a VxD is/does... A VxD is a driver file, and was used most notably on Win3.1 and Win95 (with Win98 and Win95 also using it, but supporting a newer driver architecture known as WDM as well). The device drivers allow the system to access different devices in the system, and translate the interrupts (requests for attention from a device) into something the OS can understand. It's similar to a very high priority and security privlage program. If a device driver becomes corrupted, the system can no longer talk to the device, and Windows will definatly complain because it knows something is wrong with the system.

Device drivers (be they VxD or WDM) generally cannot be effected by hardware failures, though since they are files, any hardware failure that can cause file corruption can damage them. That's why I listed hard drive (for bad sectors), RAM (bad ram can do weird stuff with files), mobo (for a bad IDE port), or CPU (unlikely, but a bad CPU could also screw up a file).

If you're really interested in more geeky goodness, here is where I learned some of the above on device drivers :)

JigPu
 

RJARRRPCGP

Member
Joined
May 30, 2004
newbienerd said:
BTW what is a virtual device driver and what does it do?? how does it affect my system?? can a hardware error like cpu of something in the mobo cause VxD errors? I'm confused!! thanks

Yes, the processor can cause VxD errors if overclocking the processor and you have a majorly unstable processor overclock.
 
OP
newbienerd

newbienerd

Member
Joined
May 26, 2004
Location
Lethbridge, AB
hmmmm... i will have to wait for my heatsink to arrive b4 i can do tests with my 200 mhz cpu. I don't want to kill it too.. it is my only spare..
 
OP
newbienerd

newbienerd

Member
Joined
May 26, 2004
Location
Lethbridge, AB
Here is my long and boring story... I hope this might explain things better...

I have a Socket 7 system with a P1 At 166 Mhz with 73 mb of EDO RAM... not much but it's fun to learn on. Anyways, the way I set it up was to have a 3Gig HD as C: and my 6Gig parted as D: and F: as slave to the 3Gig. then on the second IDE cable I have a 1.7 gig for swap and other misc files as E: drive and master to my CD-ROM as G: I have two floppies A: and B: (scheme was that A: would hold the startup disk and B: would hold Ghost. I'm too lazy to take out floppy disk and put another one in... LOL!!!)

phew..(wipes brow)

Anyways.. the way I designed it was to have the C: drive do partition to partition clones with Ghost as my software. This was intended to be my form of virus protection.. too much clutter for a small system.. the slave would be disconnected during normal runs and if something happened to my system (virus, system fudge, won't defrag properly... etc.) i could simply clone back from a previous save (formatting the infected disk first before even connecting my slave in). I know this isn't exactly virus proof, but at the time, I thought it would help. While I was tweaking one day and deleting files and cleaning up, I noticed that the disk maintenance wasn't defreging properly and so decided to clone back from a previous "save". Then I started getting messages about my MSI.vxd file or something like that when running system file checker. i don't know when exactly I started getting the VXD errors, but my system would not run properly and would reset itself with protection error messages. I did another reclone but had the same problem again.. is the VXD stored in the MBR? or boot sector?? I tried formatting the C: drive... but got error messages when trying to do a partition to partion transfer from D: to C: I tried running D: as single but couldn't boot. and I was already having problems with my boot sequence and had to restart a couple times before the startup disk would actually load properly. I even tried CMOS resets... to no avail... I then decided to format my D: and transfer the file from F: (most stable and virgin copy) then try to do a SYS with my startup disk after it was done and hopefully it will start up. While doing the clone, it was slow, since it was a partition to partition clone on the same disk... Suddenly I the thing crashed and got this Message about my CPU. not exactly sure what though.. can't remember... anyways... then I had more boot problems... and even to the point when the keyboard would not work or the sreen displayed garbles of characters while trying to run the startup disk. I decided to give my poor comp a rest and try the next day..

NExt day...

I tried popping in my pentium MMX CPU at 200 mhz ( other was 166). this time it worked.. I formatted the C: and D: and cloned from F: to C: after that it stil crapped out with VXD errors and so on... and resets!! errr.. Please note that even with the "new" CPU, I was still having problems with my boots (startup disks, bootable Flop disks....) but not as much as with the other CPU.

I have decided to give everything a rest and unplug my PSU and turn it on and let the jumper sit on my CMOS reset until I acquire more knowledge and wisdom from you guys...

i know that when I do a partition to partition copy that I do not bring over the Boot sector along with it... could this be the cuplrit?? would I be better off doing Disk to disk clones with Image Boot enabled??? just curious...

Well, anyways, this is my long and boring story, I know you guys must be thinking, "What a loser. He doesn't know what he is doing." No, I don't. I am learning... I am learning as I go along, which is why I am practicing on a crappy system... Anyways... I hope you guys can help me out...

Also, just to let you guys know that the system had 98LITE on it (demo version).

Thanks for even reading this....