Split second drop outs repeatedly throughout the day [HELP]

[MJS1991]

I recently upgraded to giga byte wifi with Virgin Media and I'm currently really disappointed with the service.
I keep receiving split second dropouts throughout the day and night where I will lose connection for anywhere from a few seconds to a minute. I'm a home worker , working for a software company and this cut out is enough to disconnect and boot me from any team meetings I maybe having at the time. This has lead to me having to work from a coffee shop a few times as not to look unprofessional dropping out of calls. This has also effected my relaxation time as I'm getting booted repeatedly form any gaming servers I play for disconnecting. This has been going on for 6 months + however the disconnections have gotten worse this past month which is what ha prompted me to make this post requesting assistance form the community. I'm using a wired connection directly into my PC and Laptop

Things I have tried so far;

• Router Firmware updated
• PC Network drivers updated
• Turning router off/on
• Turning PC/Laptop off/on
• Forward Path Attenuator ( someone suggested to me DB powers were to high) (makes no difference off or on)  
• There are no issues in my area 

I would like an engineer to come out and look at the street box / home setup 

[MJS1991]

Router Stats

Downstream

Time Priority Description

Mon 17/07/2023 10:37:41	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:06:39	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:06:39	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:06:15	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:06:15	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:05:50	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 10:05:50	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 09:15:52	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:37:05	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:37:05	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:36:41	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:36:41	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:36:17	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:36:17	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:05:41	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:05:41	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:05:06	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:05:06	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 08:00:39	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 07:13:21	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 07:06:23	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 07:06:23	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 07:05:38	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 07:05:38	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 05:35:43	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 05:35:43	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:45:17	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:45:17	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:35:13	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:35:13	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:15:02	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 04:04:54	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 03:22:31	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:43:07	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:34:08	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:34:08	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:14:33	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:14:32	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:07:57	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:04:26	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 02:04:26	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 00:04:07	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/07/2023 00:04:07	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 22:04:08	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 22:04:08	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 19:51:07	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 19:42:31	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 19:42:31	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 19:41:36	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/07/2023 19:41:36	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[MJS1991]

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	23600000	43	5120 KSym/sec	QAM64	5
2	30100000	43.5	5120 KSym/sec	QAM64	4
3	36600000	44	5120 KSym/sec	QAM64	3
4	43100000	44	5120 KSym/sec	QAM64	2
5	49600000	44.5	5120 KSym/sec	QAM64	1

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	0	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10.0

38.5

2K

QAM8

3.1 Upstream channels

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

6

OFDMA

200

53.9

0

0

[MJS1991]

Downstream re posted

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

26	339000000	6.4	35.8	QAM256	26
1	139000000	9.7	36.6	QAM256	1
2	147000000	9	36.6	QAM256	2
3	155000000	8.8	37.4	QAM256	3
4	163000000	8.5	36.6	QAM256	4
5	171000000	8.2	36.6	QAM256	5
6	179000000	8	36.6	QAM256	6
7	187000000	7.7	36.6	QAM256	7
8	195000000	7.4	36.6	QAM256	8
9	203000000	7.4	36.4	QAM256	9
10	211000000	7.2	36.6	QAM256	10
11	219000000	7.3	37.6	QAM256	11
12	227000000	7.3	37.4	QAM256	12
13	235000000	7.4	36.6	QAM256	13
14	243000000	7.3	36.6	QAM256	14
15	251000000	7.3	36.4	QAM256	15
16	259000000	7	36.6	QAM256	16
17	267000000	6.6	36.4	QAM256	17
18	275000000	6.3	36.6	QAM256	18
19	283000000	6.4	36.6	QAM256	19
20	291000000	6.6	36.6	QAM256	20
21	299000000	6.4	36.6	QAM256	21
22	307000000	6.5	36.4	QAM256	22
23	315000000	6.6	36.6	QAM256	23
24	323000000	6.6	36.6	QAM256	24
25	331000000	6.8	36.4	QAM256	25
27	347000000	6.1	35.8	QAM256	27
28	355000000	6	35.8	QAM256	28
29	363000000	5.9	35.8	QAM256	29
30	371000000	5.5	35.6	QAM256	30
31	379000000	5.4	35.1	QAM256	31

3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

26	Locked	35.779911	0	0
1	Locked	36.609653	0	0
2	Locked	36.609653	0	0
3	Locked	37.355988	0	0
4	Locked	36.609653	0	0
5	Locked	36.609653	0	0
6	Locked	36.609653	0	0
7	Locked	36.609653	0	0
8	Locked	36.609653	0	0
9	Locked	36.386890	0	0
10	Locked	36.609653	0	0
11	Locked	37.636276	0	0
12	Locked	37.355988	0	0
13	Locked	36.609653	0	0
14	Locked	36.609653	0	0
15	Locked	36.386890	0	0
16	Locked	36.609653	0	0
17	Locked	36.386890	0	0
18	Locked	36.609653	0	0
19	Locked	36.609653	0	0
20	Locked	36.609653	0	0
21	Locked	36.609653	0	0
22	Locked	36.386890	0	0
23	Locked	36.609653	0	0
24	Locked	36.609653	0	0
25	Locked	36.386890	0	0
27	Locked	35.779911	0	0
28	Locked	35.779911	0	0
29	Locked	35.779911	0	0
30	Locked	35.595078	0	0
31	Locked	35.083549	0	0

3.1 Downstream channels

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

159

96

4K

1840

QAM4096

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

36

0.3

635131285

1141

[Client62 · Accepted solution]

Showing over 600 million Pre RS Errors and over a 100 Post RS errors on the 3.1 Downstream channel, are those figures stable now or still rapidly rising ?

[MJS1991]

They Have risen the latest figures since the post this morning 

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

36

0.2

708291455

1144

[MJS1991]

What does that mean in layman terms though. Apologies I'm not network savy.

[Adduxi]

Usually a fault on the line, e.g. noise ingress.  PostRS errors are not good, as these are errors that the modem cannot correct, so the data has to be re-transmitted.  PreRS errors are errors that have been corrected, but still errors non the less.

[MJS1991]

Ah thank-you for the explanation. What in your experience causes these faults. Is it an outside fault or inside? 
I've checked my wires an they seem to be connected correctly with no visible damage along the cable outside or inside.

[Adduxi]

Could be anything along the connection path, from a cable inside, outside or faulty kit in the street cabinet.  Hard to say, but a VM field technician should be able to ascertain with the correct equipment.