Problem with Winsock DLL ?

Discussion in 'other software & services' started by dja2k, Jan 17, 2006.

Thread Status:
Not open for further replies.
  1. dja2k

    dja2k Registered Member

    Joined:
    Feb 15, 2005
    Posts:
    2,040
    Location:
    South Texas, USA
    Has anyone encountered a problem with ws2_32.dll and if so, how did you fix it. I have been having that problem with Firefox and then breaks some other interent accessing programs. All it says is that a error accoured and can't access memory at some address. I have Nod32, Online Armor, Safensec (no network protection), Look'n'Stop, Ewido 3.5, RegRun Gold 4.50 and Spyware Doctor 3.5 active. I am thinking its more towards Look'n'stop, Nod32, or Online Armor causing that since Look'n'Stop has the DLL plugin, Nod32 has the IMON, and Online Armor has the HTTP scanner. Any help ?

    dja2k
     
  2. Mrkvonic

    Mrkvonic Linux Systems Expert

    Joined:
    May 9, 2005
    Posts:
    8,696
    Hi,
    If I remember correctly, there's the Winsock and guidelines in Blackspear's general cleaning guide.
    Mrk
     
  3. dja2k

    dja2k Registered Member

    Joined:
    Feb 15, 2005
    Posts:
    2,040
    Location:
    South Texas, USA
    Thanks but that was only for using the winsock fix tool to fix broken internet which I don't have. After the error, I can still use internet explorer, opera, and maxthon, but not firefox. I am still trying to find out what is causing it. I think it might be firefox somehow but not sure cause no other program has cause that error except firefox as show in my event viewer. Does anyone know if my problem has anything to do with nod32's IMON and the compatibility options of client compatibility?

    dja2k
     
    Last edited: Jan 17, 2006
  4. dja2k

    dja2k Registered Member

    Joined:
    Feb 15, 2005
    Posts:
    2,040
    Location:
    South Texas, USA
    Well cleaned my system out and have a fresh install once more. No problems anymore.

    dja2k
     
    Last edited: Jan 19, 2006
Loading...
Thread Status:
Not open for further replies.