Keoway
Premium
join:2009-08-29
Seneca, SC
|  Corrected blocks going through the roof!
2Wire States |
Corrected Blocks: 777889401 52971916 2104197 0:00:01
Do I need to be concerned about this error rate?
They seem to be relentless and don't seem to be stopping, but so far the video looks fine this evening. |
|
btur389w
join:2009-09-22
| Yes.
Keoway, my name is Bobbie, I am from Uverse Tier 2 Technical Support, and I look for members like you who have not found traditional methods of resolution. We would love to assist you, if you could email your Billing Account Number (BAN) and a good contact number so we can look into this issue for you.
Our email is UverseCare@att.com
Thanks,
UVerse Care
--
If you have any questions or concerns, please feel free to email us at uversecare@att.com.
Our goal is to provide you Excellent Customer Service. Hours: Tu-Sa 12-9 CST |
|
Keoway
Premium
join:2009-08-29
Seneca, SC
| Now up to 61 million for the 24 hour interval.
Speedtest still looks good at 11.39/1.43 for a 12M service tier. The video also remains good this evening with no instances of picture freezes or pixellation, so far ...
[Email with BAN and VOIP sent.] |
|
Tanshin
join:2009-07-18
West Simsbury, CT | Just a small thing you can check (I had an instance like this a while back). Find the jack from where your Homerun comes and give the keystone side a squeeze.
When I did that it made the spikes stop. |
|
Keoway
Premium
join:2009-08-29
Seneca, SC | Could you define "keystone side"? |
|
Keoway
Premium
join:2009-08-29
Seneca, SC
1 edit | reply to Tanshin
Google sometimes works wonders, when the terms are right 
I don't have a Keystone implementation. The Prem Tech augmented the existing wiring with a Cat5 extension directly to the RG.
Photo's here of "before" and "after" the Prem Tech visit:
»MDU NID: Do old ones present any challenges? |
|
Tanshin
join:2009-07-18
West Simsbury, CT | Hmmm... never seen a non-keystone method of doing that.
That's all I can really think of (based off experience). I guess we'll just have to wait and see for now. |
|
zvogt
@sbcglobal.net
| reply to Keoway
I see a lot of threads here of people questioning the volume of corrected blocks as assuming that is the cause of whatever their symptom is. I just don't think that's true. My numbers have always shown about 500,000,000 corrected blocks in the last 24 hours and zero uncorrected blocks. And I personally watch more than 50 hours of television each and every week. And I wouldn't say that I've "never" seen a blip or two of pixelization, but I would say that it's "almost never". My point is, I just don't think that the two events equate to each other in any way. I think the corrected blocks are just a fact of life, and by themselves are not indicative of anything wrong. |
|
MSeng
Premium,Ex-Mod 2001-08
join:2000-07-13
Ork
clubs:
 ·AT&T U-Verse
 ·AT&T Midwest
