Have checked cable connections.
Have reset Netgear CM1150V modem multiple times.
Have used used Xfinity online trouble shooting tools.
No effect. Still seeing errors.
Event Log Error details (sample)
Wed Oct 15 10:25:35 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
Wed Oct 15 10:24:08 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
Wed Oct 15 10:22:54 2025 |
Warning (5) |
Dynamic Range Window violation |
Wed Oct 15 10:22:54 2025 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
Cable Connection details
|
Downstream Bonded Channels |
Channel |
Lock Status |
Modulation |
Channel ID |
Frequency |
Power |
SNR |
Correctables |
Uncorrectables |
1 |
Locked |
QAM256 |
20 |
471000000 Hz |
2.7 dBmV |
42.8 dB |
41 |
26 |
2 |
Locked |
QAM256 |
13 |
429000000 Hz |
3.2 dBmV |
43.1 dB |
37 |
38 |
3 |
Locked |
QAM256 |
14 |
435000000 Hz |
2.9 dBmV |
42.9 dB |
40 |
36 |
4 |
Locked |
QAM256 |
15 |
441000000 Hz |
2.8 dBmV |
42.8 dB |
38 |
28 |
5 |
Locked |
QAM256 |
16 |
447000000 Hz |
2.7 dBmV |
42.8 dB |
31 |
2 |
6 |
Locked |
QAM256 |
17 |
453000000 Hz |
2.8 dBmV |
42.8 dB |
2 |
33 |
7 |
Locked |
QAM256 |
18 |
459000000 Hz |
3 dBmV |
42.8 dB |
5 |
34 |
8 |
Locked |
QAM256 |
19 |
465000000 Hz |
2.6 dBmV |
42.7 dB |
182 |
77 |
9 |
Locked |
QAM256 |
21 |
477000000 Hz |
3 dBmV |
42.8 dB |
31 |
0 |
10 |
Locked |
QAM256 |
22 |
483000000 Hz |
3 dBmV |
42.8 dB |
11 |
27 |
11 |
Locked |
QAM256 |
23 |
489000000 Hz |
3.5 dBmV |
42.9 dB |
8 |
28 |
12 |
Locked |
QAM256 |
24 |
495000000 Hz |
3.7 dBmV |
43.1 dB |
24 |
8 |
13 |
Locked |
QAM256 |
25 |
501000000 Hz |
3.4 dBmV |
43 dB |
25 |
0 |
14 |
Locked |
QAM256 |
26 |
507000000 Hz |
3.4 dBmV |
42.9 dB |
28 |
0 |
15 |
Locked |
QAM256 |
27 |
513000000 Hz |
3.3 dBmV |
42.9 dB |
31 |
0 |
16 |
Locked |
QAM256 |
28 |
519000000 Hz |
3.5 dBmV |
42.8 dB |
29 |
3 |
17 |
Locked |
QAM256 |
29 |
525000000 Hz |
3.6 dBmV |
42.7 dB |
8 |
26 |
18 |
Locked |
QAM256 |
30 |
531000000 Hz |
3.4 dBmV |
42.6 dB |
32 |
0 |
19 |
Locked |
QAM256 |
31 |
537000000 Hz |
2.9 dBmV |
42.3 dB |
31 |
0 |
20 |
Locked |
QAM256 |
32 |
543000000 Hz |
2.8 dBmV |
42.2 dB |
24 |
9 |
21 |
Locked |
QAM256 |
33 |
549000000 Hz |
2 dBmV |
41.8 dB |
6 |
34 |
22 |
Locked |
QAM256 |
34 |
555000000 Hz |
2.3 dBmV |
41.7 dB |
7 |
28 |
23 |
Locked |
QAM256 |
35 |
561000000 Hz |
2.2 dBmV |
41.7 dB |
64 |
0 |
24 |
Locked |
QAM256 |
36 |
567000000 Hz |
3.1 dBmV |
42 dB |
28 |
0 |
25 |
Locked |
QAM256 |
37 |
573000000 Hz |
3.4 dBmV |
42.3 dB |
28 |
4 |
26 |
Locked |
QAM256 |
38 |
579000000 Hz |
4.2 dBmV |
42.6 dB |
13 |
21 |
27 |
Locked |
QAM256 |
39 |
585000000 Hz |
4 dBmV |
42.7 dB |
47 |
0 |
28 |
Locked |
QAM256 |
40 |
591000000 Hz |
3.9 dBmV |
42.7 dB |
8 |
0 |
29 |
Locked |
QAM256 |
41 |
597000000 Hz |
3.7 dBmV |
42.6 dB |
15 |
0 |
30 |
Locked |
QAM256 |
42 |
603000000 Hz |
3.7 dBmV |
42.5 dB |
12 |
22 |
31 |
Locked |
QAM256 |
43 |
609000000 Hz |
3.6 dBmV |
42.3 dB |
5 |
30 |
32 |
Locked |
QAM256 |
44 |
615000000 Hz |
3 dBmV |
41.9 dB |
27 |
0 |
|
|
Upstream Bonded Channels |
Channel |
Lock Status |
US Channel Type |
Channel ID |
Symbol Rate |
Frequency |
Power |
1 |
Locked |
ATDMA |
17 |
5120 Ksym/sec |
16400000 Hz |
49.3 dBmV |
2 |
Locked |
ATDMA |
18 |
5120 Ksym/sec |
22800000 Hz |
48.8 dBmV |
3 |
Locked |
ATDMA |
19 |
5120 Ksym/sec |
29200000 Hz |
48.5 dBmV |
4 |
Locked |
ATDMA |
20 |
5120 Ksym/sec |
35600000 Hz |
48.3 dBmV |
5 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
6 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
7 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
8 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
|
|
Downstream OFDM Channels |
Channel |
Lock Status |
Modulation / Profile ID |
Channel ID |
Frequency |
Power |
SNR / MER |
Active Subcarrier Number Range |
Unerrored Codewords |
Correctable Codewords |
Uncorrectable Codewords |
1 |
Locked |
0 ,1 ,2 ,3 |
193 |
690000000 Hz |
4.9 dBmV |
42.6 dB |
148 ~ 3947 |
7791033725 |
5300075138 |
343058 |
2 |
Locked |
0 ,1 ,2 ,3 |
194 |
957000000 Hz |
-1.9 dBmV |
41.1 dB |
148 ~ 3947 |
7895526855 |
5223301999 |
1780951 |
|
|
Upstream OFDMA Channels |
Channel |
Lock Status |
Modulation / Profile ID |
Channel ID |
Frequency |
Power |
1 |
Not Locked |
0 |
0 |
0 Hz |
0 dBmV |
2 |
Not Locked |
0 |
0 |
0 Hz |
0 dBmV |
|
|
Current System Time:Wed Oct 15 21:30:09 2025 |
System Up Time:6 days 12:13:32 |
EG
Expert
•
114K Messages
3 days ago
This may or may not be the root cause of the problem (YMMV), but it should be addressed regardless.
The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the unbonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/reconfigured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also, check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, or animal chews.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
0
0
XfinityNatalie
Official Employee
•
398 Messages
1 day ago
Hi there, user_q10i5u! Thanks for knocking on our XFINITY Community door with your connectivity concerns. I understand how important it is to have a stable connection when streaming your favorite videos. We’re really sorry if that hasn’t been your experience, that’s not the kind of journey we ever want you to have with us. Rest assured, XFINITY is here to save the day! Before proceeding with troubleshooting, I would like to ask what steps have you taken towards troubleshooting your connection so far?
0
0
EG
Expert
•
114K Messages
14 hours ago
@user_q10i5u
Have you had a chance to see if any of those tips apply ?
2
0
EG
Expert
•
114K Messages
13 hours ago
@user_q10i5u
Thanks for replying ! Ok, so if there is nothing more that can be done to improve the connection quality, then yes, you'll need a tech visit as you stated.
Bear in mind that if the premises-facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
0
0