SuperHub Connection Unstable When One PC Is Started

[MattMcQueen]

This is a very strange issue.

I have my SuperHub in modem mode and use my own router.

My connection is very stable, normally.

However, I have one Windows 10 PC that is causing an issue - if this PC is started and connected to the network, the SuperHub connection becomes unstable, and it loses the connection multiple times a day. It's as if the SuperHub is restarting.

I've tried connecting the computer with a wireless connection, and with an ethernet cable to the router, and the result is the same.

If this computer isn't running, the connection is rock solid.

Has anyone seen anything like that before? How would I go about troubleshooting this issue?

[MattMcQueen]

I've included my network log - not sure if it helps.

Network LogTime Priority Description

09/08/2021 05:16:40	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/08/2021 11:43:1	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/08/2021 11:43:1	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2021 12:56:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2021 09:34:10	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/07/2021 20:16:49	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2021 20:45:11	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2021 02:11:24	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2021 18:45:2	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2021 08:09:12	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/07/2021 03:37:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2021 09:42:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/07/2021 23:10:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/07/2021 17:36:6	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[MattMcQueen]

I also have a monitor on thinkbroadband - lost the connection this morning within ten minutes of booting up the PC. Other PC's connect fine.

[Andrew-G]

Is the problem PC a Dell and/or has a Killer wifi card?  

[MattMcQueen]

Yes to both.

[lotharmat]

You'll need a USB wifi adapter and disable the killer WiFi card. It really does seem to kill hubs!

[MattMcQueen]

Thanks - I read through the forum this morning, once I was pointed at Killer being the issue, and that seems to be the solution.

I'll come back once I try that.

[Andrew-G]

I would imagine that Intel (who make the embarrassingly appropriately named Killer wifi chips) will be having an urgent look at this.  You might want to see if there's anything in the way of Intel consumer support that sheds any light on the matter, or consult Dell if your machine is still in warranty (or use the Dell customer forums if not).  I suspect the ultimate solution is new drivers, but I don't know if a properly fixed driver is available yet.

There may also be a problem with ensuring that any existing faulty drivers are fully removed before installing new "fixed" ones, and then you need to hope that neither Dell's optimisation progammes now Windows over-writes those drivers.

[legacy1]

Maybe you could disable some of the options in the Killer NIC properties to stop it causing problems with your router as modem mode and the hub would only be (should be) affected when directly connected.

[MattMcQueen]

Looking through the forum, this issue has been going on for a long time (2 years?), so I'm not holding out much hope of Dell or Intel fixing it.