Are you using any shell extensions which talk to the network? e.g. Cloud storage or source control tools that integrate with Opus or the Windows shell (icons, context menus, etc.)?
It's possible they have a bug where they are uninitialising the WinSock API more times than they initialise it, which could leave WinSock in an invalid state for everything else sharing the dopus.exe process.
You can use ShellExView to see which shell extensions are on your system and try disabling them. (fully exit Opus (via File / Exit Directory Opus) after making any changes, since extensions which are already loaded won't always be unloaded until the process exits.)
There are other possibilities as well, but that's one which might explain why you're seeing this but others haven't reported it. It's also possible there's something unique about the site or some action you're doing which is triggering a bug in our code.