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

Forum Discussion

Keninboston's avatar
Keninboston
Aspirant
Jan 04, 2024

Sporadic router freeze on CAX80 - only when using WiFi

My Problem: Sporadic router freeze on CAX80 - only when using WiFi   Am looking for help troubleshooting assistance.  CAX80, hardware Version: 1.01, Firmware Version: v1.02.08.  Connected to Xfinit...
Troubleshooting
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Jan 04, 2024

Your behind on FW:

https://community.netgear.com/t5/Cable-Modems-Gateways/New-CAX80-Firmware-Version-2-1-5-2-Released/td-p/2271938/jump-to/first-unread-message

 

What wifi channels  are you using? 

What wifi devices do you all have connected? 

 

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

  • Keninboston's avatar
    Keninboston
    Aspirant
    Jan 05, 2024

    Thanks for the reply! Let me know if there is something I left out.  My info below:

     

    Firmware

    I realized I put in the cable firmware and not the router firmware.  I didn't realize that there were separate firmware setups for cable and router, I am current on router updates, here they are for reference:

    Firmware VersionV2.1.5.2
    Cable Firmware VersionV1.02.08

     

    What wifi channels are you using?

    For 2.4 GHz, channel is set to auto and currently 9.  5GHz is set to 48.  I've tried switching them around with no change in behavior.

     

    What wifi devices do you all have connected?

    iPhone, 2 iPads, Macbook, LG SmartTV. 

     

    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-m...

    Cable Connection
    Cancel Apply
    Cable Diagnostic
    Status:   Good
    Action:   Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.
    Internet Access: 
    Downstream Status: 
    Upstream Status: 
     Refresh Save Cable Diagnostic Info
     
    Advanced Information
    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 


    https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

    TimePriorityDescription
    Fri Jan 5 14:39:14 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 14:37:24 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 14:35:30 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 14:29:50 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 13:40:00 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 13:36:27 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 11:10:07 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 11:06:24 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 09:54:29 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 09:52:48 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 07:48:06 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Fri Jan 5 07:43:40 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 22:30:11 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 22:28:37 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 21:55:55 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 21:49:14 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 20:41:29 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 20:35:06 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 20:33:21 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 20:29:57 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 18:07:37 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 18:05:43 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 16:09:40 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 16:05:16 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 15:48:34 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 15:42:08 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 15:13:35 2024Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 15:13:02 2024Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 12:23:59 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 12:23:57 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 12:23:31 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 1 00:00:50 1970Notice (6)Honoring MDD; IP provisioning mode = IPv6
    Thu Jan 1 00:00:44 1970Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 1 00:00:44 1970Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 4 12:13:34 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 1 00:00:46 1970Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan 1 00:00:44 1970Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Tue Jan 2 20:23:51 2024Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Wed Dec 20 23:11:58 2023Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;
    Sat Dec 16 10:13:54 2023Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:dd:a5:b0;CMTS-MAC=00:90:f0:44:00:00;CM-QOS=1.1;CM-VER=3.1;