Your modem keeps restarting because of a bunch of errors labeled as CM1200.
Your modem keeps restarting because of a bunch of errors labeled as CM1200.
I've called out 7 different tech groups first few were just single people and now there bringing out multiple techs when ever I make a call and this has been happening for about 2 months now. I've switched hardware to a Netgear CM1200 and Netgear Router which is recommended by Sparklight (My ISP). So far these are the errors are either new or similar to my old modem and router setup. The new errors are: REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; I'm sure the new errors are due to being a different modem that is way newer (my old modem was from 2014 aka the SB6183 Arris Surfboard) Although a lot of the errors are similar to the ones I got before like TLV-11, Started Unicast Maintenance Ranging - No Response Received, Missing BP Configuration, etc. Time Priority Description Sun Jan 01 19:00:00 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 19:00:00 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:59:59 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:59:59 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:27 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:22 2023 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:18 2023 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Notice (6) TLV-11 - unrecognized OID;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:17 2023 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:14 2023 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Sun Jan 01 18:48:04 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:04 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:03 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:48:03 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:47:34 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:47:10 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:46:12 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:45:47 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:45:47 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:45:46 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:45:30 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:44:46 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:23 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:09 2023 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:05 2023 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Notice (6) TLV-11 - unrecognized OID;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; Sun Jan 01 18:43:04 2023 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=c8:9e:43:e7:ae:08;CMTS-MAC=00:17:10:aa:8d:13;CM-QOS=1.1;CM-VER=3.1; [TD][/TD] They note there is a lot of disconnections but no packet loss for some reason. Also noted a lot of uncorrectables. I've noticed it only goes down when I'm stressing it like streaming, playing video games, and talking in discord. Basically anything that requires a constant up to date and fast connection will usually make it reboot. The most I can do is text, go on social media, etc. Below is the cable connection information: Startup Procedure Procedure Status Comment Acquire Downstream Channel 609000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 23 609000000 Hz -7 dBmV 36.6 dB 563588 219712 2 Locked QAM256 1 477000000 Hz -8.2 dBmV 36.2 dB 462101 212614 3 Locked QAM256 2 483000000 Hz -7.9 dBmV 36.6 dB 555376 276442 4 Locked QAM256 3 489000000 Hz -8 dBmV 36.4 dB 560070 294795 5 Locked QAM256 4 495000000 Hz -8.3 dBmV 36 dB 520901 340358 6 Locked QAM256 5 501000000 Hz -8.2 dBmV 36.1 dB 549395 341035 7 Locked QAM256 6 507000000 Hz -7.7 dBmV 36.5 dB 557724 264814 8 Locked QAM256 7 513000000 Hz -7.4 dBmV 36.7 dB 544604 241135 9 Locked QAM256 8 519000000 Hz -7.7 dBmV 36.3 dB 434768 201082 10 Locked QAM256 9 525000000 Hz -8 dBmV 36 dB 552281 308195 11 Locked QAM256 10 531000000 Hz -7.7 dBmV 36.2 dB 465406 198404 12 Locked QAM256 11 537000000 Hz -7.2 dBmV 36.6 dB 341988 135831 13 Locked QAM256 12 543000000 Hz -7.1 dBmV 36.8 dB 414254 140675 14 Locked QAM256 13 549000000 Hz -7.5 dBmV 36.5 dB 343907 135027 15 Locked QAM256 14 555000000 Hz -7.5 dBmV 36.3 dB 341546 133488 16 Locked QAM256 15 561000000 Hz -7.2 dBmV 36.6 dB 419187 141379 17 Locked QAM256 16 567000000 Hz -6.7 dBmV 37 dB 334769 128262 18 Locked QAM256 17 573000000 Hz -6.7 dBmV 37 dB 333675 125226 19 Locked QAM256 18 579000000 Hz -7.1 dBmV 36.6 dB 334444 124520 20 Locked QAM256 19 585000000 Hz -7.1 dBmV 36.5 dB 325055 119254 21 Locked QAM256 20 591000000 Hz -6.7 dBmV 36.9 dB 321761 114239 22 Locked QAM256 21 597000000 Hz -6.3 dBmV 37.2 dB 317518 112805 23 Locked QAM256 22 603000000 Hz -6.5 dBmV 37 dB 312952 101463 24 Locked QAM256 24 615000000 Hz -6.8 dBmV 36.7 dB 316569 111807 25 Locked QAM256 25 621000000 Hz -6.2 dBmV 37.2 dB 310122 106051 26 Locked QAM256 26 627000000 Hz -6 dBmV 37.4 dB 311419 106315 27 Locked QAM256 27 633000000 Hz -6.6 dBmV 36.8 dB 311586 106742 28 Locked QAM256 28 639000000 Hz -7 dBmV 36.6 dB 308545 103140 29 Locked QAM256 29 645000000 Hz -6.7 dBmV 36.8 dB 308494 103027 30 Locked QAM256 30 651000000 Hz -6.4 dBmV 37.1 dB 299392 98087 31 Locked QAM256 31 657000000 Hz -6.6 dBmV 37 dB 294912 94388 32 Locked QAM256 32 663000000 Hz -7.1 dBmV 36.4 dB 299360 97115 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 5 5120 Ksym/sec 36000000 Hz 46.8 dBmV 2 Locked ATDMA 6 5120 Ksym/sec 29000000 Hz 46.5 dBmV 3 Locked ATDMA 7 5120 Ksym/sec 22000000 Hz 45.5 dBmV 4 Locked ATDMA 8 2560 Ksym/sec 16000000 Hz 43.8 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0 ,1 ,2 33 764000000 Hz -7.0 dBmV 34.8 dB 1108 ~ 2987 1811781687 1803497951 1361818 2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV I thought I should get a second opinion cause it seems they keep telling me the same thing and nothing else when ever I contact them. They've replaced cables going to my house, cables inside my house, I replaced my own equipment, I've done basically everything I can do and have tried so many different troubleshooting methods. I'm not for sure if I'm ever going to get it fixed unless I can get some insight.
You are getting packet loss, which means there are uncorrectable errors. These can come in big groups sometimes but it looks fine for a while. Just leave your constant ping test running to the first router at the internet provider's end. Generally, you will see some errors, but they usually change so slowly that the numbers don't seem to move much. I'm not sure if the modem updates these numbers often enough anyway. Unless the modem has been on for a very long time, you shouldn't have that many errors right now. The no ranging response messages mean the ISP side isn't receiving your request or your modem isn't getting an answer back. In some cases, the ISP's equipment just doesn't respond at all, but more often it is because those messages are being damaged and dropped before they get through. Sometimes, those configuration settings might also be a problem. This is part of what the ISP sends to your modem. It could be that there is an issue with how you set up your account or maybe the modem's setting doesn't match what the ISP supports, which could be normal. That kind of thing only someone at the ISP who can actually look inside their equipment would know for sure. Most times if the modem sees errors, the ISP equipment also shows them.
I talked to a senior support guy and he said he saw drop-offs but no packet loss. That doesn't make sense at all. It's an intermittent problem, but anything that needs a steady connection like gaming, streaming or video pre-loading should work fine if there is no packet loss. This makes me think the issue might be in their own gear rather than mine. They don't see any problems with my neighbors' setups either. I really doubt that. But they always blamed me for having broken things instead of blaming themselves. I'm going to let them know this when an experienced field tech comes out from our local office. I don't know who this person is yet, but it could be one of the guys I already met who have more experience.
Here are some quick thoughts to check out:
1) Is the coax coming straight from the ISP okay? Has the ISP also installed new splitter cables at places where they were used? A splitter is basically one cable going into a wall, then 2, 3, or 4 other cables going out to power different stuff.
2) Are there any unused coax cables, wall jacks, or splitter ports that are actually connected properly? I mean with a real terminator cap instead of just a "dust cap". Just for clarity: https://blog.solidsignal.com/tutorials/t...sed-ports/
3) Has the electrical socket and/or circuit testing the power to my modem and router been checked for any problems?
4) You talked about "house." Are you in a stand-alone home or somewhere where people know nothing else has tapped into your ISP services?
5) Many of the error messages mention MAC 's. Can you match those MAC addresses to specific devices on your network? c8:9e:43:e7:ae:08 is a NetGear device - that would be expected. Which one are you talking about? 00:17:10:aa:8d:13 = Casa Systems, Inc.? ??? Source: https://macvendors.com/
There are lots of things that can make this happen. It could be broken gear or noise from a neighbor's house nearby. People who hook up Modem without filters often cause trouble, like that. The issue is simple: the ping command sends too little traffic and errors show up only when there is load. Maybe you try downloading from Steam but slow your speed to half what you pay for. Then run the ping and check if packet loss happens. You can fix this by taking your cable modem and plugging it straight into the wire that goes into your house. Best if you disconnect everything else and just hook that wire directly to the modem. Since you have changed the modem, there is very little in your home that could be the problem; it must be with the ISP. The ISP has to admit they have some issue making those uncorretteable errors happen. That is not a normal thing. Mine gets maybe 20-30 Mbps total each week on all channels combined...then again, my cable is my backup internet so there is very little traffic going through it.
1.) The internet service provider put new splitters there. There is one inside a small, abandoned building on my property. I'm not sure why they installed all the electrical stuff there, but yeah, the ISP and electricians work in that area. And another one is inside a plastic box on my house. All other coax cables are only used for TVs in the living room and the bedroom. The rest of the connection is done through wifi. But we are soon going to leave cable and start streaming. So I need this fixed right now.
2.) The splitter ports aren't sure where they go, and unused coax cables aren't sure either. There might not be any extra wall jacks left that aren't being used. I know I have a coaxial cable hanging in my room that isn't working, and I think there are a few more throughout the house like this one started 2 months ago when I got my own equipment. And it is still happening after getting new "recommended" equipment.
3.) No, as far as I know, the power hasn't been checked yet. I'll get that checked right now when they come out today.
4.) Yes, I live outside the city but close enough for high speeds since there is an industrial park and a shopping district just a mile away from me. It's weirdly divided into lines, but I don't think that causes any problems.
5.) The first one is the modem. The second one doesn't look like it belongs here because Casa Systems sells networking devices for ISPs and cellular networks, which makes sense for them using it, but not why they show up on my end. Could that be the reason for my connectivity issues?
Where exactly do the first splitter or amplifier sit? It's way too far away from my house to reach with a wire, and this old building where we used to live isn't connected to anything right now. That place is only a few feet across the street and it belongs to us—we own it! Basically, the cable starts at the pole on the other side of the street and runs directly to our home. Then it goes into that abandoned house through an unconnected box I don't know what's inside (I guess it might be an amplifier). From there, it connects back to my house via a splitter I think, then another coax cable wraps around our house all the way to the front wall where the cable meets the wall jack. That is where my modem is plugged in. There isn't any power coming out here either, and honestly, even if I tried running tests right now on this specific issue, it probably wouldn't work because it's too complex for me to test with just a few simple steps. I think the problem lies with the Casa System since it keeps throwing misconfiguration errors. But remember, that system is owned by the ISP, so no matter what I try, they won't fix it anyway.
A power amplifier needs power. Maybe you could add a grounding block, or even a filter that stops bad signals from getting into the internet line (ISP). Now your problem is you think it might be their box, but they say everything is fine. You need to prove something's wrong with theirs so they have to fix it. The goal is to make this as easy as possible. If you could plug in two computers directly to the wire where it comes into your yard, they'd have to admit there was an issue with their setup. Of course, you can't just hook a computer straight into coax cable, but using fewer splitters or extra cables helps. You are basically doing some of their job for them, but if you want this fixed in a reasonable time, you likely need to do the work yourself. It might actually be as simple as there being a poor connection inside your house. It doesn't take much for a cable to just be loose, or maybe dirt is getting into a connection.
Seconding what you said. An amplifier without power adds no value, so it could be part of the problem. Abandoned buildings are a bad idea because there might be animals living in them with nests, chew marks, and lots of dirt and mess. That is not good. Unfortunately, you have to do as much as possible to figure out what infrastructure exists right now. Make sure to be safe: no climbing on roofs or poles. Use a bright flashlight to look for hard bends, kinks, pinches, nail or staple damage, corrosion, or chewed cables.
If you find two coax spliters but see three wires coming out of them downstream, there might be another splitter hidden somewhere. It could be a barrel connector that is corroded and causing trouble. Check what is printed on the cables; they should look the same on both ends if the cable is visible. Cables often have distance markings. Write down these marks and note the actual distances involved. Maybe the wrong type of cable was installed somewhere, or there is another component involved.
Check wall outlets and those small plastic boxes. They can be great hiding spots for critters or places where moisture accumulates. Problems get worse during damp weather or if there is direct heat from the sun nearby. Most people quickly turn these tiny houses into a mess of tangled wires after too much time without cleaning them up properly. Labeling is often missing or unreadable anyway. Start with a simple diagram showing all those locations, cables, splitters, and connections. It doesn't need to be fancy art; just clear enough to show everything present and where it connects. Don't leave any unknowns behind at least make sure to note something that looks wrong.
Start by testing with the simplest and easiest connections possible. Find which part works, then add in other cables and components until you see if the problem comes back when things are removed. This helps determine exactly when, where, or why the issues happen. In general, I think the problem is infrastructure-related and likely intermittent. Technicians often fix one thing while a different part gets broken later because they leave without testing everything thoroughly. To be fair to them, they face great pressure to solve problems quickly. So yes: "you must do the work." Unfortunately, more people are doing this now than before.
It's definitely your internet provider's fault. Back when my temp got cold enough to freeze, I had problems for years after many calls, lots of blame games from my gear, and three whole years of tech visits finally getting things fixed. The ground near me would get super cold and expand. This made buried cables twist up so hard that the equipment at the node got hurt, which messed up my service. I was seeing millions of codes that could be fixed or not, tons of T3-T4 timeouts, and modem restarts. But recently, when I moved places with the same company and gear, everything has been super reliable. I checked the logs yesterday and there were no single fixable or unfixable errors at all. So basically, ISPs don't care about you anyway, most tech guys are just dumb, and they don't even care either.