Random Explorer crashes in 95 OSR2.1 - Memory location : &bff9a3c0

[bassinvader]

Got a real humdinger of a problem.
Recently rebuilt my Windows 95 OSR2.1 system - Heavily loaded with apps.
Explorer (systray) randomly crashes but will usually auto-restart ok and I can continue in whatever app I'm using.
Here is a dump of the faultlog.txt

Date 10/11/2000 Time 00:29
EXPLORER caused an invalid page fault in
module KERNEL32.DLL at 0137:bff9a3c0.
Registers:
EAX=0078facc CS=0137 EIP=bff9a3c0 EFLGS=00000246
EBX=bff79895 SS=013f ESP=0078fac8 EBP=0078fb1c
ECX=00c02750 DS=013f ESI=78037118 FS=2cb7
EDX=00000000 ES=013f EDI=00000000 GS=0000
Bytes at CS:EIP:
5e 8b e5 5d c2 10 00 64 a1 00 00 00 00 55 8b ec
Stack dump:
78037118 c0000005 00000000 00000000 bff9a3c0 00000000 c71b2014 bff78028 816c7050 00000000 bff7928f 816e34c0 816c7000 c71b2014 816e45d8 816c7000
Its the same memory location (bff9a3c0) every time - I've checked the memory at this location and it would seems to be web / ppp related

Also when dialupnetworking connectoid is selected and ISP is dialed and connected I get another error message box - Here is the fault log entry.

Date 10/11/2000 Time 00:11
RUNDLL32 caused an invalid page fault in
module KERNEL32.DLL at 0137:bff9a3c0.
Registers:
EAX=0063fa78 CS=0137 EIP=bff9a3c0 EFLGS=00000246
EBX=bff79895 SS=013f ESP=0063fa74 EBP=0063fac8
ECX=00aa2750 DS=013f ESI=78037118 FS=19d7
EDX=00000000 ES=013f EDI=00000000 GS=0000
Bytes at CS:EIP:
5e 8b e5 5d c2 10 00 64 a1 00 00 00 00 55 8b ec
Stack dump:
78037118 c0000005 00000000 00000000 bff9a3c0 00000000 c71b1b84 bff78028 816c7050 00000000 bff7928f 816ef604 816c7000 c71b1b84 816eebfc 816c7000
************************************************** ********************
This would seem to confirm the web /ppp / tcp/ip related as its also the same memory location - Question is why would it affect explorer???
Have removed completely and reinstalled DUN , TCP/IP , all Network config options.
I am also running DUN1.3 upgrade for VPN.
Checked all Microsoft problem resolutions and applied to no effect - No surprise there then!!!
Its not my hardware - I initially suspected memory but a second HDU with a fresh copy of 95 doesn't exhibit the same problem.
All Win95 and IE5 updates and patches are installed.
Also reinstalled win95 over the top on a ghosted copy of this drive - No result.
If anyone can shed some light before I start delving into the registry or selectively replacing system DLL's and .EXE FILES from my known good install it would be gratefully appreciated.
Sorry this is so long winded but the more info the better no???

[BFlurie]

Here's some starters:
http://www.windowstrouble.com/kernel32dll.shtml
http://www.jenntel.com/tech/Win95/gtshoot.htm

[bassinvader]

Well it was a long weekend but I've managed to sort the problem by selectively replacing vxd , dll , 386 and other system files from
a fresh install of WIN95 to different directory (Helps no end with NT) and works just as well with Win95 . restore backup , replace files , restore backup etc....etc...etc...I use PQMAGICV3.0 - Its an absolute lifesaver and I've never had problems in restoring WIN95/98 with it.
It doesnt work with NT however - even with smartsector off.

Turns out the problem was with two corrupt files in the Windows\System directory and a corrupt registry entry:
WSHTCP.VXD
WSOCK.VXD
Although this solved both my problems I still couldn't see the services in network control panel.
In the end the full solution - Thanks to Scott McNiven - A fellow MCSE and all round good guy has this clean fix for most TCP/IP network related problems. This relates to WIN95 OSR2.x only as these are the main machines we both support on the companies NT network.

Remove all network components in control panel.
Remove Dial Up Networking
Remove Modem INF's in C:\WINDOWS\SYSTEM\INF\OTHER
Remove winsock.dll , wsock32.dll , wsock.vxd , wshtcp.vxd , mstcp.dll , mswsock.dll

Using REGEDIT remove the following keys under
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVIC ES\
1 ) winsock
2 ) winsock2 <If you've updated>

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVIC ES\VXD\
1 ) dhcp
2 ).mstcp
3 ) nwredir

(Sometimes if the above fix isn't totally successful you may need to remove the following files also:
vtdi.386 , vtcp.386 , vip.386 , vudp.386 . vdhcp.386 , vnbt.386)

Now reboot and reinstall the network card and modem when detected by plug and play.
Reinstall all protocols used & Preferred client - Microsoft client for networks (Needed if ye want to save yer DUN passwords)
Reinstall Dial Up Networking and DUN13 (Necessary for VPN and ISDN - If you Use it)
Apply winsock version 2 update.
Reboot and hey presto - A working system with no errors!!!

Hope this helps anyone else with networking-dun-rundll32 related problems!!!

One final point - Attempted to install Windows Millenium over my newly repaired system - it keeps rebooting
during pnp detection - Think its the network card causing the problem. After the weekend I've had I think I'll
give the Millenium upgrade the dizzy - We've had no successful installs at work with Millenium over either Win98 or Win95.
Anyone else had problems with Millenium upgrades??? By the looks of the upgrade it's not worth the effort!!!

Many thanks to Bflurie for the url's - The Trouble With Windows is a most excellent site - I've certainly learned a few new twists this weekend!!!

[BFlurie]

Good troubleshooting work!

[bassinvader]

Thanks mister Flurie.
Hope yer not in a hurry!!! >;O)
One good URL deserves anither ye ken???
I hail from the misty highlands of Bonny Scotland if yev not sussed the lingo by now!!!

Check this rather excellent site:
http://www.generation.net/~hleboeuf/errkrn32.htm

PS. Anyone know where I can get drivers for a GDI Rendition v2200 Agp 8Mb graphics card.
Got some uncertified beta ones for 95/98 and they work a dream but am stuck running my NT server in VGA mode without the right NTV4.0 drivers???

[BFlurie]

W/NT you always want to try to use a driver off the installation CD IF possible. Granted, it's probably not going to have something that'll work for newer cards. NT is harder to satisfy concerning drivers. The manufacturer's site doesn't have an NT version of the driver?

[bassinvader]

Thanks B - As you know NT's driver set is somewhat limiting - Managed to get the latest drivers from an obscure drivers site after much late night oil burning. Thanks to Eumir Cabatino -www.eumir.com - What would we do without the net.

NT server is now humming along in 1024x768
Makes administering Exchange , SQL , SMS and
Lotus Notes somewhat easier...Whats the smiley for understatement now!!!........>;O)