This might be a shot in the dark, but I had this exact same problem a while ago. The cause for this was a running hyper-v vm I never turned off.