Cable issues & online gaming
 

Hi,

I'm a dedicated hardcore gamer who just lives for on-line gaming ;)

Basically I'm sure my internet is playing up but i cant prove it or convince my ISP who belive there network is working proply.

I know I'm no cable specialist but I'm sure there's something wrong as i can feel it in my games, its hard to explain but what i see on my screen isn't always what happens.

Iv spent endless nights reading about the internet and cable systems as i find it so interesting forget the time hehe, anyway iv got a page full of 4-Error & 3-Critical.

From what iv read this can be normel or it can mean my modem could be dropping off-line but i dont really fully loss connection just my games can be choppy or jumpy and on download-upload test's in Task Manager it seems to drop connection.

I'm on a UP TO 20mb down and 1mb upload.

Modem status

Software Version: SB5100E-2.3.1.3-SCM01-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Downstream Value
Frequency 450000000 Hz Locked
Signal to Noise Ratio 35 dB <---sometimes 34 dB (i think might be whats wrong?)
Power Level 19 dB


Upstream Value
Channel ID 2
Frequency 28000000 Hz Ranged
Power Level 27 dBmV

Log page


1970-01-01 05:10:14 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:09:44 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:09:43 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:09:43 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:09:16 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:09:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:08:53 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:08:53 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:08:33 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:08:33 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:08:11 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:08:11 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:07:41 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:07:41 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:07:17 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:07:17 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:06:59 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:06:59 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:06:35 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:06:35 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:06:16 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:06:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:05:49 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:05:49 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:05:28 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:05:28 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:05:01 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:05:01 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:04:27 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:04:27 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:03:58 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:03:58 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:03:28 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:03:28 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:03:01 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:03:01 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:02:35 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:02:35 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:02:08 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:02:08 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:01:49 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:01:49 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:01:22 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:01:22 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:56 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:56 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:32 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:32 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 08:06:01 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 06:16:26 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 06:16:01 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 06:12:04 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 06:11:01 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 06:00:31 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 06:00:27 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 06:00:27 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 05:59:57 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 05:59:57 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 05:59:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:59:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:59:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:59:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:59:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:59:10 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:59:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:52 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:49 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:04 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:58:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:58:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 05:57:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 05:57:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

One more thing, when i use more than 30% of my upload my latency is all over the place and thats to my ISP first hop after the router. Think that might be a clue? And its always been like this even before thay brought out the "UP TO 20mb" so I'm not convinced its saturation.
Any help would be appreciated. I hope i posted this in the right place :erm:

Re: Cable issues & online gaming
 

I would ask admin to move your post to "Internet Services" section. I dont think its a home network problem. I would advise you to test without your router in place though (PC connected direct to cable modem).

I take it your getting spikes in latency all the time, with peak times a lot worse than off-peak (if so join the club).

Unsure whats going on with your modem logs, but I'm sure it shouldn't look like that. Have you been in touch with tech support. Newsgroup support is by far the quickest way to check the logs / signal levels out.
Just post description of what happening + modem signals + modem logs on:

virginmedia.support.broadband.cable

(if tech staff asks you to do ping or trace route tests, you'll have to do them with your router removed just to save you time in re-posting info, if you go down that route).