New
#81
Well, it's evident there looks to be some major malfunctioning of the TCP stream. The wireshark logs show a lot more explicit evidence of this. It looks like huge bursts of TCP retransmitting of packets. The first log with the download of Windows update file showed a TCP stream lasting 7 seconds, then a sudden gap of 31 seconds during the TCP stream and then an immediate retransmission of the packets afterwards. Then it goes for another 17 seconds with a few mass retransmissions then there's a 65 second gap and another mass retransmission.
Wireshark is having problems analyzing the TCP stream properly because every single TCP ACK packet appears to have a zeroed checksum. Often this is because of a feature on NICs called Checksum Offloading. You can turn it off by typing "view network connections" in Start Menu then right-clicking and going to Properties for your associated network adapter, then click the "Configure" button and then mosey on over to the Advanced tab. There should be an option called TCP Checksum Offload, which you can then set to disable.
Anyways, I reaaaally doubt we're dealing with some misbehaving program here. You should start by uninstalling and reinstalling your network drivers with the latest available version from your mobo's manufacturer (make sure to download your network drivers first before uninstalling them!). If that does not work, you may need to cough up some dough for a cheap NIC then connect through that and test connectivity. We could very well be dealing with a failing network controller here.
If you wish to make another run of Wireshark with Checksum Offloading disabled, I highly recommend you run both wireshark and xperf simultaneously. Only capture the download before it starts and then stop after it hangs for a bit. Stop the logging before you stop the download.
That should most likely be our final run of logs for this.