CM-500 Slow speeds, shows weak signal on ISP's end

Question

Modem is CM500, Cox is ISP. MY speeds have dropped to half of capacity in the last month(down to 160mbps). Mac OSX 10.11.6, Apple Time Capsule router(2014). Have done all the power cycling, rebooting modem/router, etc. Modem is under hardware warranty til 2/7/17.

Here's the modem log:

1970-1-1, 00:00:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:36 Notice (6) Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:38 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.0;CM-VER=3.0;
2016-12-27, 16:52:03 Notice (6) TLV-11 - unrecognized OID;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-27, 16:52:46 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 11:19:00 Warning (5) Dynamic Range Window violation
2016-12-29, 11:20:16 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 11:24:44 Warning (5) Dynamic Range Window violation
2016-12-29, 11:25:30 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 11:25:44 Warning (5) Dynamic Range Window violation
2016-12-29, 11:26:00 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 11:27:58 Warning (5) Dynamic Range Window violation
2016-12-29, 12:03:08 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 12:04:06 Warning (5) Dynamic Range Window violation
2016-12-29, 12:04:22 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 12:05:21 Warning (5) Dynamic Range Window violation
2016-12-29, 12:06:37 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-29, 12:06:51 Warning (5) Dynamic Range Window violation
2016-12-30, 11:31:12 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-30, 11:59:35 Warning (5) Dynamic Range Window violation
2016-12-31, 04:52:00 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2016-12-31, 17:24:58 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-3, 16:52:00 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 11:40:05 Warning (5) Dynamic Range Window violation
2017-1-8, 11:41:21 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 11:59:16 Warning (5) Dynamic Range Window violation
2017-1-8, 14:31:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:31:14 Warning (5) MDD message timeout;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:31:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:31:18 Warning (5) MDD message timeout;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:32:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:32:38 Warning (5) MDD message timeout;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:32:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:32:43 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
2017-1-8, 14:32:44 Warning (5) MDD message timeout;CM-MAC=40:5d:82:f0:55:b8;CMTS-MAC=00:14:f1:e5:d0:cc;CM-QOS=1.1;CM-VER=3.0;
Help Center

TheEther · Answer

Yup, it looks like the modem is having trouble communicating with the ISP's CMTS. &nbsp;You should ask the ISP to investigate. &nbsp;In the meantime, make sure that you eliminate as many coax splitters between the modem and the coax cable coming into the house as possible. &nbsp;This will help ensure that the modem receives the strongest signal as possible from the ISP.

rightintel · Answer

Thanks. They checked(level 2 support) and said the signal end everything was fine on their end. They said the modem was having power(volts or amps or something to that effect). So is this a hardware problem or what then? It's outta warranty in a month, so I need t figure out what to do...

TheEther · Answer

There's not enough information to tell whether or not it's a hardware problem. &nbsp;You can also check the signal levels on your modem.
&nbsp;
Did you remove any unnecessary splitters?

rightintel · Answer

Yeah, there's no splitters anyway. One line to the modem from the wall cable outlet to the modem. Not sure what to do if they state it's not their end. Connectivity isn't a problem, just slower speeds. They say signal is fine, but they see a problem on the modem's end. I factory reset the modem and router, that usually makes it a LITTLE faster, but I'm having to do that too often.&nbsp;

TheEther · Answer

You may have connectivity but that doesn't mean the quality of the connection is good, sorta like Wi-Fi.
&nbsp;
How about posting the signal levels under&nbsp;Cable Connection?

Forum Discussion

CM-500 Slow speeds, shows weak signal on ISP's end

8 Replies