bdubs85 :
A quick way to check the signal to the internet would be to run a ping test.
Open a command prompt by (if you have windows 7) opening the start menu and typing "cmd". If you have windows xp, open start, then Run, then type "cmd".
A box with a black background will open. It will have something like "C:\Windows\system32>_" with a flashing underscore. Type in "ping google.com -t" (or substitute any website address for google.com) and then press Enter.
The command prompt will then start giving you results to the website of your choice until you cancel it or close the window.
Start playing your game while leaving the command prompt window open. When you get disconnected from the game, switch back over to the command prompt and press Control+C to stop it from pinging, then use the scrollbar on the right to check back through your results.
A normal ping result will look like this:
Reply from 208.48.161.105: bytes=32 time=166ms TTL=47
Reply from 208.48.161.105: bytes=32 time=215ms TTL=47
Reply from 208.48.161.105: bytes=32 time=155ms TTL=47
Reply from 208.48.161.105: bytes=32 time=138ms TTL=47
Reply from 208.48.161.105: bytes=32 time=155ms TTL=47
These results are off of a slow 3g connection, so your "time=xxxms" should be lower than mine. If your time=xxxms is higher than about 100-150, you may have a problem with your internet provider. If it shows "No Response" or another error like that, you have a problem with either your network card, your router, or your internet service.
I did what you said except i was browsing the internet and it said this
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Reply from 74.125.239.40: bytes=32 time=37ms TTL=51
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Reply from 74.125.239.40: bytes=32 time=38ms TTL=51
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Request timed out.
Request timed out.
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Reply from 74.125.239.40: bytes=32 time=38ms TTL=51
Reply from 74.125.239.40: bytes=32 time=35ms TTL=51
Reply from 74.125.239.40: bytes=32 time=43ms TTL=51
Reply from 74.125.239.40: bytes=32 time=42ms TTL=51
Reply from 74.125.239.40: bytes=32 time=35ms TTL=51
Reply from 74.125.239.40: bytes=32 time=35ms TTL=51
Reply from 74.125.239.40: bytes=32 time=36ms TTL=51
Reply from 74.125.239.40: bytes=32 time=34ms TTL=51
Reply from 74.125.239.40: bytes=32 time=36ms TTL=51
Reply from 74.125.239.40: bytes=32 time=35ms TTL=51
Reply from 74.125.239.40: bytes=32 time=35ms TTL=51
Ping statistics for 74.125.239.40:
Packets: Sent = 1617, Received = 1596, Lost = 21 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 122ms, Average = 35ms
Is it possible that the request timed out part is the hiccup i have been having?
Facebook
Twitter
Instagram