user1323232's profile

New Poster

 • 

13 Messages

Tuesday, February 25th, 2020 3:00 PM

Closed

uncorrectble errors

so when i upload to google drive or any other upload intesive service it tends to tank my ping to well over 200ms from the usual 10-20. im on the XB6-T modem.recently my modem racked up well over 34 million uncorectble errors in 4 days. then when i restart the modem , for the last 2 hours very few uncorrectbles show up. i made a tech appointment for satuday as those errors looked concerning. the prevailing issue right now is the downstream snr is i few below the minimum on 2 chanels. im just wondering if i actually do have an issue or if it was just a fluke with the 34 mill errors on one chanel and i should just cancel the tech visitDownstreamDownstreamDownstreamDownstreamDownstreamDownstreamDownstreamDownstreamDownstreamDownstreamupstreamupstreambefore rebootbefore reboot

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

Expert

 • 

111.4K Messages

5 years ago

Can't see your pics. Since you are a new poster, they need to be approved by a Forum Admin. That could take some time. In the interim, you could try hosting them at one of those free third-party pic hosting sites like Imgur or Photobucket and post the link to them here.

New Poster

 • 

13 Messages

5 years ago

didnt mean to post the samelink twice

New Poster

 • 

13 Messages

5 years ago

Expert

 • 

111.4K Messages

5 years ago

Yes, there are a couple of downstream channels with low SNR's, but with all of the redundancy, I don't think that they can cause that much damage. YMMV.

 

So with the way that the TCP protocol works, all of the packets need to be acknowledged (TCP ACK) back to the sender. So if you saturate the upstream / return path, and it is full, acknowledgment packets get queued up and most of them time out and slowly return to the sending server. The server assumes failure and resends the same data. The resending of packets on the downstream / forward path will suffer. The symptom manifests itself as excess latency.

Contributor

 • 

44 Messages

4 years ago

I have been seeing a ton of uncorrectables and have had a lot of intermittent latency.  Modem is an SB8200.  Xfinity checked my lines today and area nodes and found all to be good. The did find a loose 75 ohm terminator on my splitter and they removed my splitter and just used an inline connector instead.  Note that I have only internet and not cable or phone.

See my modem logs below.  What can be done about the uncorrectables?

Connection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 507000000 Hz 4.3 dBmV 43.0 dB 2909 4218
2 Locked QAM256 489000000 Hz 4.0 dBmV 43.0 dB 2722 6067
3 Locked QAM256 495000000 Hz 4.2 dBmV 43.0 dB 3804 8867
4 Locked QAM256 501000000 Hz 4.3 dBmV 43.0 dB 3780 8261
6 Locked QAM256 513000000 Hz 4.3 dBmV 42.9 dB 2551 6374
7 Locked QAM256 519000000 Hz 4.3 dBmV 42.8 dB 3095 8214
8 Locked QAM256 525000000 Hz 4.2 dBmV 42.8 dB 2777 6868
9 Locked QAM256 531000000 Hz 4.2 dBmV 42.8 dB 4556 8132
10 Locked QAM256 537000000 Hz 4.3 dBmV 42.8 dB 2795 6626
11 Locked QAM256 543000000 Hz 4.2 dBmV 42.9 dB 2880 7479
12 Locked QAM256 549000000 Hz 4.2 dBmV 42.9 dB 3078 8080
13 Locked QAM256 555000000 Hz 4.2 dBmV 42.7 dB 3000 7563
14 Locked QAM256 561000000 Hz 4.2 dBmV 42.5 dB 3025 8410
15 Locked QAM256 567000000 Hz 4.1 dBmV 42.5 dB 3453 8516
16 Locked QAM256 573000000 Hz 3.9 dBmV 42.4 dB 2980 8123
17 Locked QAM256 579000000 Hz 3.9 dBmV 42.2 dB 4398 11374
18 Locked QAM256 585000000 Hz 3.9 dBmV 42.5 dB 3340 8608
19 Locked QAM256 591000000 Hz 3.7 dBmV 42.2 dB 3005 8229
20 Locked QAM256 597000000 Hz 3.7 dBmV 42.2 dB 2927 8666
21 Locked QAM256 603000000 Hz 3.8 dBmV 42.3 dB 3343 8431
22 Locked QAM256 609000000 Hz 3.5 dBmV 42.1 dB 4381 8403
23 Locked QAM256 615000000 Hz 3.4 dBmV 42.0 dB 3837 7748
24 Locked QAM256 621000000 Hz 3.5 dBmV 42.1 dB 3739 7895
25 Locked QAM256 627000000 Hz 3.4 dBmV 42.1 dB 3719 7768
26 Locked QAM256 633000000 Hz 3.4 dBmV 41.9 dB 3537 7568
27 Locked QAM256 639000000 Hz 3.3 dBmV 42.0 dB 3558 7714
28 Locked QAM256 645000000 Hz 3.3 dBmV 41.9 dB 3713 7673
29 Locked QAM256 651000000 Hz 3.3 dBmV 42.0 dB 4044 10326
30 Locked QAM256 657000000 Hz 3.1 dBmV 41.9 dB 4146 8279
31 Locked QAM256 663000000 Hz 3.2 dBmV 41.9 dB 4182 8292
32 Locked QAM256 669000000 Hz 3.1 dBmV 42.0 dB 4246 7723
33 Locked Other 690000000 Hz 3.5 dBmV 40.5 dB 825534217 909



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 37.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 37.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 37.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 37.0 dBmV
5 5 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 37.0 dBmV



Current System Time: Fri Mar 26 12:05:32 2021

Expert

 • 

111.4K Messages

4 years ago

At user_cd429e

Please create a new topic of your own here on this board detailing your issue (copy and paste your post above). Thanks.  Year old dead now being closed.

forum icon

New to the Community?

Start Here