New
#41
Thanks for still reading :). I'm just really curious to why this is happening still. Should i try a fix by going back to a earlier restore point? i have heard this fixes a lot of things.
Thanks for still reading :). I'm just really curious to why this is happening still. Should i try a fix by going back to a earlier restore point? i have heard this fixes a lot of things.
Just as a side note, that may also be the problem.
Ever since i was unable to connect to speedtest.net, I have been experiencing a lot of connection problems every now and then. I would have trouble loading videos. Playing counter strike for example; my ping would tripple and sit at 135ping and not budge.
I also have a brother living here too that does not receive the same issues. He uses the same setup as me etc and doesing really doing anything but "destiny" or "LoL". So is it possible i may have some software issues with my pc? a virus? or just something faulty?
I use restore points as a last resort. The restore process sometimes barfs other stuff.
The IPCONFIG info that you posted earlier did not show all of the extra junk that can sometimes cause problems. Please post the info as an attached text file. See this post for instructions on how to make that text file.
Please see this post and the one below it.
Run a constant ping against Google (and/or speedtest.net).
Run a constant ping against 192.168.1.254
If your ping times increase to Google...
...check to see if they have also increased to the router.
As a quick test, try turning off the W7 firewall.
Open the Windows Firewall with Advanced Security MMC.
Select Inbound Rules in the left hand pane.
Select Export List... in the right most pane.
Save the export as a CSV file to your desktop.
Open it and look for the column named Remote Address.
Let us know of any IP address(es) that you find in that column.
Do the steps above for Outbound Rules too.
My original plan involved electronically searching the exported text/CSV info.
Since there are no IP addresses (or range of addresses), I'm not sure what to look for next.
You might have to:
...disable one rule
...test surfing to speedtest.net
...re-enable that one rule
Repeat until you find the culprit(s).