NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

SunWukong92's avatar
SunWukong92
Tutor
Mar 20, 2022
Solved

CM1200 Modem randomly cuts off

Hi everyone,

 

I'm currently having issues with my netgear CM1200. For the last 2 weeks the upstream light has blinked and then gone solid, then the downstream light blinks goes solid, then the upstream, downstream and internet light all turn off and slowly each turns back on. Or the upstream light blinks goes solid and the downstream light blinks goes solid and they stay solid, but then my router says there's no internet connection.

 

I have tried everything from a shock reset to a factory reset. My lines to my house from the outside cablebox is new and so is my house wire. I have contacted Xfinity and they should be sending a tech to check for me but who knows if it'll work... I have also tried switching out a new modem and it did the same exact thing.

 

I have included the Log and the power information.

TimePriorityDescription
Sun Mar 20 01:23:47 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 01:23:23 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:27:33 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:27:06 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:26:57 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:25:34 2022Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:25:30 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:24:58 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:24:57 2022Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 20 00:24:26 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:50 2022Notice (6)CM-STATUS message sent. Event Type Code: 8; Chan ID: 5 6 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:33 2022Notice (6)CM-STATUS message sent. Event Type Code: 8; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:33 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:33 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:33 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:16 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:16 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:50:16 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:50 2022Notice (6)CM-STATUS message sent. Event Type Code: 8; Chan ID: 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:48 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:48 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:48 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:41 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:40 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:31 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:31 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:21 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:20 2022Notice (6)CM-STATUS message sent. Event Type Code: 8; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:19 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:19 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:19 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:11 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:10 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:49:00 2022Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:59 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:51 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:49 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:45 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:44 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 19 23:48:40 2022Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3d:fc:d8;CMTS-MAC=00:01:5c:82:cc:79;CM-QOS=1.1;CM-VER=3.1;
 
 
Apply               Cancel     
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  • plemans's avatar
    plemans
    Mar 20, 2022

    here's hoping it stays stable for you!
    if it does, I'd mark it solved so others aren't trying to continue to fix a resoled issue 🙂

3 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User
    Mar 20, 2022

    the logs indicate a line issue. 

    The cable connection page helps in conjunction with the event logs though. 

    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, bad/old/cheap connectors, or corroded connections. Replace them if you do.
    If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

    • SunWukong92's avatar
      SunWukong92
      Tutor
      Mar 20, 2022

      Hey, sorry i didnt include this however there is only one wire running from the outside box to my house then there is the connector that runs straight to my modem without any other connectors. it goes directly to my modem 😄 and from the sounds of it you were right it appears there was a "performance issue" that comcast neglected to mention that was being maintenanced today thankfully they went out to check out now for the test of using my internet for the day to see if any more issues arise.

       

      Thank you for the translation of the log and power page. I have no idea how to read it but i know more than enough to troubleshoot on my own and that was the limit of my knowledge.

      • plemans's avatar
        plemans
        Guru - Experienced User
        Mar 20, 2022

        here's hoping it stays stable for you!
        if it does, I'd mark it solved so others aren't trying to continue to fix a resoled issue 🙂