Menu
Reply
  • 1
  • 0
  • 0
cartman69
Joining in
152 Views
Message 1 of 2
Flag for a moderator

Sloooooooooooow internet after windows 10 update

Hi,

 

I have followed the instructions listed to "fix" the connection problem by the latest windows 10 update, but i am left with slow internet speeds (relatively speaking!!!) my gamer 200 which was always rocksolid for download speed at the max 200, now are all over the place from 40Mb/s up to about 100Mb/s!!! My ping and latency are also poor - but this is a separate issue i believe. I am running a 1m cat6 ethernet cable directly to the superhub 3, but i also have other pc's on the network all running windows 10 experiencing the same problem.

Here are the stats from the router status

 

Downstream bonded channels
Channel Frequency(Hz) Power(dBmV) SNR(dB) Modulation Channel ID
1 299000000 -4.7 38.6 256 qam 21
2 323000000 -4.5 38.6 256 qam 24
3 315000000 -4.4 38.6 256 qam 23
4 307000000 -4.4 38.6 256 qam 22
5 291000000 -5.2 38.6 256 qam 20
6 283000000 -4.5 38.6 256 qam 19
7 275000000 -5.4 38.6 256 qam 18
8 267000000 -5.2 38.6 256 qam 17
9 259000000 -5.4 38.6 256 qam 16
10 251000000 -5.5 38.9 256 qam 15
11 243000000 -5.2 38.6 256 qam 14
12 235000000 -5.2 38.6 256 qam 13

Upstream bonded channels
Channel ID Frequency(Hz) Mode Power (dBmV) Modulation Channel Bandwidth(Hz)Symbol Rate (ksps)
2 31000000 ATDMA 48 16 qam 6400000 5120
3 24400000 ATDMA 48 16 qam 6400000 5120

 

Network Log
Date And Time Error Number Event Description
2016-11-09 10:04:06.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-10 03:30:11.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-10 05:36:26.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-16 07:47:01.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-17 15:17:05.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-18 16:57:27.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-20 15:28:19.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-21 11:09:37.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-26 01:14:44.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-27 07:16:12.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-30 12:11:38.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-30 14:37:34.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-11-30 22:41:01.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-01 09:10:29.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-01 12:26:39.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 19:06:52.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-07 00:00:32.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:28.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:28.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:42.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


 Thnx

Andy

 

0 Kudos
Reply
  • 9.13K
  • 302
  • 981
Forum Team
Forum Team
61 Views
Message 2 of 2
Flag for a moderator

Re: Sloooooooooooow internet after windows 10 update

Hello Andy

 

Welcome to our forum, I am sorry you were having problems, it does look like something was going on. I noticed that you have subsequently called in and hopefully the speeds have improved. At the moment the hub is showing online for the last 8 days error free, area traffic is quite low. How is it for you?

 

Thank you

Nicola

Virgin Media Forum Team
0 Kudos
Reply