Download Speed Degraded - culprit mobo NIC?

P4i6g / P4i65g
February 14, 2010 at 14:36:59
Specs: Microsoft Windows XP Home Edition, 2.596 GHz / 2038 MB
I have just started noticing slower download speeds on my XP system. I have determined that it is my system and not my router, modem or cables.

Using speedtest.net I am seeing download speeds that typically top out at 2.8 Mbps. I should be getting close to 10Mbs

I have 2 other systems on my network. Using the same server at speedtest.net I get 14 Mbps on the faster system, 9 Mbps on the slower one. The system that gets the 9 Mb has the same Asrock MB as the system that gets 2.7 Mb. I am using the MB network connection on both Asrock machines.

I eliminated the router and went straight to cable modem with no improvement. I even swapped the network cable just be sure.

TWC checked my modem and declared it OK, especially since I'm exceeded 10 Mb on one of my systems.

This problem started a few days ago, so I did a System Restore back to last week but it didn't help. There should have been no changes to system since then.

Any idea on where the problem might be? Could my MB network connection be shot? Should a try a dedicated network card?

Any suggestions would be appreciated.

Thanks!


See More: Download Speed Degraded - culprit mobo NIC?

Report •

#1
Report •

#2
February 14, 2010 at 17:55:00
Thank you for those links, but I am not having problems with a slow computer when it comes to opening apps, etc.

I have run a number of scans and there doesn't appear to be any malware or viruses present.

The problem seems to be isolated to the speed of my internet connection.


Report •

#3
February 14, 2010 at 18:05:04
If you have a spare, or can get a discrete network card, use that & bypass the integrated network adapter on the Asrock motherboard to see if there's an improvement in your bandwidth capacity.

Windows 7 News!


Report •

Related Solutions

#4
February 14, 2010 at 18:16:43
Try uninstalling the onboard Network Card in Device Manager, then reboot your computer. Windows will detect the Network and reinstall drivers. Also try refreshing the ISP Software/Modem drivers, by uninstall/reinstall.

There is nothing to learn from someone who already agrees with you.


Report •

#5
February 14, 2010 at 19:18:40
re: uninstalling the onboard Network Card

Didn't help.

re: refreshing the ISP Software/Modem drivers

Not sure what I should be looking for here. I don't see anything under Add/Remove Software that relates to the NetGear router or TWC Cable Modem.


Report •

#6
February 14, 2010 at 19:30:35
I just upgraded the NetGear router firmware. Didn't help.

I think I'll pick up a network card tomorrow and see what that does.


Report •

#7
February 14, 2010 at 20:09:10
Not sure what I should be looking for here. I don't see anything under Add/Remove Software that relates to the NetGear router or TWC Cable Modem

That is because such things do not exist. Modems and Routers do not need drivers. The only drivers needed are for the network Interface card. Most software supplied by an ISP can be safely ignored. It just does what you can do for yourself in less time than it takes to load the software.

The one exception to this is if you have a USB Modem then you need USB drivers supplied by the manufacturer.

Stuart


Report •

#8
February 15, 2010 at 05:36:31
re: That is because such things do not exist.

That's kind of what I thought. I didn't recall installing any software from my ISP when I installed the modem.

Thanks.


Report •

#9
February 15, 2010 at 06:19:54
What kind of computer is it DerbyDad? Is it custom built or a brand name and if brand name, what's the make/model. If it's a Dell, it may very well be a NIC issue. We have had Dell rammed down our throats at work (you guessed it, I don't care for dell) and the one model has consistently been having major NIC issues.

In this case, you've already isolated it to the one PC so you know it's either hardware or software. Normally in a case like this I would first run antispyware and antivirus to ensure it wasn't a spyware bloat issue.

If that didn't fix it, I would then go into Device Manager and uninstall the NIC and then reboot and let XP "find" it again.

If that doesn't work, I would then un/reinstall the TCP/IP stack and see if that doesn't do the trick. If it doesn't, the next thing to test would be the NIC.

If you try a new NIC with no improvement it may be time to backup that unit and wipe it and do a clean install of your OS.

Just as an aside, with the Dell's at work that have bad NIC's, when you try my first step (unistalling the device) when reboot is done, your NIC would now show up as "Local Area Connection 2" and if you did it again, you would then see "Local Area Connection 3" and so on and so on and none of them would work and the only fix we found was to reinstall from scratch. But of course, since the NIC is borked, it's only a matter of a few days and it starts puking again and you have to replace the mobo.


Report •

#10
February 15, 2010 at 06:44:40
re: What kind of computer is it DerbyDad

It's a custom build. The mobo is an Asrock P4i65g.

re: run antispyware and antivirus

Done...Clean

re: go into Device Manager and uninstall the NIC

Done...Didn't help.

re: un/reinstall the TCP/IP stack

How do I do that?

re: try a new NIC

If the TCI/IP stack suggestion doesn't work, that will be my next step.

re: wipe it and do a clean install of your OS

Ack!


Report •

#11
February 15, 2010 at 08:35:21
TCP/IP Reset, 2 methods.

http://support.microsoft.com/kb/299357

There is nothing to learn from someone who already agrees with you.


Report •

#12
February 15, 2010 at 13:03:30
re: un/reinstall the TCP/IP stack

I ran the FixIt from here and it didn't help.

http://support.microsoft.com/kb/299357

Time to go shopping for a NIC card, but I have my doubts that it's going to help.


Report •

#13
February 16, 2010 at 06:18:28
re: un/reinstall the TCP/IP stack

How do I do that?

Go into the properties for the NIC and highlight "Internet Protocol, TCP/IP " and click the "uninstall" button, then reboot.


Report •

#14
February 16, 2010 at 16:38:20
re: Go into the properties for the NIC

Maybe I'm be missing something here...

I went into the Network Connections Control Panel, right-clicked the Local Area Connection 4 and chose Properties.

When I highlight "Internet Protocol, TCP/IP" the Uninstall button grays out.

I can uncheck the box next to it, but I can't "uninstall" it.

I tried the NIC properties in the Device Manager but there is no TCP/IP option under any tab.

Is it me?


Report •

#15
February 17, 2010 at 07:54:09
Hmmmmm.........that is odd!

Ok, I see you have it listed as "Local Area Connection 4 " . Is that because you have 4 or more NIC's or because you'ev uninstalled the NIC in device manager a couple times?

As I said In my initial post:

Just as an aside, with the Dell's at work that have bad NIC's, when you try my first step (unistalling the device) when reboot is done, your NIC would now show up as "Local Area Connection 2" and if you did it again, you would then see "Local Area Connection 3" and so on and so on and none of them would work and the only fix we found was to reinstall from scratch. But of course, since the NIC is borked, it's only a matter of a few days and it starts puking again and you have to replace the mobo.

The same thing could be happening to your system, even though it's not a dell *gag*.

So if it's because of un/reinstalls of the NIC in Device Manager that it's listed as #4 I suspect you're hooped and will have to do a clean install of the OS to get that device working properly.


Report •

#16
February 17, 2010 at 19:27:22
I don't recall ever un/reinstalling the NIC myself.

However, I recently went through a thorough cleaning with some help from geekstogo. I know that some of the cleaning apps they have you run disable your internet connection, so it's possible they un/reinstall the NIC.

...and before you ask, no, my internet slow down did not start immediately after the cleaning exercise. The system was fine for weeks after that, so I don't think anything that was done via geekstogo caused this problem. I only bring this up as a possible reason my LAN connection is up to number 4.

I also ran the TCP/IP FixIt from the MS support site.


Report •

Ask Question