1 edit | reply to Keoway
I had an identical problem a few weeks ago -- up until that point my connection was pretty much rock solid and trouble free.
After doing a little research in this forum on the issue, I found where others experiencing the problem cleared it by rebooting the RG. Lo and behold, it worked for me too.
I would suggest you give it a shot. Certainly can't hurt. 
--
If things get any worse, I'll have to ask you to stop helping me. |
|
gdm
Premium,MVM
join:2001-06-15
Mchenry, IL
clubs: | reply to zvogt
Sorry but that many corrected blocks in 24 hours is a problem. You shouldn't have anywhere near that many. |
|
Keoway
Premium
join:2009-08-29
Seneca, SC
| reply to MSeng
Can't be offline during baseball
The current numbers:
Corrected Blocks: 803219732 78302247 1860495 0:00:00
Uncorrectable Blocks: 5075 303 0 0:23:05
Note: The RG has never been rebooted. My install was on 10/15 and the box has been live, since the Prem Tech brought it on-line. |
|
MSeng
Premium,Ex-Mod 2001-08
join:2000-07-13
Ork
clubs:
·AT&T U-Verse
·AT&T Midwest
| I understand (go Phillies).
For what its worth, when I had the problem it was the first and only time I did a manual reboot since my install in late November, 2008.
--
If things get any worse, I'll have to ask you to stop helping me. |
|
Keoway
Premium
join:2009-08-29
Seneca, SC | Indeed! In honor of all the Cullinet support folks that used to be based at Scott II Plaza, the Phillies get my support |
|
Keoway
Premium
join:2009-08-29
Seneca, SC
| reply to Tanshin
said by Tanshin  :Hmmm... never seen a non-keystone method of doing that. My Prem Tech was from Saginaw, Michigan and helping with my area's huge backlog of installs. |
|
Tanshin
join:2009-07-18
West Simsbury, CT
·AT&T U-Verse
| Once the game is over (I really hate Baseball so... I'll just ignore those discussions ), I would give it a reboot.
Have you gotten the firmware update? If you have a 3800HG-V (which I believe everyone has), you would have software version 5.29.135.47. The previous version was 5.29.115.xx or 5.29.105.xx or something. |
|
aturner733
join:2003-08-28
Saint Louis, MO
| reply to Keoway
I too have had the corrected blocks go through the roof, the other day before I rebooted I was almost at a total of 1 billion and most of those happened within a few days.
After reboor everything seems fine for a while then something caused them to go crazy again. I have had several techs out and they all have done different things.
I can't really say though that the corrected blocks are causing picture problems as of yet. I have only had service for a month. I have noticed some freezing and pixelation but that could be the DVR also.
Like others have said try a reboot and see what happends. |
|
Keoway
Premium
join:2009-08-29
Seneca, SC
| reply to Tanshin
said by Tanshin : ... Have you gotten the firmware update? If you have a 3800HG-V (which I believe everyone has), you would have software version 5.29.135.47. The previous version was 5.29.115.xx or 5.29.105.xx or something. I have 5.29.105.94 on a 3800HGV-B Gateway.
I rebooted to try and get some runs ...
Here are the stats after being back on-line for 30 minutes:
Cumulative Seconds w/Errors: 5 5 5 0:03:01
Cumulative Sec. w/Severe Errors: 0 0 0 0:00:00
Corrected Blocks: 23089 23089 18847 0:01:06
Uncorrectable Blocks: 6 6 6 0:03:01
DSL Unavailable Seconds: 284 284 0 0:24:12
Yikes! It's quite daunting to see the RG lights dance between red to green and back to red then green and cycle back around several times indicating no Broadband!
Whoa, no video, no broadband, and no VOIP until the lights turn the right shade of green |
|
Tanshin
join:2009-07-18
West Simsbury, CT | Yeah, that was fixed in the firmware update. They now boot successfully in about one minute (the red-green-red... pattern was a pain before).
But they are still climbing pretty fast after the reboot. |
|
zvogt
@sbcglobal.net
| reply to gdm
said by gdm :Sorry but that many corrected blocks in 24 hours is a problem. You shouldn't have anywhere near that many. I'm not sure I understand what you're saying. I've had U-Verse service a little over year. My first gateway probably was reset multiple times over that first year. I recently got a new gateway when the first one catastrophically failed. But in all that time, on both pieces of hardware, I've never seen my number of UNcorrected be more than a single digit number. But despite the numbers, I've also never have had a problem with the picture on my TV service. I'm not sure I understand why the numbers themselves have any inherent value (positive or negative) given that I'm not having any negative side-effects. Clearly the technology is still capable of performing as expected independent of those statistics. If I wasn't nosy, and looking at that 2Wire diagnostic page, I would never even have known that the hardware is doing all these"corrections". I'm just really having a hard time understanding how you can label it as a "problem". |
|
Tanshin
join:2009-07-18
West Simsbury, CT
·AT&T U-Verse
| said by zvogt :said by gdm :Sorry but that many corrected blocks in 24 hours is a problem. You shouldn't have anywhere near that many. I'm not sure I understand what you're saying. I've had U-Verse service a little over year. My first gateway probably was reset multiple times over that first year. I recently got a new gateway when the first one catastrophically failed. But in all that time, on both pieces of hardware, I've never seen my number of UNcorrected be more than a single digit number. But despite the numbers, I've also never have had a problem with the picture on my TV service. I'm not sure I understand why the numbers themselves have any inherent value (positive or negative) given that I'm not having any negative side-effects. Clearly the technology is still capable of performing as expected independent of those statistics. If I wasn't nosy, and looking at that 2Wire diagnostic page, I would never even have known that the hardware is doing all these"corrections". I'm just really having a hard time understanding how you can label it as a "problem". You may have an issue past the router, eg in your LAN. |
|
