- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Nighthawk C7000v2 needing frequent rebooting
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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:39 | Notice (6) | WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INTERFERENCE |
2024-5-15, 14:12:10 | Notice (6) | WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE |
2024-5-15, 14:12:06 | Notice (6) | WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:GUI |
2024-5-14, 02:04:58 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2024-5-14, 02:04:42 | Critical (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:33 | Critical (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:32 | Critical (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:30 | Critical (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:29 | Critical (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:27 | Critical (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:26 | Critical (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:15 | Critical (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:14 | Critical (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:40 | Critical (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:39 | Critical (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:36 | Critical (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:35 | Critical (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:34 | Critical (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:32 | Critical (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:29 | Critical (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:28 | Critical (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:25 | Critical (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:24 | Critical (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:23 | Critical (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:21 | Critical (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:18 | Critical (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:17 | Critical (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:12 | Critical (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:11 | Critical (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:10 | Critical (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:08 | Critical (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:07 | Critical (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:05 | Critical (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:04 | Critical (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:03 | Critical (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:53 | Critical (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:52 | Critical (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:44 | Critical (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:44 | Critical (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:40 | Critical (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; |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Nighthawk C7000v2 needing frequent rebooting
Under the cable connection tab, this is what it shows.
Startup Procedure | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more