Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

Tethering freezes pc when a lot of traffic goes through.

Jun 2, 2019 10:17AM PDT

Once I tether my phone's internet to my pc the event viewer spits out errors like "Miniport Remote NDIS based Internet Sharing Device #2, {ccd99f63-a7a0-46af-922a-98e740cd0d57}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)"
and "The network interface "Remote NDIS based Internet Sharing Device #2" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver did not respond to an OID request in a timely fashion. This network interface has reset 1 time(s) since it was last initialized." I have no idea what could be causing it, I have the adb usb drivers installed. My phone is a Redmi 6A and here's a speccy of my pc : https://ufile.io/u6jo2szh . This only happens while tethering.
EDIT: also this appears "Name resolution for the name ml314.com timed out after none of the configured DNS servers responded."
I've tried doing "wmic nicconfig where (IPEnabled=TRUE) call SetDNSServerSearchOrder ("8.8.8.8", "8.8.4.4")"
and "netsh winsock reset
netsh int ip reset
ipconfig /flushdns" in cmd then rebooting to no avail.

Moderator edited: Added a space after the URL to fix it.

Post was last edited on June 2, 2019 10:30 AM PDT

Discussion is locked

Rexongaming has chosen the best answer to their question. View answer

Best Answer

- Collapse -
Link fixed.
Jun 2, 2019 10:41AM PDT

BIOS is current. I'd check the motherboard maker's site as the chipset driver is now dated 2019/05/27 so something is up there.

You should disable Microsoft driver updates (so many articles on the web about that) then install at least the motherboard chipset driver as USB issues are suspect here.

The ML314 site is blocked here with "uBlock Origin has prevented the following page from loading:"

Maybe they are just a bad site that tried to do something awful, I won't investigate that.

MOVING ON. There are far too many AMD 350 chipset based boards with owners yelping about lockups, reboots and more. Our office avoided those builds so we didn't have to deal with the fallout. If I was going to do a Ryzen build it would be from this list: https://www.reddit.com/r/PCMasterRace/wiki/builds

Since some can't decode what I'm writing here, I'll just write "No, I don't expect an easy fix." But if this was mine I'd try something else other than tethering.

1. I'd install UBLOCK ORIGIN!
2. I'd plug in some WiFi card.
3. I'd tether via WiFi to my phone.

As to the machine, I would:
1. Disable Windows 10's driver update system. (google how!)
2. Install the makers latest chipset driver and hope.
3. Post in the motherboard maker's forums.

- Collapse -
Temp fixed
Jun 2, 2019 11:11AM PDT

I am doing as you say, currently ordering the motherboard and ram from that post, right now it works once I cap the network speed at 3MB/s so that's good. Thanks for the help!

- Collapse -
Answer
Just a note. I'll edit your URL too.
Jun 2, 2019 10:30AM PDT

When posting URLs be sure to not add anything before or after the URL.

I'll reply again later but Ryzen systems are all over the web with lockup issues. Be sure to talk to the motherboard maker or their forum about which BIOS to use (I use the latest) and get them to tell you exactly which drivers to use for W10 and what order to install them. The BIOS settings can matter too.

But I can't tell you that. You need to be on that motherboard maker's forum for those answers. My answer will be generic. That is, latest BIOS, BIOS defaults then install W10, disable W10's driver updates then install the drivers in this order: Motherboard, Audio, video, LAN, WiFi and then onto whatever else is required for this build.

- Collapse -
Fixed it completely.
Jun 5, 2019 8:27AM PDT

Turns out it was my carrier, I switched from ipv6 to ipv4 and it suddenly didn't error at all and worked fine. Fixed!