Orbi WiFi 7 RBE973
Reply

Re: Nighthawk C7000v2 needing frequent rebooting

ShelboTron
Aspirant

Nighthawk C7000v2 needing frequent rebooting

I just got this router/modem from Best Buy roughly 3 months ago. Everything seems to work great for a couple of weeks at a time. I have a 600mbps plan, so I definitely notice when the internet gets slowed down. It's happened since I purchased this model. My wifi gets really weak, and my speeds on ethernet are slow. Pictures load slow, sites load slow, etc. When it starts to do this, I do a speed test, and sure enough, it shows I'm only getting about 10-12mbps on my download speed. When I should be getting 600. So I reboot the Nighthawk, and bam right back up to 600+ speeds. I have to do this about every 2 weeks since I've gotten it. Is there a fix for this? Any suggestions? Firmware shows 1.03.08. Thanks for any help. 

Message 1 of 8
FURRYe38
Guru

Re: Nighthawk C7000v2 needing frequent rebooting

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?

Is Smart Connect enabled or disabled on the modem?

 

Be sure to disable any MAC Address randomizers on phones and pads while at home:
https://community.netgear.com/t5/Nighthawk-App/NETGEAR-Mobile-Applications-and-Apple-Devices-FAQ/td-...

 

Has a factory reset and setup from scratch been performed since last FW update? 

 

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...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Message 2 of 8
ShelboTron
Aspirant

Re: Nighthawk C7000v2 needing frequent rebooting

Okay so I did have the channels on auto...so I changed them to what you suggested. However it's not just my wifi that drops. It's my ethernet/direct connection to my PC that also shows the slow down. I have always had to reboot it to get it to fix again. 

Here's the event log page. 

2024-5-15, 14:12:39Notice (6)WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2024-5-15, 14:12:10Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2024-5-15, 14:12:06Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:GUI
2024-5-14, 02:04:58Notice (6)Honoring MDD; IP provisioning mode = IPv6
2024-5-14, 02:04:42Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:33Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:30Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:27Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:26Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:15Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:04:14Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:36Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:34Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:28Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:23Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:18Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:17Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:12Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:11Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:10Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:08Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:05Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:04Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:03:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:02:53Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:02:52Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:02:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:02:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-5-14, 02:02:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:02:53:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Message 3 of 8
FURRYe38
Guru

Re: Nighthawk C7000v2 needing frequent rebooting

Lets see the cable connections log data please. 

 

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

Message 4 of 8
ShelboTron
Aspirant

Re: Nighthawk C7000v2 needing frequent rebooting

Sorry, I'm not really savvy with this stuff. How do I get to the "cable connection" specifically? All I can see are the event logs.

Message 5 of 8
FURRYe38
Guru

Re: Nighthawk C7000v2 needing frequent rebooting

ON the modems web page there should be a menu feature called Cable Connection Status or something like that:

https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...

Message 6 of 8
ShelboTron
Aspirant

Re: Nighthawk C7000v2 needing frequent rebooting

Under the cable connection tab, this is what it shows.

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel417000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)
 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM2564417000000 Hz4.5 dBmV42.8 dB00
2LockedQAM2561399000000 Hz3.9 dBmV40.2 dB00
3LockedQAM2562405000000 Hz4.3 dBmV42.7 dB00
4LockedQAM2563411000000 Hz4.5 dBmV42.8 dB00
5LockedQAM2565429000000 Hz3.8 dBmV42.1 dB00
6LockedQAM2566435000000 Hz3.4 dBmV41.4 dB00
7LockedQAM2567441000000 Hz3.4 dBmV41.4 dB00
8LockedQAM2568453000000 Hz2.9 dBmV40.8 dB00
9LockedQAM2569459000000 Hz2.6 dBmV40.5 dB00
10LockedQAM25610465000000 Hz2.3 dBmV40.3 dB00
11LockedQAM25611471000000 Hz2.4 dBmV40.3 dB00
12LockedQAM25612477000000 Hz2.5 dBmV40.7 dB00
13LockedQAM25613483000000 Hz3 dBmV41.3 dB00
14LockedQAM25614489000000 Hz2.9 dBmV41.3 dB00
15LockedQAM25615495000000 Hz2.8 dBmV41.4 dB00
16LockedQAM25616501000000 Hz2.3 dBmV40.8 dB00
17LockedQAM25617507000000 Hz0.8 dBmV39.4 dB00
18LockedQAM25618513000000 Hz1 dBmV39.9 dB00
19LockedQAM25619519000000 Hz1.1 dBmV39.9 dB00
20LockedQAM25620525000000 Hz1.4 dBmV40 dB00
21LockedQAM25621531000000 Hz1.6 dBmV40.4 dB00
22LockedQAM25622537000000 Hz1.5 dBmV40.3 dB00
23LockedQAM25623543000000 Hz1.3 dBmV40.2 dB00
24LockedQAM25624549000000 Hz1.3 dBmV40.1 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA195120 Ksym/sec29200000 Hz46.5 dBmV
2LockedATDMA185120 Ksym/sec22800000 Hz46.1 dBmV
3LockedATDMA175120 Ksym/sec16400000 Hz45.9 dBmV
4LockedATDMA205120 Ksym/sec35600000 Hz47.2 dBmV
5LockedATDMA212560 Ksym/sec40400000 Hz48.7 dBmV
6LockedATDMA222560 Ksym/sec10400000 Hz46.5 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
Message 7 of 8
FURRYe38
Guru

Re: Nighthawk C7000v2 needing frequent rebooting

Well that looks good.

 

Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
Be sure your using good quality RG6 coax cable up to the modem. 
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, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Mod...
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/

 

Try a factory reset and setup from scratch. 

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 427 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7