Packet loss caused by graphics card

[jknowles1]

Has anyone else had a problem with their graphics card causing packet loss inside their network? Got off the phone earlier with a rep that claimed this was my problem.

Tech called back later asking me to tweak some MTR settings and the packet loss showed up 20mins later.

[smith6612]

Perhaps if there is a nasty driver problem or a chipset issue on your motherboard (nForce board?), but I have personally never seen this. Where exactly are you seeing this packet loss?

[jknowles1]

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| verizon.home - 0 | 1111 | 1111 | 0 | 0 | 8 | 0 |
| 10.28.11.1 - 14 | 637 | 550 | 0 | 546 | 4782 | 25 |
| 100.41.133.16 - 14 | 640 | 552 | 0 | 530 | 4788 | 27 |
| 130.81.163.52 - 14 | 631 | 543 | 0 | 576 | 4797 | 32 |
| 0.xe-7-0-3.XL4.IAD8.ALTER.NET - 14 | 633 | 545 | 0 | 557 | 4823 | 31 |
| 0.xe-10-0-1.BR1.IAD8.ALTER.NET - 14 | 637 | 549 | 0 | 542 | 4791 | 31 |
| 192.205.36.137 - 14 | 633 | 545 | 0 | 555 | 4796 | 33 |
| cr82.wshdc.ip.att.net - 15 | 622 | 533 | 0 | 639 | 4872 | 101 |
| cr2.wswdc.ip.att.net - 15 | 616 | 525 | 0 | 638 | 4869 | 104 |
| cr1.wswdc.ip.att.net - 16 | 619 | 526 | 0 | 610 | 4868 | 94 |
| cr2.dlstx.ip.att.net - 15 | 622 | 531 | 0 | 622 | 4877 | 104 |
| cr1.dlstx.ip.att.net - 15 | 624 | 534 | 0 | 622 | 4871 | 100 |
| cr1.phmaz.ip.att.net - 15 | 620 | 529 | 0 | 625 | 4866 | 99 |
| 12.123.158.5 - 15 | 622 | 533 | 0 | 645 | 4861 | 93 |
| 12-122-254-218.attens.net - 68 | 291 | 95 | 0 | 873 | 4667 | 275 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| Destination host unreachable. - 100 | 223 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[jknowles1]

http://asrock.com/mb/Intel/H61M-VS/index.us.asp?cat=Download&os=Win7

This is my motherboard. Don't see anything reffering to chipset driver in the downloads section.

[MyEye]

Neither do I, but I have heard of this happening (a long while ago) on another forum.

Just tried a google search on your topic (below) and it yields some interesting results, at least in terms of trying to understand what my be happening re: your specific card.   Can't hurt to take a look make some inquiries ...

"WinMTR v0.92 GPL V2 by Appnor MSP causing network packet loss"

JK

[jknowles1]

I'm sorry... do I understand correctly that you are suggesting WinMTR is causing the packet loss?

[smith6612]

They are just joking.

The loss is occurring beyond your router. You have no loss to your router, which is indicative that your motherboard is not to blame. Your PC might still be to blame if there is something running on the system that is causing some problems.

These are the three lines to focus on.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host -                     % |  Sent | Recv | Best | Avrg | Wrst | Last |

verizon.home -        0 | 1111 | 1111 |      0 |       0 |        8 |     0 |
10.28.11.1 -           14 |    637 |   550 |      0 |  546 | 4782 |   25 |
100.41.133.16 -    14 |    640 |   552 |      0 |  530 | 4788 |   27 |

10.28.11.1 is the Gateway on Verizon's end that you connect up to. Between "Verizon.home" and 10.28.11.1 this involves your DSL modem (from the modem portion if you have one of those all-in-one gateways), the DSLAM, all copper wiring outside, and the aggregate network inside of the Central Office.

Since your latency is also pretty bad, you might be running into a couple of issues which Verizon will need to sit down and think about. Some of which, you'll need to think about too.

• This latency could be caused by traffic on your network. If your Wi-Fi is not secured with WPA2, secure it to WPA2. If you have P2P software, streaming, cameras, cloud backups, etc running, this could be causing some issues as well. Check to make sure, during times of packet loss and activity, that the lights on your router are not flashing quickly, except for when you are running ping tests/MTR. If you can rule out network activity, you rule out the problem being on your end, mostly.

• Perhaps your line quality is bad. If you have an ActionTec Gateway, please try to share your modem's Transceiver Statistics with us. They can be found by visiting http://192.168.1.1/ , followed by cliking on "Stauts" and then "DSL Status". You should see a page showing information such as Attenuation, SN Margin, your speed, and your line mode. Please copy/paste this information into a post. Now, if you have a D-Link Gateway from Verizon, there is no known way to getting information from these to my knowledge. We will have to use Verizon's best judgement.

• If your Transceiver Statistics look good, you can confirm that the latency and loss is not due to traffic at your home, then this is a Verizon problem. Verizon will need to have their MCO group check your circuit for congestion, and rebuild it if there are any signs. Congestion is commonly seen during the evening hours, to a lesser extent during "non-peak" hours such as very late at night, or in the morning hours.

• If Congestion is not the problem, then there is likely faulty equipment out in the field or somewhere in the CO. Often, checking with neighbors can help to rule out this kind of a problem, but not always. Sometimes, the problem is just with the line card you are attached to on Verizon's end. A field technician can help swap this if it's found to be bad.

So the TL;DR of this is - it's Verizon's problem most likely, but please make sure that this is not due to traffic on your network. Use the information provided above to figure out how to go about resolving this.

I'll provide some more support information that can give you a hand once we can determine what the problem is.