Have gigabit - Downloading at 20MB/s HELP! - SOLVED!

[-12 syl]

So here's my issue. I have gigabit internet and I can only download games at 20MB/s. This seems to be an issue on my end because my roommate gets 90MB/s down. We are both connected to the same modem and we both have the exact same CAT6A cable.

I can get 90MB/s+ on Origin launcher, but steam never goes above 20MB/s.

I have spent over 60+ hours trying various solutions to fixt he problem and I have not been successful. At some point I was getting the full speed but something changed and I have no clue what it was.

I am at the end of my rope as I've literally tried every solution I could find on Google, including a fresh OS install. I'm exhausted and would like this problem to go away. I know 20MB/s is still very fast, but it's become a thorn in my side at this point when I have to wait 1 hour 30 mins to download a large game.

System specs
8600k OC'ed 5GHZ
1GB/s LAN (10GB/s ethernet link)
Asus Prime Z370-A
Samsung 960 NVME 256GB
Samsung Evo Pro 500GB SSD

Router:
Asus R7000

OS
WIn 10 Pro 64 bit

Things I've tried:
Disabling energy efficiency settings in Windows power options & Device manager
Updating network drivers
Updating router and modem firmware
Checking to see if QOS is enabled (It is disabled)
Installing fresh OS
Changing steam download location
Changing steam install directory
Using a TCP optimizer tool
Trying a different Ethernet cable
Updating SSD drivers
Confirming my download speed VIA Speed test in windows 10 app and using other game launchers
Updating steam
Checking steam network settings to see if I'm throttling myself
Clearing steam download cache
Using a VPN
Using a public DNS
Possibly more...

[-12 syl]

Originally posted by Nightenhelser:

Do you have "Throttle downloads" checked or "Limit bandwidth" checked in Settings?

Both boxes are unchecked :(

[Iceira]

9/30/20 - Firmware update 1.0.11.110 for R7000 now available.

speed test into own ISP.

change DL zone as test

NO vpn, no wifi. use cable as only test to ruleout wifi unstability.

[-12 syl]

Originally posted by Iceira:

9/30/20 - Firmware update 1.0.11.110 for R7000 now available.

speed test into own ISP.

change DL zone as test

NO vpn, no wifi. use cable as only test to ruleout wifi unstability.

Router firmware is currently up to date, set to auto-update. I also checked the modem and it's firmware is also up to date.

Isp speed test gives me roughly the same speed. 900MB/s down - 40Mb/s up
Speed test gives 900MB/s down 40MB/s up

I only use a cable. VPN is off and I have even tried disabling the VPN adaptor just in case windows was trying to use it.

Steam still wants to download at 20MB/s

I also downloaded the latest drivers for both my SSD's, not help.

I just tested origin again and I'm getting roughly 80-90MB/s down.

Tried opening my firewall for steam and running it as admin, and also tried disabling the firewall entirely. It's still 20mb/s :(

Also, thanks to everyone who has tried to help so far.

[-12 syl]

Okay, so I have found the issue. The link between my modem and router is somehow interfering with steam but not origin. I am going to look into this further but I suspect it may be port related.

I found the issue when I plugged directly into the modem and completely bypassed the router.

[-12 syl]

So I managed to fix the issue completely. I read a post on netgear forum about an older version of the firmware being more stable. So I decided it was worth a shot. When I applied the firmware, it made me go through the setup wizard. Once the wizard was done setting up (I choose the auto-option) my speed went to full.

So the issue was either the newer firmware version or the router configuration.

Previously my router was setup for "Router mode" and the auto-wizard set up my router in "AP mode"

Now I noticed that the router set itself up as the default gateway as my modem which is 10.0.0.1. Before my router was set up as 192.168.1.1 and my modem 10.0.0.1. So currently I am unable to change any router settings without turning off the modem. Which is OK for now.

I will work on this more later when I have more free time and get everything set up the way I want. I just wanted to post here and let everyone know that the issue was RESOLVED.

Thanks to everyone who took the time to try and help me with this issue. I can not thank you enough <33

[Iceira]

wellcome to my world , i know you did not need such problem , but now you get it check all things. and the ip adr. dont change how router work , thats a configuration , any privat network scope adr. is okay, and atleast you discover it, most of the time modem is part of ISP setup or building complex, it can very well be new modem , not much you can do, as i recall thats a isp choise to get a stability on the line, but many forget that was cobber line issue , not on cable but they have use it to check line is okay. (most isp today have skip that check because they can cause more grief after 10 . 15years. and yet other unit keep going, so its not that simple. ask isp if its needed. ( depend on the signal converting ) and how fare from dslam or server room and setup they did )

[rawWwRrr]

Nice job.

From your story, I bet it was more than configuration than the driver. If you have the time to test it more, see if you can get the new firmware back on the router and ensure the settings were correct.

[-12 syl]

I changed the settings back to router mode and it was indeed the firmware causing the issue.

For anyone having this issue in the future, If you have a R7000 router, downgrading from R7000-V1.0.11.110_10.2.100 to firmware version R7000-V1.0.9.42_10.2.44 fixed the issue.

[-12 syl]

Originally posted by Iceira:

wellcome to my world , i know you did not need such problem , but now you get it check all things. and the ip adr. dont change how router work , thats a configuration , any privat network scope adr. is okay, and atleast you discover it, most of the time modem is part of ISP setup or building complex, it can very well be new modem , not much you can do, as i recall thats a isp choise to get a stability on the line, but many forget that was cobber line issue , not on cable but they have use it to check line is okay. (most isp today have skip that check because they can cause more grief after 10 . 15years. and yet other unit keep going, so its not that simple. ask isp if its needed. ( depend on the signal converting ) and how fare from dslam or server room and setup they did )

Hehe, did not "need" this but it helps save me time. I dont have infinite SSD space, so when someone who has a game installed wants me to play a game and I DONT have it installed, I have to wait over an hour sometimes. That sometimes means they lose interest/time and I lose space.

I've been doing basic networking for 10 years now, so I know how it goes. Check all. I honestly didn't expect to get a fix by posting this, but I'm glad I did or else I wouldn't have thought about DOWNGRADING firmware. As you said "check all things".

Theres been a few times where I have reset the modem and gotten gimped speeds for the whole network. Had to call ISP to solve. We were getting 400/20 and paying for 600/20. The ISP reapplied the gateway settings and it fixed. I like to not call them if I don't have to, saves us both some time.

A friend of mine just upgraded his router and to his surprise he gained 300MB/s from his ISP. He was paying for 400/30 and was only getting 70/5. Simply upgrading helped.

You learn lots from doing things like this, but I understand why people don't. Its very time consuming and not exactly straightforward if you aren't good with tech. Today alone I spent 6 hours troubleshooting before I nailed the issue. Ironically once I fixed the issue, my ISP decided to do maintenance and I didn't know so I thought something I did, broke the whole network but it's fine now :D. So happy this is all over!

[Hispalense]

Originally posted by Jeffreythe00:

I changed the settings back to router mode and it was indeed the firmware causing the issue.

For anyone having this issue in the future, If you have a R7000 router, downgrading from R7000-V1.0.11.110_10.2.100 to firmware version R7000-V1.0.9.42_10.2.44 fixed the issue.

You saved my life. I've been trying to fix this for days.

Thank you for sharing it!