cancel
Showing results for 
Search instead for 
Did you mean: 

Livestream buffering and disconnects while gaming.

DrKnavery
Joining in

Hi there, I've had my 1GB Virgin Broadband for 11 months but for the past 3 weeks or so I've been experiencing a lot of buffering when watching livestreams (Twitch.tv) as well as disconnects from games while playing on PC or Xbox. I've had an engineer visit who came out, replaced a connector outside and left me to see if anything improved. It did not, so he came back with a replacement router. The router was set up with 2 x 4dB attenuators in the back. The problem was even worse than before. I removed those attenuators and it worked pretty much as normal for a few days but now the problem is the same as before. I tried putting both attenuators back, only trying one attenuator at a time. No improvement. What is the next move?

12 REPLIES 12

DrKnavery
Joining in

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
133100000011.742QAM 25625
213900000015.143QAM 2561
314700000014.643QAM 2562
415500000014.443QAM 2563
516300000014.243QAM 2564
617100000013.943QAM 2565
717900000013.943QAM 2566
818700000013.743QAM 2567
919500000013.943QAM 2568
1020300000013.843QAM 2569
1121100000013.643QAM 25610
1221900000013.743QAM 25611
1322700000013.443QAM 25612
1423500000013.243QAM 25613
1524300000013.243QAM 25614
1625100000012.743QAM 25615
1725900000012.743QAM 25616
1826700000012.643QAM 25617
1927500000012.343QAM 25618
2028300000012.543QAM 25619
2129100000012.443QAM 25620
2229900000012.143QAM 25621
2330700000012.243QAM 25622
2431500000011.742QAM 25623
2532300000011.742QAM 25624
2633900000011.442QAM 25626
2734700000011.642QAM 25627
2835500000011.342QAM 25628
2936300000011.342QAM 25629
3037100000011.642QAM 25630
3137900000011.142QAM 25631

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4250751776
2Locked4341047839051
3Locked4330477152621
4Locked4329085165721
5Locked4319095154327
6Locked4341621161931
7Locked4335420057805
8Locked4333349838610
9Locked4329008044637
10Locked4328742446909
11Locked4328528934985
12Locked439679427282
13Locked4310161541234
14Locked437244731775
15Locked4311331545289
16Locked4313686651833
17Locked439855556237
18Locked4313105646885
19Locked439440454346
20Locked4311415443915
21Locked4310531749849
22Locked4315337655208
23Locked438203238879
24Locked425475655375
25Locked426169672925
26Locked42119489113923
27Locked4212363569328
28Locked4219223768035
29Locked4215055753773
30Locked4215350551769
31Locked4214719757245

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
49944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
49Locked405.91048720062104188

DrKnavery
Joining in

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000036.55120QAM 641
14310000036.35120QAM 642
236600000365120QAM 643
33010000035.85120QAM 647
42360000035.55120QAM 648

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
1110.431.52KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
11OFDMA2087400000010
 

DrKnavery
Joining in

Network Log

Time Priority Description
17-05-2024 12:11:53noticeGUI Login Status - Login Fail from LAN interface
16-05-2024 18:33:12noticeGUI Login Status - Login Success from LAN interface
16-05-2024 18:31:47noticeGUI Login Status - Login Fail from LAN interface
16-05-2024 18:04:51warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:47:33noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:45:36noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:43:45noticeCM-STATUS message sent. Event Type Code: 22; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:59noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1
16-05-2024 17:41:59noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM
16-05-2024 17:41:54noticeCM-STATUS message sent. Event Type Code: 20; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:46noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:46noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 5 7 8 10 11 12 13 14 15 17 18 19 20 21 22 23 26 29 30 31 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:42noticeCM-STATUS message sent. Event Type Code: 23; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:36warningRCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:30warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:24criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:09warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:07criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:06criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:06warningRCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:41:03criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:49criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:48warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:43criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:42warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:39criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:33noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:40:30warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:38:09noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:36:14noticeCM-STATUS message sent. Event Type Code: 22; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:34:20noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1
16-05-2024 17:34:15noticeCM-STATUS message sent. Event Type Code: 20; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:34:11noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:34:03noticeCM-STATUS message sent. Event Type Code: 23; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2024 17:34:03noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM
 

DrKnavery
Joining in
 

Thanks for your posts on our Community Forums @DrKnavery, and a very warm welcome to you!

Sorry to hear of the issues you've been experiencing.

I've been able to look into your local area but there doesn't appear to be an issues flagging.

With this, a flow has been ran on the hub and no issues have been revealed.

Can you please provide an updated BQM link and/or screenshot so we can see how things have been since your most recent post?

Thanks,

David_Bn

Purely on the data posted in the thread the downstream power levels are all far too high and there are tens of thousands of Post RS errors and uncorrectable errors. A 10 dB attenuator would seem to be in order here. 

---------------
Cancel VM here
Complain to VM
here
Demand compensation from VM here
Demand your call recordings here
Monitor the state of your VM connection here

legacy1
Alessandro Volta

Just another upstream problem that VM would not like to fix because next day it might be fine instead of fixing the issue.  

---------------------------------------------------------------

Hi David,

I reattached the 2 x 4 equalisers on the 18th at 08:40 to see if that had any effect but found the issue has persisted. Although errors are down. They remain attached. Here's the link for the BQM 

jpeg1
Alessandro Volta

Those attenuators need to stay in.  Do a reset on the Hub and see if the RS errors return. If so there is very likely a cable problem somewhere between the Hub and the street cabinet.

The BQM shows there is a degree of contention on the network which you might be stuck with. 

- jpeg1
My name is NOT Alessandro. That's just a tag Virginmedia sticks on some contributors. Please ignore it.