f2bme's profile

Contributor

 • 

19 Messages

Monday, January 30th, 2023 5:26 PM

Closed

Motorola MT8733 Randomly Reboots

For about the past 2 to 3 weeks I have been experiencing almost daily restarts of my modem/router.  The modem router model is a Motorola MT8733 (approved by comcast).  To get started, here is a post of the event log [Note: CM-MAC and CMTS-MAC info removed].

Event Log

   Event Log

 


  

   

Time 

 

Priority 

 

Description 

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

23:53:48
Thu Jan 26 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

16:37:01
Fri Jan 27 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

01:34:02
Sat Jan 28 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

01:34:02
Sat Jan 28 2023

 

Critical(3)

 

SYNC Timing Synchronization failure - Loss of Sync; CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

05:35:52
Sat Jan 28 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

17:14:05
Sat Jan 28 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

20:52:14
Sat Jan 28 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

02:26:47
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:38
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

08:28:18
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:38
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

11:37:33
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

15:01:46
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:40
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

19:56:10
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:38
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

   

21:50:53
Sun Jan 29 2023

 

Notice(6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

   

19:00:31
Web Dec 31 1969

 

Critical(3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

19:00:39
Web Dec 31 1969

 

Notice(6)

 

Honoring MDD; IP provisioning mode = IPv6

I've tried restarting the modem multiple times via the xfinity troubleshooting app as well as powering it down and restarting it via the power plug. No apparent cable damage nor unnecessary/defective splitters.  Any help would be greatly appreciated.  Will post other info, if needed.

Thanks!

This conversation is no longer open for comments or replies and is no longer visible to community members.

This post was created from this comment on different post

Expert

 • 

110.3K Messages

2 years ago

Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

Contributor

 • 

19 Messages

2 years ago

@EG  Thank you for your response.  Here is the information you requested.

 Downstream Bonded Channels

 


  

   Channel

Lock Status

Modulation

Channel ID

Freq. (MHz)

Pwr (dBmV)

SNR (dB)

Corrected

Uncorrected

   1

Locked

256 QAM

4

447.0

-3.1

42.1

2

0

   2

Locked

256 QAM

1

429.0

-2.9

42.2

1

0

   3

Locked

256 QAM

2

435.0

-3.0

42.1

2

0

   4

Locked

256 QAM

3

441.0

-2.9

42.1

2

0

   5

Locked

256 QAM

5

453.0

-3.4

42.0

2

0

   6

Locked

256 QAM

6

459.0

-3.3

42.0

5

0

   7

Locked

256 QAM

7

465.0

-3.1

42.0

2

0

   8

Locked

256 QAM

8

471.0

-3.0

42.1

4

0

   9

Locked

256 QAM

9

477.0

-2.9

42.1

2

0

   10

Locked

256 QAM

10

483.0

-3.5

41.8

4

0

   11

Locked

256 QAM

11

489.0

-3.8

41.8

4

0

   12

Locked

256 QAM

12

495.0

-3.5

41.9

3

0

   13

Locked

256 QAM

13

507.0

-3.5

41.8

9

0

   14

Locked

256 QAM

14

513.0

-3.5

41.9

7

0

   15

Locked

256 QAM

15

519.0

-4.1

41.7

4

0

   16

Locked

256 QAM

16

525.0

-4.3

41.5

6

0

   17

Locked

256 QAM

17

531.0

-4.3

41.5

6

0

   18

Locked

256 QAM

18

537.0

-4.2

41.6

2

0

   19

Locked

256 QAM

19

543.0

-4.2

41.5

7

0

   20

Locked

256 QAM

20

549.0

-3.9

41.6

6

0

   21

Locked

256 QAM

21

555.0

-4.3

41.5

12

0

   22

Locked

256 QAM

22

561.0

-4.7

41.2

10

0

   23

Locked

256 QAM

23

567.0

-4.7

41.2

10

0

   24

Locked

256 QAM

24

573.0

-4.8

41.1

8

0

   25

Locked

256 QAM

25

579.0

-4.9

41.1

11

0

   26

Locked

256 QAM

26

585.0

-4.8

41.2

15

0

   27

Locked

256 QAM

27

591.0

-5.0

41.3

13

0

   28

Locked

256 QAM

28

597.0

-5.2

41.0

13

0

   29

Locked

256 QAM

29

603.0

-5.4

40.8

17

0

   30

Locked

256 QAM

30

609.0

-5.8

40.6

22

0

   31

Locked

256 QAM

31

615.0

-5.9

40.6

21

0

   32

Locked

256 QAM

32

621.0

-5.8

40.6

15

0

   33

Locked

OFDM

193

702.0

-6.6

39.7

15602495

0



   Upstream Bonded Channels

 


  

   Channel

Lock Status

Channel Type

Channel ID

Symb. Rate (Ksym/sec)

Freq. (MHz)

Pwr (dBmV)

   1

Locked

SC-QAM

1

5120

35.6

51.5

   2

Locked

SC-QAM

2

5120

29.2

50.8

   3

Locked

SC-QAM

3

5120

22.8

50.5

   4

Locked

SC-QAM

4

5120

16.4

52.0

 

Thanks for your help!

Expert

 • 

110.3K Messages

2 years ago

The upstream power levels are too high to being out of spec. The downstream power is on the weak side as well. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

Contributor

 • 

19 Messages

2 years ago

Could the picture below explain the reason for my lousy signals and power levels posted earlier?  This is the splitter that the Comcast Tech installed in Nov 2020, when I first moved in and established service here.   It is a 3-way balanced splitter, all -5.5dB.  One leg goes directly to the MT8733, and the other 2 go to TV boxes.  I've always thought that the one going directly to the modem was supposed to be a different dB level than those going to TVs.

 

Contributor

 • 

340 Messages

Hello @f2bme We appreciate you reaching out to bring the trouble you are experiencing with your internet to our attention. It is possible that the splitter can degrade the signal. I'd like to check your signal levels. Can you please send our team a direct message with your full name and full address?

I no longer work for Comcast. 

Contributor

 • 

19 Messages

@XfinityYvonne Thank you.  I will send a DM with the information you requested.  

Problem Solver

 • 

546 Messages

@f2bme  We look forward to assisting you 😀

I no longer work for Comcast.

Expert

 • 

110.3K Messages

2 years ago

They are already indicated to be marginal..

Expert

 • 

110.3K Messages

2 years ago

@f2bme 

If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated. 


Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.


Good luck !

Contributor

 • 

19 Messages

@EG​ Thank you for your help and suggestions.  I live in a condo building (built in the mid to late 80's), so cabling infrastructure could definitely be a factor here. Incidentally, I just had another random reboot of the MT8733, but that could be due to the DM I just sent to the Xfinity reps. In any event, I'll post the outcome of this situation. 

Problem Solver

 • 

546 Messages

A great big THANK YOU to @EG and our other experts for providing AMAZING support to our customers like @f2bme, we appreciate you ❤️ 

I no longer work for Comcast.

Expert

 • 

110.3K Messages

2 years ago

My pleasure ! It's why I lurk ! 🙂

Contributor

 • 

19 Messages

2 years ago

Okay, so just to circle back around to report on updates/current status.  I have not experienced any further unexpected disconnects or random reboots of the modem/router (Motorola MT8733).  My US/DS signals and pwr levels are still only marginal to out of spec, but for some strange reason, this is not causing any problems.  My Xfinity plan is 800Mbps down and 20Mbps up.  I am consistently getting (via wired connection) 930Mbps down and 24Mbps up.  So, at this point I have no validity to complain. 

After investigating a bit, I did figure out why the signals and pwr levels are screwy (see earlier post where I provided them).  I hooked the modem router up to a coax right off of the primary main splitter that enters my condo unit.  DS/US signals and pwr levels were just about perfect.  My office, where I normally keep the router, is in a back room, enabling me to connect my PC via ethernet.  The bad news (for me, of course) is that the poor signals and pwr levels I'm experiencing in the office area are due to the cabling within my condo unit (condo was built in the mid-1980's), and therefore, I don't believe there is anything I can do about it.   

Expert

 • 

110.3K Messages

2 years ago

Thanks for the update ! You wrote: My US/DS signals and pwr levels are still only marginal to out of spec, but for some strange reason, this is not causing any problems. 

Be advised that some makes / models of modems / chipsets are more tolerant of less than stellar signals / connection quality than are others.

You wrote:

The bad news (for me, of course) is that the poor signals and pwr levels I'm experiencing in the office area are due to the cabling within my condo unit (condo was built in the mid-1980's), and therefore, I don't believe there is anything I can do about it.   

Unless there is a special arrangement, the unit owner for the inside of their unit, and the condo management for the common areas are typically responsible for the repair and maintenance of internal wiring / hardware.

(edited)

Contributor

 • 

19 Messages

2 years ago

@EG very interesting. Thanks for this information and all your help!  I'll have to check in with the Condo Association.  I'm the unit owner for my unit, but there are 3 other units within this building.  When you get into wiring, plumbing, etc., inside of walls, you're actually between units.  So, I'll see what their rules and regulations state about those responsibilities.  Thanks again! 

Expert

 • 

110.3K Messages

2 years ago

You're quite welcome ! Good luck with it ! Please post back about how things go.

Contributor

 • 

19 Messages

2 years ago

Hello, I am posting back as requested to update the situation with the Motorola MT8733 modem/router.  I am still experiencing random reboots, which occur about every 2 days.  Signal levels, etc. as posted earlier in this thread, are still about the same and I know they were borderline on being unacceptable.  I have sent a DM to Xfinity to request a tech visit to check my line signals. 

Official Employee

 • 

1.7K Messages

Thank you, @f2bme! We have received your Direct Message and will reply to you there shortly.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Expert

 • 

110.3K Messages

2 years ago

@dcf_atl 

Please create a new topic of your own here on this board detailing your issue. Thanks. The original poster has not returned. 6-month-old dead thread is now being closed.


For future reference, it is better to submit your own post as it creates a ticket to get help, and posting on an old thread can delay getting help.

Also, please re-post those error log entries there but you need to redact all of the CM MAC and the CMTS MAC addresses from them for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

And what do the modem's signal stats look like ? 

Please copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

forum icon

New to the Community?

Start Here