This widget could not be displayed.
This widget could not be displayed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Vivobook 16 (M1603QA): Frequent packet loss and connection drops

Addendum: The WLan 6001.15.117.0 and Bluetooth 1.9.1046.3001 driver pair seem to work as expected (the versions after the oldest pair listed in MyASUS). I did not test the pair following (no reason to rn) and the latest (6001.15.128 and 1.9.1051.3007 pair as of 8/16/2023) work terribly.

Prefacing with saying I have done everything any support page has asked of me, barring System Restore (nothing to restore to) and resetting (issue out of the box). I have kept this laptop up to date.

The network adapter (Realtek 8852BE Wireless LAN WiFi 6 PCI-E NIC) has frequent packet loss and connection drops and only seems stable when loading non-interactive content like web pages or files. 

I've done mitigations such as downgrading the adapter via Device Manager properties and preferring IPv4, which help, yes, but they're still mitigations.

6 REPLIES 6

Editted for clarity and new info

I ran "netsh interface ip reset" (I believe ip just aliases to ipv4, so for already established games like OW, most Source games, etc this isn't a problem for now) and "netsh winsock reset" in an elevated cmd prompt and restarted. After re-installing both the network and bluetooth drivers, restarting, and then restoring my net adapter settings, my dns servers, and flushing dns, it seems to now briefly timeout/drop packets every like 30 minutes to an hour. A major improvement but it would be nice if it didn't happen at all. L4D2 turned from a slog to being plenty stable, even on latin america servers. Insurgency always seems to run fine so I can't judge it.

Turning on auto-tuning (netsh winsock set autotuning on) seems to bring even more network stability (OW2 complains way less about brief "superficial" high latency). I have no idea about any settings before as I didn't have the foresight to, sorry on that one.

While an improvement not to be scoffed at, I still would prefer not having to deal with hourly brief timeouts at any time. Only saving grace is that the timeouts recover after a second compared to like 3 from before.

The wlan driver 6001.15.117.0 and matching bluetooth driver 1.9.1046.3001 seems to work the best. The time between the timeouts seems to be longer, connection more stable than before, but it still happens.

The initial wlan 2024.0.10.135 and bt 1.9.1041.3002 drivers do not work (devices aren't detected). I did not test the next pair (6001.15.124.0 and 1.9.1015.3002, version before latest) as the same thing will probably happen anyway.