Slow internet after Hamachi download

[Firiender]

So this has happened most of the times i'v downloaded hamachi, that after 3 weeks or so my net starts to slow down totaly random. I can play fine for 1 hour or so and then my network starts going crazy with over 7000 ping on bf3 and dota 2.

This has exactly happend before when i downloaded hamachi, but i tought since i got a new computer that wont be the case this time. But again after 2-3 weeks my network started to slow down on random. I re-formated my PC, and tried everything to reset my network settings, but it is still slow and laggy.

Sorry for my bad english, its not my first laungage.

And i would REALLY appriciate of someone could help me, because most games are unplayable, and i'v had this problem for like 2 years or something.

EDIT: Here's the ipconfig


Windows IP-konfigurasjon


Ethernet-kort Lokal tilkobling:

Tilkoblingsspesifikt DNS-suffiks : lan
Koblingslokal IPv6-adresse. . . . : fe80::313a:c82d:a5eb:4fac%11
IPv4-adresse. . . . . . . . . . . : 10.0.0.187
Nettverksmaske . . . . . . . . . .: 255.255.255.0
Standard gateway . . . . . . . . .: 10.0.0.1

Tunnelkort isatap.lan:

Medietilstand . . . . . . . . . . : Medium frakoblet
Tilkoblingsspesifikt DNS-suffiks : lan

Tunnelkort Teredo Tunneling Pseudo-Interface:

Tilkoblingsspesifikt DNS-suffiks :
IPv6-adresse. . . . . . . . . . . : 2001:0:5ef5:79fb:4f9:293:f5ff:ff44
Koblingslokal IPv6-adresse. . . . : fe80::4f9:293:f5ff:ff44%13
Standard gateway . . . . . . . . .: ::

C:\Users\Kristian Dønnestad>

 

[Firiender]

Dont know if this means anything to you guys, but i took this from the router website.

FIREWALL exact tcp state check (1 of 4): Protocol: TCP Src ip: 69.63.190.71 Src port: 443 Dst ip: 80.202.153.41 Dst port: 54751


Jun 17 23:47:25 SNTP Synchronised again to server: 80.202.5.3


Jun 17 23:47:24 FIREWALL replay check (1 of 10): Protocol: ICMP Src ip: 152.63.51.38 Dst ip: 80.202.153.41 Type: Time Exceeded Code: Time to Live exceeded in Transit


Jun 17 23:46:00 FIREWALL exact tcp state check (1 of 18): Protocol: TCP Src ip: 66.220.146.100 Src port: 443 Dst ip: 80.202.153.41 Dst port: 54196


Jun 17 23:44:47 LOGIN User 39609B logged in on [HTTP] (from 80.202.153.41)


Jun 17 23:44:45 FIREWALL exact tcp state check (1 of 10): Protocol: TCP Src ip: 69.63.190.71 Src port: 443 Dst ip: 80.202.153.41 Dst port: 64329


Jun 17 23:44:21 FIREWALL replay check (1 of 2): Protocol: TCP Src ip: 173.194.32.4 Src port: 443 Dst ip: 80.202.153.41 Dst port: 58573


Jun 17 23:43:36 FIREWALL exact tcp state check (1 of 10): Protocol: TCP Src ip: 69.171.228.75 Src port: 443 Dst ip: 80.202.153.41 Dst port: 62603


Jun 17 23:42:11 FIREWALL exact tcp state check (1 of 3): Protocol: TCP Src ip: 69.63.189.74 Src port: 80 Dst ip: 80.202.153.41 Dst port: 54944


Jun 17 23:40:31 FIREWALL exact tcp state check (1 of 5): Protocol: TCP Src ip: 141.0.168.7 Src port: 80 Dst ip: 80.202.153.41 Dst port: 61579


Jun 17 23:40:14 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 212.111.3.40 Dst ip: 80.202.153.41 Type: Destination Unreachable Code: Host Unreacheable


Jun 17 23:39:30 FIREWALL exact tcp state check (1 of 3): Protocol: TCP Src ip: 69.171.242.74 Src port: 80 Dst ip: 80.202.153.41 Dst port: 60161


Jun 17 23:38:01 FIREWALL exact tcp state check (1 of 7): Protocol: TCP Src ip: 66.220.158.71 Src port: 80 Dst ip: 80.202.153.41 Dst port: 62396


Jun 17 23:37:15 FIREWALL replay check (1 of 7): Protocol: TCP Src ip: 81.19.238.61 Src port: 80 Dst ip: 80.202.153.41 Dst port: 51747


Jun 17 23:35:34 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 212.182.98.112 Dst ip: 80.202.153.41 Type: Destination Unreachable Code: Host Unreacheable


Jun 17 23:35:03 FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 71.100.184.236 Dst ip: 80.202.153.41 Type: Destination Unreachable Code: Port Unreacheable


Jun 17 23:34:31 FIREWALL exact tcp state check (1 of 3): Protocol: TCP Src ip: 66.220.146.107 Src port: 443 Dst ip: 80.202.153.41 Dst port: 60091


Jun 17 23:33:45 FIREWALL replay check (1 of 2): Protocol: TCP Src ip: 81.19.238.61 Src port: 80 Dst ip: 80.202.153.41 Dst port: 57243


Jun 17 23:33:03 FIREWALL exact tcp state check (1 of 18): Protocol: TCP Src ip: 10.0.0.194 Src port: 61416 Dst ip: 77.75.73.215 Dst port: 80


Jun 17 23:32:25 SNTP Synchronised again to server: 80.202.5.3


Jun 17 23:32:01 FIREWALL exact tcp state check (1 of 51): Protocol: TCP Src ip: 10.0.0.193 Src port: 51385 Dst ip: 88.87.58.130 Dst port: 80


Jun 17 23:30:57 FIREWALL exact tcp state check (1 of 2): Protocol: TCP Src ip: 10.0.0.193 Src port: 51385 Dst ip: 88.87.58.130 Dst port: 80


Jun 17 23:29:53 FIREWALL exact tcp state check (1 of 2): Protocol: TCP Src ip: 10.0.0.193 Src port: 51385 Dst ip: 88.87.58.130 Dst port: 80


Jun 17 23:28:50 FIREWALL replay check (1 of 6): Protocol: ICMP Src ip: 212.111.3.40 Dst ip: 80.202.153.41 Type: Destination Unreachable Code: Host Unreacheable

It says destination unreachable for a while, and i think it says that the period the network is slow, because at 23:40, thats the last time my network was slow and it stopped, and so did the Destination unreachable code: Host unreacheable

BTW, this is the traffic from the event log for the router.

 

[Firiender]

No one have a clue?

 

[chev65]

No one have a clue?

All I can tell you is that Hamachi or pretty much any secondary network can cause connection problems in Windows 7.

I've had three people who had to uninstall Hamachi the last three weeks and in their case they could not get a working connection at all if Hamachi was installed.