Repeated 0xD1 BSOD in NETIO WFP path with adgnetworkwfpdrv 8.0.87

### Environment

- AdGuard for Windows: **8.0.5560.0**
- `adgnetworkwfpdrv.sys`: **8.0.87.0**
- WFP component: **1.7.2.2**
- NFSDK component: **1.7.5.8**
- Windows 11 Pro for Workstations 25H2, build **26200.9168**
- Google Chrome: **151.0.7922.174**
- Clash Verge: **2.5.2**, TUN enabled (`stack: mixed`, `auto-route: true`, `strict-route: true`)
- `wintun.sys`: **0.14** (WireGuard LLC)

### Summary

The system crashed and rebooted four times during ordinary network activity (video playback and gaming). There was usually no visible blue screen: the display went black, audio looped or made a loud noise, and Windows rebooted automatically.

All four minidumps report `DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)` and reproduce the same WFP/NETIO receive path. The evidence suggests an interaction between the AdGuard WFP driver and Wintun rather than a GPU crash. I cannot prove which driver owns the invalid object from these minidumps alone.

### Crash times (local time, UTC+8)

- 2026-08-21 19:17:44
- 2026-08-22 01:07:26
- 2026-08-22 18:24:40
- 2026-08-22 18:44:23

### Common dump pattern

Two pairs have identical bugcheck arguments and instruction offsets:

```text
0xD1 (0x50, 2, 0, NETIO!KfdAleAcquireEndpointContextFromFlow+0x2f27)
0xD1 (0x08, 2, 0, NETIO!KfdAleAcquireEndpointContextFromFlow+0x2ca8)
```

The relevant stack is consistent across all four dumps:

```text
wintun+0x19fe
ndis!NdisMIndicateReceiveNetBufferLists
tcpip
NETIO!WfpStreamInspectReceive
NETIO!FwppStreamInject
NETIO!KfdClassify
NETIO!KfdAleAcquireEndpointContextFromFlow
```

In every dump, one address shown in the `NETIO!KfdAleAcquireEndpointContextFromFlow+0x1244` frame resolves inside `adgnetworkwfpdrv+0x1330`. The AMD display driver is loaded but does not appear in any of the four crash stacks.

### AdGuard log timeline

On 2026-08-21 at approximately 19:11 local time, AdGuard stopped/uninstalled driver 8.0.86.0 and installed/started 8.0.87.0. The log also contained these warnings during the transition:

```text
The NFAPI lib isn't initialized, can't unregister...
The NFAPI lib isn't initialized, can't register...
```

The first crash occurred about six minutes later. Before later crashes, the logs repeatedly showed `Start network driver`, `Stream was not found`, and frequent rule-state checks.

The installed and DriverStore copies of `adgnetworkwfpdrv.sys` had matching hashes and a valid digital signature, so file corruption is unlikely.

### Workaround / current status

I completely uninstalled AdGuard, including its remaining WFP driver service, and am monitoring the system. This is not yet enough observation time to claim the crashes are resolved. Clash Verge/Wintun had been active during the crashes.

Raw minidumps and complete logs may contain private memory, account details, URLs, or browsing data, so I have not attached them publicly. I can provide the four dumps and relevant redacted logs privately to the AdGuard team if needed.

Possibly related to #5792, #6119, #6014, and #5409.