Hello Toms Hardware,
I have had a post marinating over on the Comcast support forums for more than 16 hours with zero comments, so I am turning to you folks for some help.
My Surfboard Modem has been randomly rebooting, slowly getting worse over the last week.
The modem is over a year old, and has performed flawlessly up to this point. After the random reboots started, I requested a refresh signal to my modem, which happened two days ago, and it seems to have gotten worse.
I feel like the issue is kind of reproducable if one person is streaming Amazon Prime or Netflix, and I am playing Online Games. Multi-tasking seems to be an issue, but I am not 100% certain, cause sometimes is just happens when I am the only one home, and I am just gaming and it will randomly cut out.
Also, the Modem is getting quite warm. I have started pointing a fan at it to cool the darn thing off.
I dont know what any of this means, so anyone that can shed some light on the errors below for me please let me know. If I need to get a Comcast tech over here, fine. If I need a new modem, fine. I just want to get the issue resolved and go back to not worrying about my connection.
The Modem has one LAN cable connected to a Netgear Nighthawk AC1900, which is the hub of my home network. Connected to this router is:
Hardwired:
Xbox One
Wireless:
Wife's Surface 2
My office desktop (custom build)
My Lenovo u430 Laptop
Nexus 7 tablet
Note 2 Phone
Samsung S4 Mini phone
iPhone 5S
My signal details:
Downstream
Channel ID 12
Frequency 721750000 Hz
Signal to Noise Ratio 36 dB
Downstream Modulation QAM256
Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 2 dBmV
Upstream
Channel ID 49
Frequency 36400000 Hz
Ranging Service ID n/a
Symbol Rate 5.120 Msym/sec
Power Level 45 dBmV
Upstream Modulation [3] QPSK [3] 64QAM
Ranging Status Other
Signal Stats
Channel ID 12
Total Unerrored Codewords 1190175
Total Correctable Codewords 25
Total Uncorrectable Codewords 701
LOGS:
Sep 02 2014 18:12:44 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:08:44 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:15 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:15 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:33:30 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:32:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:13:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:13:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:05:36 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:04:49 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:02:53 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=
All of this signal data and logs was collected last night. I am at the office now, but can post updated information if necessary this evening when I get home from work.
I have had a post marinating over on the Comcast support forums for more than 16 hours with zero comments, so I am turning to you folks for some help.
My Surfboard Modem has been randomly rebooting, slowly getting worse over the last week.
The modem is over a year old, and has performed flawlessly up to this point. After the random reboots started, I requested a refresh signal to my modem, which happened two days ago, and it seems to have gotten worse.
I feel like the issue is kind of reproducable if one person is streaming Amazon Prime or Netflix, and I am playing Online Games. Multi-tasking seems to be an issue, but I am not 100% certain, cause sometimes is just happens when I am the only one home, and I am just gaming and it will randomly cut out.
Also, the Modem is getting quite warm. I have started pointing a fan at it to cool the darn thing off.
I dont know what any of this means, so anyone that can shed some light on the errors below for me please let me know. If I need to get a Comcast tech over here, fine. If I need a new modem, fine. I just want to get the issue resolved and go back to not worrying about my connection.
The Modem has one LAN cable connected to a Netgear Nighthawk AC1900, which is the hub of my home network. Connected to this router is:
Hardwired:
Xbox One
Wireless:
Wife's Surface 2
My office desktop (custom build)
My Lenovo u430 Laptop
Nexus 7 tablet
Note 2 Phone
Samsung S4 Mini phone
iPhone 5S
My signal details:
Downstream
Channel ID 12
Frequency 721750000 Hz
Signal to Noise Ratio 36 dB
Downstream Modulation QAM256
Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 2 dBmV
Upstream
Channel ID 49
Frequency 36400000 Hz
Ranging Service ID n/a
Symbol Rate 5.120 Msym/sec
Power Level 45 dBmV
Upstream Modulation [3] QPSK [3] 64QAM
Ranging Status Other
Signal Stats
Channel ID 12
Total Unerrored Codewords 1190175
Total Correctable Codewords 25
Total Uncorrectable Codewords 701
LOGS:
Sep 02 2014 18:12:44 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:08:44 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:15 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:15 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 18:06:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:33:30 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:32:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:13:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:13:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:05:36 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:04:49 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2014 17:02:53 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:7d:37:98:41:3f;CMTS-MAC=00:01:5c:62:f0:4a;CM-QOS=1.1;CM-VER=
All of this signal data and logs was collected last night. I am at the office now, but can post updated information if necessary this evening when I get home from work.