Your problem is almost certainly a networking driver in AdGuard. We see it called several times immediately before the page fault that causes the BSOD (read this from the bottom up)...
[code]
ffff9586`0faabea8 fffff802`6c425f89 nt!KiPageFault+0x489
ffff9586`0faabeb0 ffffce01`4f60a202
ffff9586`0faabeb8 00000000`00000108
ffff9586`0faabec0 ffff9586`0faac0a0
ffff9586`0faabec8 fffff802`7c17e800 adgnetworkwfpdrv+0xe800
[/code]
The driver adgnetworkwfpdrv.sys fails in all of those dumps -which are pretty near identical. The version of adgnetworkwfpdrv.sys that you have installed seems current...
[code]
6: kd> lmvmadgnetworkwfpdrv
Browse full module list
start end module name
fffff802`7c170000 fffff802`7c189000 adgnetworkwfpdrv T (no symbols)
Loaded symbol image file: adgnetworkwfpdrv.sys
Image path: adgnetworkwfpdrv.sys
Image name: adgnetworkwfpdrv.sys
Browse all global symbols functions data Symbol Reload
Timestamp: Tue Oct 1 18:11:28 2024 (66FC1120)
CheckSum: 00018456
ImageSize: 00019000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
[/code]
...but it's worth checking for an update.
