Community Forum

Dynamic Range Window violation - flaky connection from 2 to 5 PM

Highlighted
Regular Visitor

Dynamic Range Window violation - flaky connection from 2 to 5 PM

Hello.   Since March, between 2 and maybe 5 PM, my cable modem loses connections.  I'm now down to one splitter, from two, and it still happens.  Re-booting the modem brings it back most of the time but then sometimes it drops again.  I was using an Arris when these problems were happening but then switched to a Netgear C7000-100NAS but the problems persist.  Here is a snapshot of today's log.  Is the problem outside or inside of my house and what can be done? 

 

Time Priority Description
2020-9-19, 14:41:31Warning (5)Dynamic Range Window violation
2020-9-19, 14:41:12Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:41:11Warning (5)Dynamic Range Window violation
2020-9-19, 14:40:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:40:11Warning (5)Dynamic Range Window violation
2020-9-19, 14:40:07Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:38:15Warning (5)Dynamic Range Window violation
2020-9-19, 14:38:15Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:38:11Warning (5)Dynamic Range Window violation
2020-9-19, 14:37:00Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:36:51Warning (5)Dynamic Range Window violation
2020-9-19, 14:36:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:36:27Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:36:11Warning (5)Dynamic Range Window violation
2020-9-19, 14:36:07Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:34:12Warning (5)Dynamic Range Window violation
2020-9-19, 14:23:38Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:23:10Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:23:07Warning (5)Dynamic Range Window violation
2020-9-19, 14:23:05Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:22:54Warning (5)Dynamic Range Window violation
2020-9-19, 14:22:54Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:22:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:22:20Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:22:12Warning (5)Dynamic Range Window violation
2020-9-19, 14:22:05Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:53Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:48Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:35Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:34Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:33Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:33Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:21Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:20Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:19Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:19Warning (5)Dynamic Range Window violation
2020-9-19, 14:21:04Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
2020-9-19, 14:21:02Warning (5)Dynamic Range Window violation
2020-9-19, 14:20:54Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:8c:d7:08;CMTS-MAC=2c:31:24:61:16:41;CM-QOS=1.1;CM-VER=3.0;
Highlighted
Expert

Re: Dynamic Range Window violation - flaky connection from 2 to 5 PM

Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.




I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Regular Visitor

Re: Dynamic Range Window violation - flaky connection from 2 to 5 PM

Thank you so much for your reply.  Here is what things looked like today when my VPN dropped me.  I didn't lose my Comcast network connection, though, but the Up-bound icon was flashing on the modem while these figures were collected:

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM25633603000000 Hz12.2 dBmV38.4 dB90188180
2LockedQAM25621531000000 Hz11.8 dBmV38.7 dB1061380
3LockedQAM25622537000000 Hz11.9 dBmV38.8 dB1191970
4LockedQAM25623543000000 Hz12.4 dBmV39.1 dB950940
5LockedQAM25624549000000 Hz12.3 dBmV39 dB1076250
6LockedQAM25625555000000 Hz12.1 dBmV38.8 dB1712620
7LockedQAM25626561000000 Hz11.7 dBmV38.7 dB2539620
8LockedQAM25627567000000 Hz11.4 dBmV38.6 dB3446480
9LockedQAM25628573000000 Hz11.5 dBmV38.5 dB3973550
10LockedQAM25629579000000 Hz10.8 dBmV38.1 dB87983518
11LockedQAM25630585000000 Hz11.3 dBmV38.1 dB11772870
12LockedQAM25631591000000 Hz11.5 dBmV38.2 dB11486080
13LockedQAM25632597000000 Hz11.4 dBmV38 dB13990340
14LockedQAM25634609000000 Hz11.9 dBmV38.3 dB10797880
15LockedQAM25635615000000 Hz12.1 dBmV38.4 dB12466400
16LockedQAM25636621000000 Hz12.2 dBmV38.5 dB11456050
17LockedQAM25637627000000 Hz12.4 dBmV39.3 dB590
18LockedQAM25638633000000 Hz12.2 dBmV39 dB1210
19LockedQAM25639639000000 Hz12.2 dBmV39 dB620
20LockedQAM25640645000000 Hz13 dBmV39.6 dB440
21LockedQAM25641651000000 Hz12.7 dBmV39.4 dB710
22LockedQAM25642657000000 Hz13.7 dBmV39.8 dB590
23LockedQAM25643663000000 Hz14.1 dBmV39.9 dB350
24LockedQAM25644669000000 Hz13.5 dBmV39.5 dB440
 
Upstream Bonded Channels (Partial Service)
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1Not LockedUnknown10 Ksym/sec35600000 Hz0.0 dBmV
2LockedATDMA25120 Ksym/sec29200000 Hz41.3 dBmV
3LockedATDMA35120 Ksym/sec22800000 Hz39.8 dBmV
4LockedATDMA45120 Ksym/sec16400000 Hz46.3 dBmV
5Not LockedUnknown50 Ksym/sec39600000 Hz0.0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Highlighted
Expert

Re: Dynamic Range Window violation - flaky connection from 2 to 5 PM

The downstream power is on the high side bit I'm not certain that that is the root cause of your issue. There is a good amount of correctable bit errors on many of the downstream channels but that should not be a problem as they have been corrected / neutralized. The uncorrectables are practically non-existent.

 

There is a greater than 6 dB difference in upstream channels 3 and 4. It should be only 2 to 3 dB. That typically is the cause of this error;

 

2020-9-19, 14:34:12Warning (5)

Dynamic Range Window violation  

 

I don't think that you will be able to correct this problem. It may be best to get a tech out to investigate and correct this. Good luck with it !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Regular Visitor

Re: Dynamic Range Window violation - flaky connection from 2 to 5 PM

The Comcast tech that came out said the same thing.  On our 4 house junction box he cut an unused line to my neighbor's house and added two terminators where none had been before.  Then he gave me a splitter to put inside the house to lower the signal.  No problems since!  Thank you for your insights!   Gary

Highlighted
Expert

Re: Dynamic Range Window violation - flaky connection from 2 to 5 PM

Hope things hold up for you. Good luck !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!