Problem with LAN port performance Issues affecting data transfer rates on network ports
Problem with LAN port performance Issues affecting data transfer rates on network ports
Hello everyone. The PC details are as follows: MSI B450i Gaming Plus AC equipped with 1.2.0.6c AGESA BIOS. An AMD Ryzen 1700X processor, overclocked and reduced to 3.7 GHz, paired with an MSI Armor MK2 RX 580 8 GB SSD. The graphics card was undervolted from 950 to 900 mV on the VRAM and -50 mV across all states except the first and last. It runs a 32 GB (2x16) G.Skill Ripjaws V at 3200 MHz CAS, using an EX920 M.2 NVMe SSD with 512 GB storage. The system uses Seagate FireCuda 2.5 SSHD 5400 RPM, 2 TB, and comes with a Noctua case featuring two 80 mm 4-pin fans, two 92 mm 4-pin fans, one 120 mm 4-pin fan, and a Noctua controller.
Network configuration includes a TP-Link A8, TP-Link RE550 Ugreen Cat7 flat cable. Recently, I observed websites loading more slowly than usual. After testing speed and downloading files, speeds fell from 100 Mbps to 0.20–0.35 Mbps. On Wi-Fi, download/upload remained between 90–95 Mbps. Using the cable consistently still yielded 0.20–0.50 Mbps regardless of connected device.
Several troubleshooting steps were attempted: updated ISP firmware (no improvement), reset router settings, reinstalled drivers, used built-in drivers, disabled Large Send Offload v2 on both IPv4 and IPv6, set full duplex at 100 Mbps, changed cable, tested other ports, reset network, checked for corrupted files, cleared recent installations, and reinstalled OBS after restarting the PC. After deleting the 28.0.3 version of OBS and restarting, the connection speed returned to normal. However, it later dropped again.
Event Viewer logs showed numerous informational entries and an error labeled DHCPNACK, possibly indicating an IP lease issue. I suspect either a system malfunction requiring reinstallation or physical damage during an out-of-home period affecting the LAN port or chip. Additional notes: BIOS was updated a month ago, switching from CSM to UEFI, with everything functioning until last week.
It might have been a PowerSpectre, though unlikely since it would also damage the router or switch. They sometimes manage to survive. I’d just reinstall Windows without spending extra time fixing issues. If it’s still problematic after reinstall, the onboard NIC could be faulty. Stick to working Wi-Fi instead. I’ve witnessed many network cards failing without reason, and seen several Windows setups break network devices too. ... Honestly, try reinstalling Windows at least once a year, as leftover junk from patches and updates often fails. Regarding the time you mentioned—updating BIOS and tweaking settings can take weeks before effects appear. Most network configurations have a timer that needs resetting, DHCP DNS, Windows accounts, and even server settings. These changes usually require patience. Ultimately, troubleshooting is slow and depends on hardware quality. A quicker method would be to check the device directly.
The person who owns several flat cables says that if there are any problems, it's likely due to the flat cable.
I experienced the same issue recently, which required adjusting settings only via the command line—something I had never done before. Windows automatically changed it on its own. To verify, I used a thumb drive and installed a bootable Linux system. If you could connect to the network at full speed, it pointed to a software problem; otherwise, it likely indicated hardware issues.
I neglected to note that I had reinstalled Windows multiple times each month. While attempting a fresh install from Legacy to UEFI, I encountered issues with MSI's modified BIOS, which only supports certain Ryzen AM4 processors. The UEFI setup didn't function properly in the 2020 BIOS version, and even with the latest release (1.2.0.7 AGESA), it wasn't working. It might be worth trying a complete fresh install now.
That sounds like a solid plan. I’m glad you found the info helpful.
start pressing start in a new window, type cmd and select it. enter ping google.de, then check if anything above 100ms is reached or not. if not, try pinging your router with fritz.box. open cmd again later and see the results. look at your network speed and confirm the speeds shown.
I followed all your recommendations. The screenshots are included in the reply. When I noticed many timed-out requests, I considered clearing DNS and resetting TCP/IP to see if it would resolve the problem. After restarting, I opened the auto repair diagnostics window and received a message indicating Windows couldn't repair corrupted files. Based on this, I believe I should skip installing a bootable OS and instead perform a fresh installation of Windows to address not just the Ethernet issue but also potential problems in system32 files.