Help with LSO Triggers - Connection Drops

[WHYAHWHYA]

Hello everyone,

I’m experiencing a recurring issue where my PC randomly disconnects and reconnects to my TP-Link Deco X55 network, and keeps doing so for 10-15 minutes until i get a stable connection

Setup

OS: Windows 11

Wi-Fi Adapter: Intel AX200

Driver Version: 23.150.0.4 (updated to 24.20.2.1 and rolled back)

Router: TP-Link Deco X55 (Wi-Fi 6)

System model: Beelink SER5 Plus Mini PC,

What I’ve tried so far

I initially tried troubleshooting using ChatGPT by sharing logs from Windows Event Viewer and Deco logs. Based on the suggestions

1.Changed the following adapter settings:

Preferred Band → Prefer 5GHz

Roaming Aggressiveness → Lowest

Channel Width for 2.4GHz → 20 MHz only

Channel Width for 5GHz → Auto

Transmit Power → Highest

Throughput Booster → Disabled

U-APSD → Disabled

Fat Channel Intolerant → Enabled

802.11ax Mode → Disabled

Could someone help interpret the logs and identify the root cause?

Is this:

• A driver issue with the AX200?
• A compatibility issue with Wi-Fi 6 / Deco X55?
• Or a roaming/mesh-related problem?

furthermore, I'm also attaching DECO Log, which i notice the below lines gets repeated 192 times each within 9 minutes, i have redacted my MAC address

client_ifname:ath1, client_action:associate

client_ifname:ath1, client_action:disassociate

• Other devices on the same network are stable
• Issue is isolated to this client
• Signal connection (full)
• Mesh system (Deco) is using wireless backhaul

Any guidance or direction would be greatly appreciated.

[JeanetteC_Intel]

Hello WHYAHWHYA,

Thank you for the update and for reviewing the TP-Link troubleshooting page. I acknowledge that you've already tried forcing the device to connect to another satellite as suggested in the "Fix: Deco Network Is Stable but Specific Devices Drop Out" section, but the issue persisted.

Disabling the "Channel-Load usage for AP selection" and "Phantom TAP-Windows Adapter V9" are good troubleshooting steps that may help reduce the roaming conflicts and connection instability you've been experiencing with the mesh system.

Please take your time to monitor the connection stability after implementing these changes. We look forward to your next update on whether these adjustments resolve the frequent disconnections and LSO triggers.

If you have any questions or need further assistance during the monitoring period, please don't hesitate to reach out.

Best regards,

JeanetteC.

Intel Customer Support Technician

[WHYAHWHYA]

Unfortunately disabling Channel-Load usage for AP selection and Phantom Tap V9 didn't help.

Please see attached logs, i didnt event need to wait 24 hours, as you can see, "7021 - Connection telemetry fields and analysis usage" was triggered 2593 times between 5/1/2026 12:50:40 AM & 5/1/2026 12:57:17 AM.

[JeanetteC_Intel]

Hello WHYAHWHYA,

Thank you for the update and attached log file. I can see that the recent changes did not resolve the connectivity issues.

The log data confirms a significant compatibility issue between your Intel AX200 adapter and the TP-Link Deco X55 mesh system, with 2593 connection events occurring in just over 6 minutes.

Since we've completed standard troubleshooting and the issue persists only with the mesh network, I will proceed with the investigation of this case for further investigation by our technical team. They will analyze the logs to determine if additional solutions are available for this compatibility scenario.

You will receive an update once our investigation is complete. In the meantime, you may continue using the direct connection to your Huawei router for stable connectivity.

Thank you for your patience throughout this troubleshooting process.

Best regards,

JeanetteC.

Intel Customer Support Technician

[WHYAHWHYA]

Thank you very mucb Jeanette, will look forward for your technical teams input, mean time I'll continue diagnosing the issue with TP-Link hopefully they have other solutions for me.

I might look into upgrading teh Wi-Fi card if it all fails, but that will be my last resort

[JeanetteC_Intel]

Hello WHYAHWHYA,

To assist with further investigation, please check your email for our private message requesting additional information that may help. Be sure to check your inbox, as well as your spam and junk folders, as the message might have been directed there

Best regards,

JeanetteC.

Intel Customer Support Technician

[emmasmith]

Hello Jed,

At the time of writing this update, I have completed diagnostic steps 1 and 2, including disabling power management for the network adapter.

I have also cleared the Event Viewer logs to ensure I can better monitor any new activity or errors moving forward.

I will continue to observe the situation and report back within 48 hours with my findings and any further updates.

Best regards,

seo sabir

[peptixcalc]

This is a really well documented case, and you’ve already done a solid job narrowing it down.

From the logs and the repeated associate/disassociate pattern, this really looks more like a roaming or mesh handoff issue rather than a pure driver failure. The fact that other devices stay stable also points away from router-wide instability and more toward how the AX200 is interacting with the Deco mesh switching.

One thing that stands out is the LSO trigger cycle happening in bursts. That usually happens when power saving or network optimization features are trying to aggressively manage throughput, especially on WiFi 6 + mesh setups. Even after the driver reset, the behavior changing slightly suggests it’s still environment + adapter interaction rather than a corrupted driver.

If Step 5 (clean install) still doesn’t fully fix it, I’d personally test one more thing that often gets overlooked in mesh systems:

Try locking the device to a single node (if Deco allows device binding) and temporarily disabling any “auto optimization” features during testing. That can help confirm if roaming is the real trigger.

Also, keeping a clean monitoring window like you’re doing with event logs is exactly the right approach. It helps separate random noise from actual patterns.

For people working with systems, tools, or technical optimization workflows, I also maintain a simple utility platform that focuses on clean calculations and structured outputs for technical use cases: peptixcalc 

Hopefully Step 5 gives you a clearer result, but if not, this is very likely a mesh roaming behavior issue rather than hardware fault.