I suspect this may be related to the Killer Network Manager. Could you try disabling it and see if the issue persists?