Modems rebooting after heavy use

Question

After about 4 cable technicians and many nights of constant failures, I wanted to turn to the internet for answers.

In the past month, my modem is constantly rebooting itself after 4 or so hours of constant use. This is especially annoying since I play online games and having to be disconnected for brief moments.

My cable provider is Suddenlink and I have had them for 2 1/2 years. The only problems I had with them was when I needed their rental modem replaced. After 2 years, I decided to get my own modem to save on money. My first modem was an Arris Surfboard Cable Modem Model SB6141.

It was working just fine up until recently. I could surf the web and I could play my games without fear of having a random disconnect. So to have it start after a few months of use was worrying. So I decided to do a bit of troubleshooting. I first started with power cycling and factory reseting. Didn't work. I then tried getting a UPS and giving it its own power source. The modem still rebooted itself after a few hours of use. I tried to see if heating was an issue. My room is well ventilated and is constantly at low tepperature with a fan blowing through the room. I then replaced my modem with the CM400 Netgear modem to see if that would work.

Nope.

It did the same thing as the other modem. So, then I called the technicians out there. The first technician removed a filter on the line to see if that worked. He leaves, I start using the internet. 4 hours later, the modem reboots itself. I call a 2nd technician out here. This technician gives me my own line and even replaced the splitter I was attached to and puts it on a three way splitter.

For reference, the cable reaches from at least 3 poles and to a 2 way splitter before they attache another cable that is covered and buried underground. The coaxial cable is then brought through the floor of the trailer and attached to the modem.

4 hours later, modem reboots.

I then call a third tech to see if they would know anything else to replace. The guy just tests the connection and tells me that I either have a grounding issue or an electric issue. My trailer has a grounding box and everything in the trailer has been working fine, no fluctuations or anything. He also mentions that the SNR was fine and passable. So he just places another splitter on the line; this time inside the trailer before it hits the box.

I checked the logs for my modem and saw that the power levels as well as the noise was well within the recommended range and yet when I look at my logs I keep seeing T3 Timeouts every so often.

I called a fourth tech out today. It was the same guy as last time. All he does it check the connection on his equipment, tell me nothing is wrong, and leaves but not before saying something about seeing if I have a grounding issue or an electrical issue.

This is the only cable internet service I have in the area and nobody even knows what is going on with my modems.

When I say "reboot", I mean that all the lights, except for the power light, goes out and slowly blink back on.

Is there anyone here that has an idea as to what the problem really is?

vkdelta · Answer

Can you please post event log and power table for us to review?&nbsp;

AlistairPhoenix · Answer

Event LogTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 4 17:07:10 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Time Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 4 20:11:07 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Time Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 4 23:03:26 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 5 04:04:43 2017 Warning (5) Lost MDD TimeoutJul 5 04:05:42 2017 Critical (3) No Ranging Response received - T3 time-outJul 5 04:06:36 2017 Warning (5) Lost MDD TimeoutTime Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 5 10:09:15 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Time Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 5 14:09:47 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Time Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 5 17:56:59 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 5 22:54:27 2017 Warning (5) Lost MDD TimeoutTime Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 5 23:18:55 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 6 04:18:12 2017 Warning (5) Lost MDD TimeoutTime Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 6 04:29:11 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jul 6 09:24:55 2017 Warning (5) Lost MDD TimeoutTime Not Established Critical (3) No Ranging Response received - T3 time-outTime Not Established Critical (3) DHCP failed - RS sent, no RA receivedTime Not Established Error (4) Primary lease failed, IPv4 fallback initiatedJul 6 09:43:52 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1&nbsp;&nbsp;

vkdelta · Answer

can you please post your powet table as well from the connection page? thank you.

AlistairPhoenix · Answer

Downstream Bonded ChannelsChannel Lock Status Modulation Channel ID Frequency&nbsp; &nbsp; &nbsp; &nbsp;Power&nbsp; &nbsp; &nbsp; &nbsp;SNR Correctables UnCorrectables1 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;567000000 Hz &nbsp;8.7 dBmV &nbsp;35.5 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;24 6862 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;573000000 Hz &nbsp;8.4 dBmV &nbsp;35.5 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19 5443 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;579000000 Hz &nbsp;8.2 dBmV &nbsp;35.4 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6 5414 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;585000000 Hz &nbsp;8.2 dBmV &nbsp;35.4 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19 7335 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;591000000 Hz &nbsp;8.5 dBmV &nbsp;35.5 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;29 6156 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;597000000 Hz &nbsp;9.0 dBmV &nbsp;35.5 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;26 7027 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;7 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;603000000 Hz &nbsp;9.3 dBmV &nbsp;35.9 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;31 6518 &nbsp; &nbsp; &nbsp; &nbsp;Locked QAM 256 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;8 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;609000000 Hz &nbsp;9.7 dBmV &nbsp;36.1 dB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;33 611Upstream Bonded ChannelsChannel Lock Status US Channel Type Channel ID Symbol Rate&nbsp; &nbsp; &nbsp; Frequency&nbsp; &nbsp; &nbsp; &nbsp;Power1 &nbsp; &nbsp; &nbsp; &nbsp;Locked &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ATDMA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;44 &nbsp; &nbsp; &nbsp; &nbsp;2560 Ksym/sec &nbsp; &nbsp; 21400000 Hz &nbsp;39.5 dBmV2 &nbsp; &nbsp; &nbsp; &nbsp;Locked &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ATDMA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;43 &nbsp; &nbsp; &nbsp; &nbsp;2560 Ksym/sec &nbsp; &nbsp; 25000000 Hz &nbsp;39.8 dBmV3 &nbsp; &nbsp; &nbsp; &nbsp;Locked &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ATDMA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;42 &nbsp; &nbsp; &nbsp; &nbsp;5120 Ksym/sec &nbsp; &nbsp; 30700000 Hz &nbsp;40.5 dBmV4 &nbsp; &nbsp; &nbsp; &nbsp;Locked &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ATDMA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;41 &nbsp; &nbsp; &nbsp; &nbsp;5120 Ksym/sec &nbsp; &nbsp; 37500000 Hz &nbsp;41.3 dBmV

vkdelta · Answer

can you please PM me? we will need some details which you would not be able to post publicly.&nbsp;&nbsp;thank you. modems going offline is not acceptable (and especially every few hours).&nbsp;&nbsp;few items noticed in your logs:&nbsp;1. Power are generally ok. DS is bit hot but it is not a deal breaker.2. Uncorrectables should be 0 but it is not a big problem since the count is low.3. US powers levels look OK as well.4. Event log is messed up:&nbsp;

Forum Discussion

Modems rebooting after heavy use

6 Replies