BSOD when using WFP driver

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

7.22.3 / 8.0

### Browser version

Chrome 142+

### OS version

Windows 11

### Issue Details

This issue is created to collect and track user reports of BSOD occurrences related to WFP driver after migration from TDI driver.

The migration was introduced as part of AdGuard for Windows 7.22.3 to address filtering issues in modern Chromium-based browsers (Chrome 142+), where traffic is no longer visible to legacy TDI driver - more information in [release notes](https://github.com/AdguardTeam/AdguardForWindows/releases/tag/v7.22.3).

While migration resolves filtering problem, some users report system instability and BSODs when using WFP driver, which requires investigation and correlation across reports.

### Expected Behavior

- AdGuard works stably with the WFP driver enabled
- Traffic filtering functions correctly in Chromium-based browsers (Chrome 142+)
- No system instability, crashes, or BSODs occur during normal operation

### Actual Behavior

- With WFP driver enabled, some users experience system crashes (BSOD)
- The issue appears after automatic migration from TDI driver in version 7.22.3

### Additional Information

For more technical details about causes of the original TDI driver limitations, architectural changes in modern Chromium-based browsers, and temporary workarounds, please refer to the [AdGuard Knowledge Base article](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142).

This article explains why TDI became incompatible, how traffic routing changed in Chrome 142+, and what interim solutions were used before migration to WFP driver.