Lots of error messages for CM500 on TWC

[MiloTock]

Upload light is a solid red. Download is a solid green. LAN is flashing. Speed tests show over 75Mbps but downloads are incredibly slow in reality. This is what my log looks like -- a complete hodgepodge of error messages: 

Time Priority Description
2015-11-4, 20:47:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-4, 21:18:02 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-5, 07:24:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-5, 10:40:15 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2015-11-5, 20:06:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
2015-11-6, 21:41:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 22:15:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 22:15:56 Critical (3) REG RSP not received;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 22:16:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 23:53:31 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 23:53:31 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-6, 23:55:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 04:19:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 05:38:15 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 05:38:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
2015-11-7, 05:38:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 08:18:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 11:24:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-7, 13:38:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-8, 07:05:55 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-8, 07:08:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-8, 18:07:32 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 07:21:52 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 07:21:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
2015-11-9, 07:22:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 16:06:34 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 16:07:02 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:29 Notice (6) Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:33 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:52 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:52 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:54 Warning (5) ToD request sent - No Response received;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.0;CM-VER=3.0;
2015-11-9, 21:59:03 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 21:59:03 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 21:59:04 Notice (6) TLV-11 - unrecognized OID;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;
2015-11-9, 22:01:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:6a:03:7d:91:28;CMTS-MAC=00:17:10:87:58:1b;CM-QOS=1.1;CM-VER=3.0;

[Reckoner]

You're not alone. I've been having very similar problems with my CM500 and TWC.

I would be interested to learn if your CM500 is displaying the correct System Time. To find it, log into the CM500, click on the Basic tab, then click on Cable Connection. Scroll to the bottom and you should see displayed the "Current System Time". Is it accurate?

[MiloTock]

System time seems to be correct, and cable connection shows as good, but I have rebooted multiple times -- both hard reboot by powering down and disconnecting cables, and rebooting after logging in to the modem.  Nothing really seems to work, and (needless to say) there is litte assistance from TWN

[vkdelta]

@MiloTock

can you please post your power values?

you have quite a few T3 timeouts which may lead to disconnections.

also, I see DHCP no offer recieved error which means that ISP's DHCP server did not respond to our DISCOVER message.

can you please clear your log and start monitoring