General discussion

Locked

Invalid VxD Dynamic Link Call

By holt_m2 ·
One of the PCs in our school system has error at startup "invalid vxd dynamic link call from VREDIR(01)+00005B12 to device 0487, serive 4. I work primarily with Macs and only have a little experience with Win9s5. I've tried reinstalling Win95 4 times with no luck. Before I result to reformatting does anyone have any suggestons?

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Invalid VxD Dynamic Link Call

by wirejockey In reply to Invalid VxD Dynamic Link ...

VREDIR=Virtual Redirector

Hi, you have a device driver problem. VREDIR is usually associated with a network device. Try reinstalling the network drivers. You may want to see if there are new drivers for the NIC you have. If there are, install those.

Here is the link to the KB article on the Microsoft Web site.

http://support.microsoft.com/support/kb/articles/Q137/3/35.asp?LNG=ENG&SA=ALLKB&FR=0

The Article I Q137335

Good Luck

Collapse -

Invalid VxD Dynamic Link Call

by holt_m2 In reply to Invalid VxD Dynamic Link ...

The question was auto-closed by TechRepublic

Collapse -

Invalid VxD Dynamic Link Call

by WColeT In reply to Invalid VxD Dynamic Link ...

SUMMARY
This article describes the three parts of the following error message:

Invalid VxD dynamic link call from <Part 1> to device <Part 2>, service <Part 3>


MORE INFORMATION
Normally, an Invalid Dynamic Link Call error message is the result of an incompatibility between driver versions, or a damaged or missing driver. Try uninstalling and then reinstalling any programs or components that you installed recently (before the error message occurred).

The error message stated above may occur because your computer is configured incorrectly. This may be due to a device driver that was added or removed recently.

Part 1
Part 1 may be divided into an encoded device name, object number, and offset, such as "VMM(0A) + 0000001C." This example means the problem was detected in the VMM virtual device driver, in object 0A, at offset 0000001C.


If Part 1 is an eight-character sequence of letters and numbers, such as "C13A1EC6," a device driver jumped to an invalid location. The identity of t

Collapse -

Invalid VxD Dynamic Link Call

by holt_m2 In reply to Invalid VxD Dynamic Link ...

The question was auto-closed by TechRepublic

Collapse -

Invalid VxD Dynamic Link Call

by matt_sandberg In reply to Invalid VxD Dynamic Link ...

As stated already this is probably a driver conflict. If you don't know what kind of networking card you have you will need to remove it and go to windrivers.com. This site will show you how to identify the card and where to get drivers. Hope this helps

Collapse -

Invalid VxD Dynamic Link Call

by holt_m2 In reply to Invalid VxD Dynamic Link ...

The question was auto-closed by TechRepublic

Collapse -

Invalid VxD Dynamic Link Call

by RMmcp In reply to Invalid VxD Dynamic Link ...

Open "System Properties" (press the "Windows" key and "Pause Break" together). Select the Device Manager tab. Click the + by Network Adapters. Write down the exact entry for the Network Card. Double click the NIC entry. Click the Drivers tab. SelectDriver File Details. Highlight each file and any that are not from Microsoft, write down the file name. Do a search on the computer for them and delete them. Then select the NIC in Device Manager again and remove it. Now, open Windows Explorer/Windows folder/INF folder/open Others folder. If you see an .inf file from the NIC company, delete it. Then search the manufacturer's web site, under Support, for driver's for that card. Download them. Put them on a floppy and reboot allowing Windows to redetect the card. When it calls for files, give it the floppy.

Collapse -

Invalid VxD Dynamic Link Call

by holt_m2 In reply to Invalid VxD Dynamic Link ...

The question was auto-closed by TechRepublic

Collapse -

Invalid VxD Dynamic Link Call

by dkemper314 In reply to Invalid VxD Dynamic Link ...

This is meant as the best first step. Not a complete fix, though it turns out to be the solution to similar problems 70% of the time.

An important first thing to look at is the network properties. Right click the network neighborhood icon on the desktop and go to properties. A screen should appear that has three tabs, the one showing should have a little window in it which will list devices, adapters, protocols, etc. If you are not used to looking here, some of this will just look like gibberish and it will also list the bindings of protocols to devices.

Often, there is a bunch of extra crap in here -multiple listings of drivers for the same network card, protocols that are no longer used, AOL ADAPTERS, etc.

Basically, remove everything that is not being used. For example, if the network is only TCP/IP then remove all other protocols and their bindings. Unless dependent on AOL remove all references to it. I, personally have seen a lot of problems caused by it. Once everything is a little cleane

Collapse -

Invalid VxD Dynamic Link Call

by holt_m2 In reply to Invalid VxD Dynamic Link ...

The question was auto-closed by TechRepublic

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums