We have seen this a few times now. Check your debug.log for windows socket errors. When they occur they sometimes leak memory and can make the client function in unpredictable ways... It's completely unrelated to Swipp and is Windows-specific. Restarting the node might fix it if the socket errors do not occur in the same place again.

If you do some google-fu there are some fixes available when these errors occur.

Yours, team swipp