Explorer error(ws2_32.dll related)

[mountainman]

I have had my internet go completely down and no option of release/renew to fix it. A PC restart takes care of the issue but it comes back at a random time.

I looked in the logs and found this...

Faulting application explorer.exe, version 6.0.2900.5512, faulting module ws2_32.dll, version 5.1.2600.5512, fault address 0x00006a55.

I looked up the DLL and found this...

File that contains the Windows Sockets API used by most Internet and network applications to handle network connections.

http://www.processlibrary.com/directory/files/ws2_32/

It seems that it handles the sockets for internet which would explain why I get no net. Any know how to replace/fix this DLL? I've not much experience with DLL's.

Thanks!

[Sava700]

winsock repair wouldn't hurt.. then might want to boot from the OS disk and do a repair with the chkdsk /r

Otherwise the main thing that would screw up a winsock dll would be malware or spyware of some sorts.

[mountainman]

Thanks, sava. I'll give it a go tonight and report back. I guess it isn't as easy as getting a new DLL, dropping it in the folder and rebooting, eh?

Dangit.

[YeOldeStonecat]

Can you find this .DLL in win explorer? Should be inside your Windows\System32 directory.

A cure in the past was to uninstall/reinstall the TCP/IP protocol.
Try this TCP/Winsock repair utility
http://www.snapfiles.com/reviews/WinSock_XP_Fix/winsockxpfix.html

Which OS?

[mountainman]

Yes, I found it last night and ran AV on it. No virus there. I'll try that link when I get home.

Windows XP Pro SP2. (Installed and removed SP3 when I started getting another error that I'm getting with my memory card reader I've used for YEARS. Still getting the errors. Ugh.)

[mountainman]

Ran the software earlier tonight and we'll see how she works.

After my internet "died" earlier, I ran the software and rebooted. It didn't give me the "explorer.exe error" that I got the other times.

Things are looking up! Thanks.

[mountainman]

Well, it died again but I didn't get the explorer.exe error after the reboot.

I guess they aren't related. *sigh*