"Invalid VxD dynamic link call from VMIN32(05)+0000119E to device "0002", service 1

[crazzmf]

Does anyone know how to fix this. My CPU keeps shutting down when this comes up. It happens while i am using IE 5.5. Please Help.
"Invalid VxD dynamic link call from VMIN32(05)+0000119E to device "0002", service 1. Your windows config is invalid. Run the windows set up program again to correct this problem". How and what do I need to do? I am running Windows 98 with IE 5.5. Please tell me what this message means and what I can do.

[Richard_Cranium72]

All the results at MS varied in Resolution.

I'd try a fresh format/install if no one else has any suggestions..

DrVette

[bighogjeep]

I had similar problems and went into Microsoft Technichal chat room and asked whats up and it was my modem. He said vxd is a modem problem and to update my drivers and if i couldnt update them to get a new modem and i did i got a winmodem and have never had a problem since old modem was a rockwell chipset.

[Richard_Cranium72]

VXD's are virtural device drivers

What we need to know is what "Device 002" is to resolve this issue.

I searched at MS for a while using several variations of the error message including a c&p of the whole thing, no dice..

[socalgal]

If I remember correctly, in Win95/98, the VxD, VWIN32.VXD supports the input/output control functions of the virtual device driver being accessed...

You might try running SFC to check for system files corruption; if that doesn't work, I'd try a reinstall (run setup.exe, not reformat) to see if it fixes the corruption.

Good luck!




[This message has been edited by socalgal (edited 05-25-2001).]

[Michael Chiew]

Crazzmf

Reminds me of a recent episode of Providence (in Singapore). This father (a vet by profession) is having an argument with family members (about sins of the past). He has a parrot with him. He turns to the parrot and said, "I'm sure you've got something to say, too. So say it." Guess what the parrot replied.

"You suck," the parrot bit back.

Memory, memory sucks! It causes us to spin in a daze, sends us on a wild goose chase at times and occasionally subverts our good intentions.

Invalid vxds, dlls, general protection faults, fatal exception errors all tend to be the work of physical memory - ram.

The figure "0002" is, I understand, part of a segment-offset addressing system that uses 2 4-digit numbers to come up with a single 5-digit number which results in 20-bit addressing in PCs. It's a mindboggling exercise, a beast I am determined to conquer over time.

Anyway, what I'm trying to say is this. VWin32.vxd has invaded an address in memory it has no business getting into. In so doing, it has caused a system shutdown. The system won't work until the alien presence is expelled.

Since your problem revolves around the use of IE5.5, it could well be the instigator of the system crash.

By the way, socalgal, thanks for the little insight on VMin32.vxd. I hadn't heard or read about this item until now. Of course, I went straight into my subservient machine to check it out. I did a search of the entire directory, subdirectories, every nook and corner. I couldn't find VMin32.vxd. I'll check cabinet files later.

Let's do a spot of deductive reasoning here. The error message itself provides an interesting clue to the behavior of physical memory.

"Invalid VxD dynamic link call from VMIN32(05)+0000119E to device "0002", service 1. Your windows config is invalid. Run the windows set up program again to correct this problem".

VMin32 has made an invalid move. Device "0002", service 1, (indicative of defective ram); "Your windows config is invalid (environment variables have changed). Hence the suggestion to Run the Windows set up program to correct this problem. But how could environment variables have changed (the OS determines environment variables upon OS installation), unless you have a virus infection or defective ram. Or there is a third possibility, a more worthy opponent - a malfunctioning CPU.

Crazzmf, I suspect there is foul play afoot. The main villain of the piece could be psychotic ram, throwing a smokescreen to befuddle us.

The way I see it, you have 3 choices.

Reinstall IE5.5.

Do the socalgal bit. Reinstall your OS. If it's just a matter of alien invasion of private space or file corruption, a reinstallation will end your pain.

If it doesn't, make a bold move no other has suggested. Check your ram. Make sure it is sitting properly. Change DIMM slots. See how it goes. If you have a stick of known good ram, switch it. It may be the next best thing you do.

Have fun!

Michael Chiew

[Michael Chiew]

Crazzmf

This is the kind of arithmetic I like. Crunching numbers - VMIN32(05)+0000119E to device "0002", service 1.

0000119E (is part of a memory address range 00000000:0009FFFF for System Board Extension for ACPI BIOS in my computer) to device "0002" (0002 is within the I/O address range 0000:000F, one of the address ranges for the DMA Controller in my computer). Service 1, like all its other Service nn deviants, is supposed to indicate ram involvement of one kind or another. Could be psychotic ram (dysfunctional), could be just plain alien invasion of private space. But the tilt is towards defective ram.

