NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM2050V needs daily power cycling
I've had this modem for about a week. I noticed right away that pages were taking a while to load and within a couple of days, I had to power cycle the modem because I had no connection. This happens...
What Firmware version is currently loaded?
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?
- Cable ConnectionCancel Apply
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 Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 4 411000000 Hz -8.0 dBmV 40.9 dB 0 0 2 Locked QAM256 1 393000000 Hz -7.7 dBmV 41.3 dB 0 0 3 Locked QAM256 2 399000000 Hz -7.8 dBmV 41.2 dB 0 0 4 Locked QAM256 3 405000000 Hz -8.1 dBmV 41.0 dB 0 0 5 Locked QAM256 5 417000000 Hz -8.1 dBmV 41.0 dB 535 1427 6 Locked QAM256 6 423000000 Hz -8.4 dBmV 40.8 dB 0 0 7 Locked QAM256 7 429000000 Hz -8.7 dBmV 40.5 dB 0 0 8 Locked QAM256 8 435000000 Hz -9.1 dBmV 40.2 dB 0 0 9 Locked QAM256 9 441000000 Hz -9.2 dBmV 40.1 dB 0 0 10 Locked QAM256 10 447000000 Hz -9.1 dBmV 40.2 dB 0 0 11 Locked QAM256 11 453000000 Hz -9.5 dBmV 39.9 dB 0 0 12 Locked QAM256 12 459000000 Hz -9.7 dBmV 39.7 dB 0 0 13 Locked QAM256 13 465000000 Hz -9.4 dBmV 39.9 dB 0 0 14 Locked QAM256 14 471000000 Hz -9.3 dBmV 40.0 dB 0 0 15 Locked QAM256 15 477000000 Hz -9.2 dBmV 40.1 dB 0 0 16 Locked QAM256 16 483000000 Hz -9.2 dBmV 40.0 dB 0 0 17 Locked QAM256 17 489000000 Hz -9.4 dBmV 39.0 dB 0 0 18 Locked QAM256 18 495000000 Hz -9.1 dBmV 39.6 dB 0 0 19 Locked QAM256 19 501000000 Hz -9.3 dBmV 40.0 dB 0 0 20 Locked QAM256 20 507000000 Hz -9.7 dBmV 39.7 dB 0 0 21 Locked QAM256 21 513000000 Hz -10.0 dBmV 39.6 dB 0 0 22 Locked QAM256 22 519000000 Hz -10.4 dBmV 39.1 dB 0 0 23 Locked QAM256 23 525000000 Hz -10.6 dBmV 34.8 dB 0 0 24 Locked QAM256 24 531000000 Hz -10.8 dBmV 38.6 dB 0 0 25 Locked QAM256 25 537000000 Hz -11.3 dBmV 38.4 dB 0 0 26 Locked QAM256 26 543000000 Hz -11.5 dBmV 38.2 dB 0 0 27 Locked QAM256 27 549000000 Hz -11.4 dBmV 38.3 dB 0 0 28 Locked QAM256 28 555000000 Hz -11.2 dBmV 35.4 dB 0 0 29 Locked QAM256 29 561000000 Hz -11.0 dBmV 38.2 dB 0 0 30 Locked QAM256 30 567000000 Hz -10.9 dBmV 35.5 dB 0 0 31 Locked QAM256 31 573000000 Hz -11.0 dBmV 36.6 dB 0 0 32 Locked QAM256 32 579000000 Hz -10.8 dBmV 37.9 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 16400000 Hz 46.8 dBmV 2 Locked ATDMA 2 5120 22800000 Hz 46.8 dBmV 3 Locked ATDMA 3 5120 29200000 Hz 47.3 dBmV 4 Locked ATDMA 4 5120 35600000 Hz 47.8 dBmV 5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 193 690000000 Hz -12.0 dBmV 36.8 dB 508 ~ 3587 362195004 361701622 530 2 Locked 0 ,1 ,2 ,3 194 957000000 Hz -15.3 dBmV 34.1 dB 148 ~ 3947 370179017 99678973 267543483 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 So just one PC connected to the back of the CM modem?
Power levels are too low:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
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://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/Yes, just a desktop. When you say power levels, what power levels, specifically?
I am not using a router.
Hardware Version 1.01 Cable Firmware Version V2.01.03 Sun Sep 15 22:25:01 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 22:20:40 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:22:14 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:20:23 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:10:04 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:04:26 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:04:18 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 21:01:59 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:59:21 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:57:31 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:23:27 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:17:53 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:03:51 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 20:00:25 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:42:24 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:38:00 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:11:54 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:10:30 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:04:21 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 19:02:24 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 18:57:52 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 18:53:40 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 18:39:22 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 18:38:15 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:53:56 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:52:25 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:18:22 2024 (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: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:17:38 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:17:19 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 17:10:54 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:57:35 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:54:39 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:39:46 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:36:43 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:30:44 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:29:41 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:12:44 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:10:26 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:07:59 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Sep 15 16:05:54 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:b7:84:d8;CMTS-MAC=00:90:f0:2c:01:00;CM-QOS=1.1;CM-VER=3.1;