Question Please help - Slow speeds using GB ethernet card. Other wired/wireless devices are fast.

Jun 1, 2019
2
0
10
Affected PC:
------------------
System Information
------------------
Time of this report: 6/1/2019, 14:21:44
Machine name: MATT-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr_escrow.190320-1700)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK Computer INC.
System Model: CM6330_CM6630_CM6730_CM6830-8
BIOS: BIOS Date: 09/28/12 14:39:34 Ver: 04.04
Processor: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8 CPUs), ~3.4GHz
Memory: 16384MB RAM
Available OS Memory: 16336MB RAM
Page File: 4907MB used, 27760MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

I'm using a Nighthawk AC1900 WiFi Cable Modem Router. The ports on it support GB speeds.

Trying multiple cables in both the PC and the PS4 that is sitting right next to the PC, I've ruled out the cables as the problem. Cat5e cables, seem to be working fine. ISP speed is 200mbps, the ps4 pulls about 180 wired. Good. The PC stays between 40-70 mbps.

First, I updated the drivers for my on board ethernet port. No good. Played with speed and duplex, disabled green, or energy saving settings. No good. I figured the port was just old and going bad. I installed a new PCIE GB Ethernet card with drivers from the website provided. Still no change. I've been googling solutions for days now and I'm starting to lose my mind a bit. The replacement network card is from EDUP, model EP-9602. I repeated all my troubleshooting from before with this new card. No good. I'm at a brick wall now, and I'm sad.
 
Jun 1, 2019
2
0
10
Well, for anyone having a similar issue, sorry I do not have a straight fix for this. I finally said "screw it" and did a fresh install of win10 from win7. It's fixed. 200+ mbps now. I don't know if reinstalling win7 would have also fixed the problem, but in my case, going from win7 to fresh win10 solved it.