Computer Disconnecting And Reconnecting Often

TheFinisher0

Reputable
Sep 16, 2014
14
0
4,510
Practically the title, its been getting much worse and it used to be prominent only when I had played games so I guessed that with high load came the discconections, it was infuriating though, expecially in the middle of a game. I had uninstalled Hamachi, VMWare and Hotspot shield because they were the only other adapters I had and since then it has only gotten worse. If all goes wrong, I have no qualms with backing and reformatting my HDD, but I fear that the backup will take the issue with it.

Extra Info
Overclocked I5-3570k
GTX 960 4gb
8 GB Ram
MSI Z77A-G45
Never had this issue before
Only my computer
There are many other devices on this network

It used to only happen under high load, for example a league of legends game but now it happens randomly, while surfing the web

If buying an NIC could be avoided it would be much appreciated

EDIT:
I ran a ping -t in cmd to 8.8.8.8 and this was the result
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56 ---->Started League Of Legends Game
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
General failure. ----> First Crash
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=7ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=6ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=26ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=5ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56 -----> Second Crash
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Request timed out.
Reply from 192.168.2.20: Destination host unreachable.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=8ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=7ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=3ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56
Reply from 8.8.8.8: bytes=32 time=4ms TTL=56

I started a league of legends game, let it run and this is what happened.
Thanks for all the answers!
 
Solution
run ipconfig and find the IP address of your default gateway.
run the same ping test but instead of pinging 8.8.8.8 ping the gateway.
let us know the results, no need to paste the entire thing, just the statistics at the end.

gbb0330

Reputable
Apr 28, 2015
1,498
0
5,960
run ipconfig and find the IP address of your default gateway.
run the same ping test but instead of pinging 8.8.8.8 ping the gateway.
let us know the results, no need to paste the entire thing, just the statistics at the end.
 
Solution

TheFinisher0

Reputable
Sep 16, 2014
14
0
4,510


I dont know what you mean but I ran ping -t to my default gateway but it didn't give me results at the end, it just kept on going. When it crashed it said
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Request timed out.
Request timed out.
and then when it came back it just continued pinging.
 

gbb0330

Reputable
Apr 28, 2015
1,498
0
5,960



i forgot to tell you to press Ctrl+C to interrupt the ping test.
anyways, looks like the problem is on your internal network. could be your NIC, your cable, or your gateway.
try pinging the gateway from another computer to narrow it down. if other devices on your network can ping the gateway with no issues then the problem is with your computer. if all computers on the network have issues with the gateway then the problem is with the gateway. the gateway is your router, if you don't have a router, then its your modem.

 

TheFinisher0

Reputable
Sep 16, 2014
14
0
4,510


Well what do i do if its my computer only? I have already updated drivers, and I can check the wire right now.
 

gbb0330

Reputable
Apr 28, 2015
1,498
0
5,960


NICs are pretty cheap, you can buy one to test with and keep it as a spare or return it if it turns out that its not the problem.
 

TheFinisher0

Reputable
Sep 16, 2014
14
0
4,510


Lets say I can't get one right now, are there any programs or the such that I can use to troubleshoot?
 
When it is random like this is tends to be hardware issues. The standard other causes are firewall & virtual machine configurations. These though tend to completely break not randomly. Still virtual machines and vpn may leave crap installed that is not easy to see.

You can try things like disabling IPv6 and turning off any of the offload features in the nic. You should not have to but both can cause strange issues with the nic.

You could also ping 127.0.0.1. Generally if this works but the others do not it points more to a hardware failure but since hardware failures cause strange results you never really know.

I will have hoped you have tried a different lan cable, but that most times give you a different error.