Hi all
Finally had a chance to look at the Event logs and the MSInfo data ... nothing jumps out at first look. There's an Unknown Device (ACPI\PNP0A0B\2&DABA3FF&0), but I'm not sure that it is making a difference one way or another. It could be an onboard device of some sort, since an interesting ACPI warning also shows up in the Error logs, concerning an embedded controller returning data when none was requested. Unless its a source of unnecessary polling & traffic, it might be harmless.
I also took another look at the reviews for your board at a couple of different tech sites ... it's reputation is a glowing 5 stars for only 40% of the owners, on average. An uninviting 38% give it one star (the lowest) or two. The main issues for the unhappy owners revolve around sound problems & video slots that stop working after a not-so-long period. My suspicion is that it is "luck of the draw" with the Asus boards: when they are good, they are very good. And when they are bad, there's no doubt about it -- even for boards of the same model (that were wonderful for the lucky 40%). Might not just be a driver/operating system issue - certainly there is a possibility of qualitry control [in fact, that issue might hold for all three: the hardware manufacturers, the driver programmers, and the operating system programmers].
Do you notice the troubles mostly in the audio stream? (or does video stuttering become noticeable too?) ... I wonder if anything would change if you move the card to the second slot - who knows.
I've seen the same articles that you have seen - regarding using an older network driver for ndis. Since your board originally came out in the Windows 8/8.1 years, I'm a little surprised that nothing from then installs [you mentioned trying older drivers, and none would work]. It's an ugly dilemma: I'd expected the driver issues to calm down after the first year (of Windows 10). But it seems that there's still a lot of room for improvement.
For the moment, it looks like the only thing consistently holding the issues down during gameplay is to have no other Internet activity going on simultaneously (no open browsers, torrents, "live tile" updates, etc.) and also limiting background activity such as Windows "tips" notifications, background app notifications and other app background activity, and limiting system "indexing" functions to basics .... and so on.
You can check in on your firewall situation too, the Windows Firewall should show as "Off" in Control Panel, since you are using the Avast firewall. If it is allowed, try disabling the "block port scans" feature in the Avast firewall (though you might make sure first that your gateway/router/modem device has this feature enabled - - you just want to have the software firewall on your system to not cause trouble when it is an unnecessarily redundant function). It is the block-port-scans feature that was shown to cause audio issues on some systems. Since this issue mainly concerns Internet traffic, its possible it might effect the ndis latency problems.
Keep trying .... since you got it working well enough once - - - you likely can do so again!