Question Massive Lag Spikes since 2 weeks

[Keesekuchen]

About two weeks ago I started noticing huge lag spikes while playing tf2. I've tried cable connection instead of wifi but the problem was still there and since my pc is the only one in this house with this problem i assume it's a hardware problem.
Things I've tried out that didn't work:
deactivating WLAN AutoConfig
turning off location
disabling updates from other pc's
updating drivers
reinstalling drivers

Here are the clearly visible lag spikes in the cmd field (sorry for german):
Antwort von 172.217.19.67: Bytes=32 Zeit=22ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=5ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=9ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=4ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=6ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=2432ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=4ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=4ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=5ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=5ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=4ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=4ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=2539ms TTL=55
Antwort von 172.217.19.67: Bytes=32 Zeit=3ms TTL=55

Did anybody else experience lag spikes like this and if yes do you know how to fix it?

 

[viveknayyar007]

Hello

Can you please check if your network cable is not too close to any power cable, and in case of wireless network, your router and/or your PC are not too close to any high magnetic field such as disassembled speakers or something like that?

You may also want to check if it's the graphics driver that is the main culprit. If it's not, you can try rolling back your NIC driver to one of its previous versions and see if it does the trick.

Cheers!!