SB6141 rebooting 2x a day

Just wondering if someone out there can help.

Here are my logs / signals.  It's rebooting every day, sometimes 2x a day.  Most of the time when I'm not at home but I was watching Netflix the other night and it rebooted.  I have a splitter I will replace, but I wanted to see if it's something Comcast needs to investigate.  Perhaps there is a firmware upgrade? Everything else is fine when it's online.  I'm getting 27 down / 6 up roughly.  Pingtest.net shows no packet loss and very low jitter.  It gives me an A grade.

Let me know what you think.  Thanks!

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781236322090309020022
Firmware Build Time: Oct 29 2012 18:07:13

Downstream Bonding Channel ValueChannel ID 1  2  3  4  5  6  7  8  Frequency 651000000 Hz  657000000 Hz  663000000 Hz  669000000 Hz  675000000 Hz  681000000 Hz  687000000 Hz  693000000 Hz  Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB  37 dB  37 dB  37 dB  37 dB  Downstream Modulation QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 6 dBmV   6 dBmV   7 dBmV   7 dBmV   7 dBmV   7 dBmV   7 dBmV   7 dBmV  

Signal Stats (Codewords)Bonding Channel ValueChannel ID 1  2  3  4  5  6  7  8  Total Unerrored Codewords 3380874919  3379890133  3379872868  3379880939  3379865451  3379865041  3379867628  3379867130  Total Correctable Codewords 62  43  61  77  90  85  77  71  Total Uncorrectable Codewords 543  513  492  585  699  634  683  675 

TimePriorityCodeMessage Jan 24 2014 16:01:16 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 07:01:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:38 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:38 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:26 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:26 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:14 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:14 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:45:10 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:44:20 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:46 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:46 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 01:31:36 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 16:01:16 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 07:01:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:38 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:38 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:50:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:26 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:26 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:14 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:14 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:46:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:45:10 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:44:20 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:46 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:46 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 06:43:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0; Jan 24 2014 01:31:36 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:2d:35;CMTS-MAC=00:01:5c:3e:18:54;CM-QOS=1.1;CM-VER=3.0;