Maybe a temporary DNS issue caused the spike. A quick DNS purge might resolve it.
Maybe a temporary DNS issue caused the spike. A quick DNS purge might resolve it.
Hi, I see you've been dealing with a persistent problem for a while. From what you describe, it looks like your friend's computer experiences brief ping spikes that disrupt games and programs. Temporary solutions include clearing the DNS and restarting the machine, which temporarily resolves the issue for a few hours before it returns. We believe this isn't related to a firewall problem. The issue doesn’t affect other devices in the house (300 Mbps connection) or other games like CS:GO, Apex, Overwatch, or Discord—only certain titles seem affected. Some users suspect a clock-related sync issue or even lag-switching behavior, though games from the source engine run normally. We think a corrupted Windows file might be involved, but no malware has been detected during scans. Running commands like "dism.exe /online /cleanup-image /restorehealth" and "sfc /scannow" also seems to help. I hope these suggestions provide some clarity and a short-term fix. Thanks for reaching out!
If the scan resolves the problem briefly, it indicates a damaged Windows file is likely the cause. At least that should be the case. Unless you're certain it's not a malware infection, consider performing a full Windows reinstall and backing up vital data to the cloud.
A couple troubleshooting steps to rule out total connectivity loss and DNS issues: When you're waiting for the issue to occur, open three separate command prompts. In the first, run "ping 8.8.8.8 -t" in the second do the same except to your router (ex. ping 192.168.1.1 -t) and in the third do it to a different machine on your network (ex. ping 192.168.1.50 -t, where that's a device that actually responds to ping requests). You can leave all three windows in the background and go about your business. When the issue occurs, pop them back open and share the results. If there's a change in any of them, we can greatly narrow down the problem. Secondly, when the issue occurs, open another command prompt and run "nslookup google.com". Post the full results. I've redacted mine because I doubt there's anyone else in the world with the same DNS server address, and I don't want my employer to have evidence that I'm browsing the Internet on the clock. C:\Users\(redacted)>nslookup google.com Server: (redacted) Address: (redacted) Non-authoritative answer: Name: google.com Addresses: 2607:f8b0:4002:c2c::71 2607:f8b0:4002:c2c::8b 2607:f8b0:4002:c2c::8a 2607:f8b0:4002:c2c::66 108.177.122.101 108.177.122.139 108.177.122.100 108.177.122.102 108.177.122.138 108.177.122.113 If neither of those give us something conclusive, a packet capture (with exact time the issue occurs) is the ultimate information source.
Great suggestions! We'll test it and share our response once we have data. Appreciate your support!
Hi, the tests didn’t give clear results. When the issue started, nothing altered with the four CMD panels. We also couldn’t pinpoint the exact moment it happened. However, the error appeared only when the computer shut down. What suggestions do you have for moving forward?
We discovered a solution or at least a workaround to bypass the problem entirely. For those facing a comparable challenge, disabling the computer's sleep mode resolved the matter. When the system enters sleep, a network file becomes corrupted, leading to significant ping spikes. By removing this capability, the issue appears to have disappeared. We hope this assists anyone experiencing the same situation! Appreciate your support and advice.