All right. This is a strictly personal conclusion, may sound stupid, illogical or just a plain mindless exercise of grey matter. But love me or hate me, just don't shoot me down for trying.

VWin32.vxd has boldly gone where no other vxds have gone. First, it lands on 0000119E (System Board Extension for ACPI BIOS), gets itself kicked out and touchdowns on 0002 (DMA Controller). No can do. The system shuts down. It wouldn't want to be a part of the madness created by Ram. VWin32.vxd didn't have a choice of location, psychotic ram indiscriminately throws it in the middle of unfriendly territory.

Crazzmf, I conclude (strictly personal) that you've got bad, bad ram!

Thanks to socalgal and you, I'm now acquainted with VMin32.Vxd, a vxd that supports the I/O control functions of the vxd being accessed.

The one thing that puzzles me is VWin32.vxd. I can't find it in my system (running OS Win98SE).

Hey, socalgal, help me out here. Where is VWin32.vxd. Location, please. I found VWin32.vxd (60,641 bytes) nestled in the cabinet files, more precisely in Win98_54.cab but not in the "active" list of vxds. How come! I must find out! It's become an itch I can't scratch.

I shall continue investigations with a giant magnifying glass.

Michael Chiew

[Richard_Cranium72]

MicroSoft has NO records in the serch for VMIN32, are we getting jerked around here ?

[Michael Chiew]

Socalgal

I've struck gold; I've found the elusive Mr VWIN32.VXD. A combination of machine/textbook research did the trick.

You're right about its function, it's a Win32 support driver. The textbook research reveals that rather than have an endless entourage of vxds in the background (there are more than 6,000 -Win98SE- system files of one sort or another, vxds, dlls, etc, etc., working at the back of the house to ensure a well-run machine), some of them were chosen to reside inside Virtual Memory Manager (that's why I couldn't find VWIN32.vxd). Virtual Memory Manager is host to 43 vxds in my machine running Windows 98SE. VWIN32.vxd is one of them. VMM32.vxd, which creates virtual machines, initiates the loading of the 43 vxds.

An item flashed through my mind - VMM32. I'd seen it somewhere but where! I ransacked the bowels of my machine, went into System Tools, System Configuration Utility. No luck. Then it came to me - the Registry. I ran REGEDIT. Wow! Six hot keys, terribly long hot keys. I got to work and I found the link to it.

Registry Key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\VMM32Files

reveals all. The dirty little rat is in the Registry.

At last, I've scratched the itch.

Crazzmf, sorry for making your adversity the playground of my whims.

Right now, it's night in Singapore. Guess I'll power down and sneak up to slumberland in silk sheets.

Good night, everybody!

Michael Chiew

[Andy_L]

Wow Michael, you make my head hurt :-) Your point about memory is well taken tho.

[socalgal]

Hey Michael http://www.sysopt.com/forum/smile.gif

Just for fun I did more research on VWIN32. More info:
http://msdn.microsoft.com/library/psdk/win95/devio_2b1v.htm

http://msdn.microsoft.com/library/psdk/win95/excluse_92ib.htm

32-bit Windows-based applications must call the exclusive volume-locking IOCTL functions indirectly by opening VWIN32.VXD and using its DeviceIoControl interface.

In response, VWIN32.VXD issues the low-level disk I/O functions (Interrupt 13h, Interrupt 25h, and Interrupt 26h) as well as the MS-DOS Interrupt 21h file handle read, write, seek, and IOCTL functions in the context of the calling process.


BUT... I think I / we are confusing VMIN32 with VWIN32 here? crazzmf's error said VMIN32 - correct crazzmf? Sorry if I led off-track on the real problem.. and Michael, I'm in rush here, so I'll read your posts more thoroughly later to study the correlation between the two..

Like Doc, I quick MS search has produced no results.

crazzmf - Has anything worked? Some feedback??


[This message has been edited by socalgal (edited 05-30-2001).]

[Michael Chiew]

Socalgal

You cared. You finally crawled out of the woodwork to make an appearance on my behalf. You're human after all (used to wonder about that). The 2 links will be explored bit by bit, dissected, digested and embraced.

My heart's pumping real fast, my mind agog with dreams of yet greater discoveries. There are wonders, nuggets and gems still to be unearthed on an island called Windows 98.

And I thought I was sneaking up to slumberland in the embrace of silk sheets.

Life is full of surprises. Sysopt.com is certainly one of them.

Michael Chiew

[crazzmf]

Thanks for all the help everyone, I have been away on business since I posted this topic. I re installed IE and the problem has gone away. I am sorry that I could not respond sooner, thanks again.