Winsock won't stop getting corrupted

[Kibōchen]

I've been having this issue since late of March. For some strange reason, Winsock gets corrupted out of nowhere, sending my connection to the Internet haywire. This wouldn't happen all that much, but soon it began occurring every week.

Even resetting Winsock via command prompt doesn't help. Sure, after restarting, my computer would be A-OK, but after a week, Winsock gets corrupted again!

Is there anything I could do to fix it?

I have a Windows 7 Home Premium computer.

[Mid-Forever]

What is the actual error message tying it to winsock? To be blunt, what's giving the impression it's winsock related at all? Not possible it's a DNS issue or LAN side modem/router based?

If you restart without the CMD>winsock reset, does it (however temporarily) fix it still?

Also, update and run anti-virus recently?

Nother, run ipconfig /all while it's working and copy&paste/screenie it, then next time it cuts out, ipconfig /all again to compare. Probably won't show too much, but worth a try in case something obvious.

[M.A.F.I.A Cannoli]

Originally posted by Teslahaha:

I've been having this issue since late of March. For some strange reason, Winsock gets corrupted out of nowhere, sending my connection to the Internet haywire. This wouldn't happen all that much, but soon it began occurring every week.

Even resetting Winsock via command prompt doesn't help. Sure, after restarting, my computer would be A-OK, but after a week, Winsock gets corrupted again!

Is there anything I could do to fix it?

I have a Windows 7 Home Premium computer.

Winsock whew havent touched that since win 98

Anyways yeah your rig has aids.....

[_I_]

best bet is to reinstall windows

backup all important info and format and install the os again

[M.A.F.I.A Cannoli]

Originally posted by _I_:

best bet is to reinstall windows

backup all important info and format and install the os again

Yes but nuke first. It would beating dead horse, infection will be a never ending reincarnation

[Kibōchen]

Originally posted by Mid-Forever:

What is the actual error message tying it to winsock? To be blunt, what's giving the impression it's winsock related at all? Not possible it's a DNS issue or LAN side modem/router based?

If you restart without the CMD>winsock reset, does it (however temporarily) fix it still?

Also, update and run anti-virus recently?

Nother, run ipconfig /all while it's working and copy&paste/screenie it, then next time it cuts out, ipconfig /all again to compare. Probably won't show too much, but worth a try in case something obvious.

Winsock just stops working as I work on the computer every 8 days or so. Resetting it and restarting Windows does work, but it just gets corrupted again 8 days later.