NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1200: rebooting itself at random times
Hello,
Cable modem CM1200 is 6 month old. Last few months, I started noticing that the connection drops automatically and reconnects itself. I called Xfinity tech and they confirmed that signal is ok. While troubleshooting with Xfinity I actually show that the model rebooted itself. When the modem decided to reboot itself, it continues to reboot itself for an hour or two. Very frustrating experience with Netgear!!
Firmware Version: V10.11.02
Is there a solution to this issue?
Would appreciate help.
Cable modem CM1200 is 6 month old. Last few months, I started noticing that the connection drops automatically and reconnects itself. I called Xfinity tech and they confirmed that signal is ok. While troubleshooting with Xfinity I actually show that the model rebooted itself. When the modem decided to reboot itself, it continues to reboot itself for an hour or two. Very frustrating experience with Netgear!!
Firmware Version: V10.11.02
Is there a solution to this issue?
Would appreciate help.
3 Replies
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.
What is the brand and model of the host wifi router connected to the modem?- Thank you for helping
Modem is connected to netgear R7900P
Below is requested data, sorry I couldn’t find a way to download the data and attach it in nicer format
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD IPv6 only
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 507000000 Hz 0.7 dBmV 40.8 dB 226 153
2 Locked QAM256 17 483000000 Hz 0.6 dBmV 41 dB 256 113
3 Locked QAM256 18 489000000 Hz 0.4 dBmV 40.9 dB 300 156
4 Locked QAM256 19 495000000 Hz 0.4 dBmV 41 dB 344 310
5 Locked QAM256 21 513000000 Hz 0.5 dBmV 40.8 dB 266 93
6 Locked QAM256 22 519000000 Hz 0.6 dBmV 40.8 dB 286 192
7 Locked QAM256 23 525000000 Hz 0.8 dBmV 40.9 dB 344 238
8 Locked QAM256 24 531000000 Hz 0.8 dBmV 40.8 dB 200 241
9 Locked QAM256 25 537000000 Hz 0.7 dBmV 40.6 dB 197 108
10 Locked QAM256 26 543000000 Hz 0.4 dBmV 40.5 dB 209 157
11 Locked QAM256 27 549000000 Hz 0.3 dBmV 40.4 dB 224 231
12 Locked QAM256 28 555000000 Hz 0.4 dBmV 40.5 dB 207 237
13 Locked QAM256 29 561000000 Hz 0.2 dBmV 40.3 dB 163 153
14 Locked QAM256 30 567000000 Hz -0.3 dBmV 40.1 dB 177 88
15 Locked QAM256 31 573000000 Hz -0.3 dBmV 40.2 dB 166 173
16 Locked QAM256 32 579000000 Hz -0.1 dBmV 40.2 dB 243 284
17 Locked QAM256 33 585000000 Hz 0.1 dBmV 40.2 dB 141 180
18 Locked QAM256 34 591000000 Hz -0.1 dBmV 40.1 dB 110 98
19 Locked QAM256 35 597000000 Hz -0.4 dBmV 39.9 dB 147 74
20 Locked QAM256 36 603000000 Hz -0.4 dBmV 39.9 dB 202 139
21 Locked QAM256 37 609000000 Hz -0.5 dBmV 39.9 dB 168 223
22 Locked QAM256 38 615000000 Hz -0.4 dBmV 39.8 dB 96 128
23 Locked QAM256 39 621000000 Hz -0.3 dBmV 39.9 dB 79 86
24 Locked QAM256 40 627000000 Hz -0.4 dBmV 39.8 dB 94 113
25 Locked QAM256 41 633000000 Hz -0.5 dBmV 39.7 dB 143 167
26 Locked QAM256 42 639000000 Hz -0.4 dBmV 39.7 dB 113 151
27 Locked QAM256 43 645000000 Hz -0.5 dBmV 39.8 dB 82 92
28 Locked QAM256 44 651000000 Hz -0.8 dBmV 39.7 dB 116 88
29 Locked QAM256 45 657000000 Hz -1.1 dBmV 39.7 dB 95 135
30 Locked QAM256 46 663000000 Hz -1 dBmV 39.6 dB 84 176
31 Locked QAM256 47 669000000 Hz -1 dBmV 39.6 dB 313 95
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 6 2560 Ksym/sec 10400000 Hz 39.5 dBmV
2 Locked ATDMA 7 5120 Ksym/sec 16400000 Hz 40.5 dBmV
3 Locked ATDMA 8 5120 Ksym/sec 22800000 Hz 40.8 dBmV
4 Locked ATDMA 10 5120 Ksym/sec 35600000 Hz 41.8 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 48 850000000 Hz -1.9 dBmV 38.2 dB 1108 ~ 2987 24300342776 22380357933 2
2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0
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
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
Current System Time:Sat Feb 22 13:36:49 2025
System Up Time:13 days 04:33:27
—————————-
Time Priority Description
Sat Feb 22 06:09:51 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 06:09:22 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 06:09:18 2025 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 06:09:18 2025 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 06:09:18 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:46 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:20 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:16 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:01 2025 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:01 2025 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Sat Feb 22 05:25:01 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 08:08:34 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 08:07:52 2025 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 08:07:52 2025 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 08:07:52 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:38:36 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:38:25 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:37:32 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:37:12 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:37:11 2025 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:37:08 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:37:02 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:36:57 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:36:53 2025 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:36:53 2025 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:36:53 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:36:26 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:50 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:42 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:37 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:26 2025 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:22 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:09 2025 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 7 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:34:01 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:49 2025 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:40 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:39 2025 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 7 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:16 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:09 2025 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 7 8 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Fri Feb 21 07:33:07 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:d2:de:a1;CMTS-MAC=00:01:5c:7d:7a:52;CM-QOS=1.1;CM-VER=3.1;
Help Center Show/Hide Help CenterPower levels are ok.
Getting some Correctables and Un-correctables that should be mostly zeros.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/
