//flex table opened by JP

Click to See Complete Forum and Search --> : "Blue screen of death" when modem connects


DMan
08-05-1999, 05:50 PM
Anyone else have this problem. I'll dial in to my ISP, it'll chirp and beep, and right after it does this I get the big "blue screen of death", hit a key, and the modem disconnects. After I reboot though I can connect okay, but if I leave my system idle for a while or if I've been using it for a while it tends to do this (among other things).

MrEd
08-05-1999, 06:19 PM
Can you tell us what your system has in it? Is this Win95 or 98? We need more info please. If it's Win98, make sure you have VCOMM.VXD in your C:\Windows\System folder. Also make sure you have the latest drivers for your modem or any patches the manufacturer offers.

DMan
08-05-1999, 11:16 PM
Ooops, hehe. I have an AMD K6-2 300MHz, 64MB, Win98, Voodoo2, SII220 video card, 8.4 Western Digital, ActionTec 56k.
I looked for this VCOMM.VXD and didn't find it anywhere, but my system has been working fine up until recently. I have a feeling it might have something to do with installing ICQ so I uninstalled it for now.
BTW, where do I get VCOMM.VXD and what does it do exactly?
Thx.

MrEd
08-06-1999, 12:10 AM
Awhile back, I found out that Win98 doesn't install 7 specific drivers, and I posted them here. One of them is VCOMM.VXD, and another one is NTKERN.VXD. They are both on the Win98 CD. If I remember, they are in CAB 25 or 24. Just do a search for them on the CD, and right click on them and extract to C:\Windows\System folder then restart. Windows needs certain drivers to run programs and hardware. Since these don't install with windows, it forces your computer to use old drivers. If you look in your device manager, and select "modem", and Properties, then driver details, you should see what drivers windows is using for your modem. If you see something in parenthesis next to it, that is the one windows wants to use, but can't find. That's why it has to be manually extracted to your system folder. Not sure on how the driver works, but I know it is needed.



[This message has been edited by MrEd (edited 08-06-99).]

philipg
08-06-1999, 10:13 AM
Here's a better way open your 'device manager' in system properties.
open each installed devices properties one at a time and check for a driver name like this (vcomm.vxd) if you find one.

Click start>> run
type SFC <return>
extract one file, the file in () place in c:\windows\system\
leave both screens up (device manager and SFC) and click back and forth between them.

In device manager after you extract the file close the devices properties and then reopen it to see if the devices driver is still in perenthesis, if not move to next device until your done, rebooting is not necessary after your done extracting.

These steps should only take you about 10 minutes to complete, it's very easy to do.