Open ianusa opened 2 months ago
Already released version 7.18
.
Already updated to 7.18 and will add new dumps once hitting it again.
FWIW, the BSOD persists across many builds (I was on stable, switched to nightly then back to stable few days ago).
The callstacks suggest the identical adgnetworktdidrv+0xac45
(I was enabling full 64GB memory dump, switched back to minidump yesterday to capture and upload the dump).
In this version, network drivers have been updated to improve AdGuard's compatibility with other network applications.
Got a new crash dump on the latest 7.18 build. 070624-22843-01.dmp
PROCESS_NAME: AdguardSvc.exe
TRAP_FRAME: ffffb4091babf150 -- (.trap 0xffffb4091babf150)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb4091babf318 rbx=0000000000000000 rcx=0000000000000008
rdx=ffff900aa5cc3870 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80626857926 rsp=ffffb4091babf2e0 rbp=0000000000000000
r8=ffff900aa5cc3940 r9=0000000000000000 r10=fffff8062669e4f0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiAcquireSpinLockInstrumented+0x56:
fffff806`26857926 f0480fba2900 lock bts qword ptr [rcx],0 ds:00000000`00000008=????????????????
Resetting default scope
STACK_TEXT:
ffffb409`1babf008 fffff806`2682be29 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffb409`1babf010 fffff806`26827289 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb409`1babf150 fffff806`26857926 : 00000000`00000002 ffff900a`74544080 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x489
ffffb409`1babf2e0 fffff806`268412a2 : 00000000`00000000 ffff900a`898ce18c ffff900a`a5cc3940 00000000`00000008 : nt!KiAcquireSpinLockInstrumented+0x56
ffffb409`1babf320 fffff806`2b3c6bf5 : ffffd880`52d37dc0 ffff900a`6357bd30 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x1a2db2
ffffb409`1babf350 fffff806`2b3c7cdf : 00000000`00000000 ffff900a`a5cc3940 00000000`00000000 fffff806`2b22c56c : tdx!TdxObjectHeaderToTransport+0x25
ffffb409`1babf380 fffff806`2b3c2fb8 : ffff900a`9b45f430 fffff806`2669ec0f ffff900a`a5cc3870 ffff900a`a5cc3870 : tdx!TdxQueryInformationControlChannel+0x33
ffffb409`1babf4d0 fffff806`266c1ab5 : 00000000`c0000001 ffff900a`00000000 ffff900a`ab08ce01 ffffb409`1babf5a0 : tdx!TdxTdiDispatchInternalDeviceControl+0x1638
ffffb409`1babf500 fffff806`2b22ac45 : ffff900a`6357bd30 0a000005`e4970b63 00000000`c0000001 ffff900a`898ce18c : nt!IofCallDriver+0x55
ffffb409`1babf540 ffff900a`6357bd30 : 0a000005`e4970b63 00000000`c0000001 ffff900a`898ce18c 00000000`00000000 : adgnetworktdidrv+0xac45
ffffb409`1babf548 0a000005`e4970b63 : 00000000`c0000001 ffff900a`898ce18c 00000000`00000000 00000000`00000000 : 0xffff900a`6357bd30
ffffb409`1babf550 00000000`c0000001 : ffff900a`898ce18c 00000000`00000000 00000000`00000000 00000000`00000001 : 0x0a000005`e4970b63
ffffb409`1babf558 ffff900a`898ce18c : 00000000`00000000 00000000`00000000 00000000`00000001 ffffb409`1babf5a0 : 0xc0000001
ffffb409`1babf560 00000000`00000000 : 00000000`00000000 00000000`00000001 ffffb409`1babf5a0 ffffb409`1babf590 : 0xffff900a`898ce18c
@ianusa Could you please export logs and system info and send them to devteam@adguard.com? Looks like this is a compatibility issue.
@ianusa Could you please export logs and system info and send them to devteam@adguard.com? Looks like this is a compatibility issue.
Sure thing, just sent.
Same issue here: https://github.com/AdguardTeam/AdguardForWindows/issues/5062#issuecomment-2204229202
Logs and system info sent to devteam@adguard.com
I keeping hitting the BSOD again and over again even at the latest build (7.18.1 (4778)).
Already sent logs and crashdump twice to devteam@adguard.com but no response yet. Attach the crashdump for 7.18.1 even if the callstack is completely the identical. 072024-22953-01.dmp
Please bump up the priority to root cause it.
@ianusa in one of the other threads, Bitdefender antivirus was tracked down as the culprit. are you running the same software perchance?
@silverwings15 no, I don't install any AVs but Microsoft built-in one.
Same no Bitdfender her either.
We've updated the drivers in this version, please, check it out https://uploads.adguard.org/AdGuard-7.18.0-nightly-12-%284789%29.exe
related to #5218
Any chance this will land in beta soon? Thanks.
Here's another improvement, could you install this version please or just update through the app.
Please answer the following questions for yourself before submitting an issue
AdGuard version
7.17.2
Browser version
Chrome 126
OS version
Windows 11 23H2 (OS Build 22631.3810)
Traffic filtering
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Other
No response
Language-specific
No response
Which DNS server do you use?
DNS protection disabled
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
I've hit this issues a couple times randomly, and it always points to the Adguard's adgnetworktdidrv. ffffe00a
eb1f7008 fffff806
55a2be29 : 000000000000000a 00000000
00000008 0000000000000002 00000000
00000001 : nt!KeBugCheckEx ffffe00aeb1f7010 fffff806
55a27289 : 0000000000000000 00000000
00000000 0000000000000006 00000000
00000001 : nt!KiBugCheckDispatch+0x69 ffffe00aeb1f7150 fffff806
55a57926 : 0000000000000002 ffffb906
20fb5080 0000000000000000 00000000
00000000 : nt!KiPageFault+0x489 ffffe00aeb1f72e0 fffff806
55a412a2 : 0000000000000000 ffffb906
2e64a61c ffffb90618df6ae0 00000000
00000008 : nt!KiAcquireSpinLockInstrumented+0x56 ffffe00aeb1f7320 fffff806
5bda6bf5 : 000000000044baef ffffb905
f16c3d30 0000000000000000 00000000
00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x1a2db2 ffffe00aeb1f7350 fffff806
5bda7cdf : 0000000000000000 ffffb906
18df6ae0 0000000000000000 fffff806
00000000 : tdx!TdxObjectHeaderToTransport+0x25 ffffe00aeb1f7380 fffff806
5bda2fb8 : ffffb9062f50aa80 fffff806
5589ec0f ffffb90618df6a10 ffffb906
18df6a10 : tdx!TdxQueryInformationControlChannel+0x33 ffffe00aeb1f74d0 fffff806
558c1ab5 : 00000000c0000001 ffffb905
00000000 ffffb9062f34d401 ffffe00a
eb1f75a0 : tdx!TdxTdiDispatchInternalDeviceControl+0x1638 ffffe00aeb1f7500 fffff806
71aeac45 : ffffb905f16c3d30 0a00000d
6950bb63 00000000c0000001 ffffb906
2e64a61c : nt!IofCallDriver+0x55 ffffe00aeb1f7540 ffffb905
f16c3d30 : 0a00000d6950bb63 00000000
c0000001 ffffb9062e64a61c 00000000
00000000 : adgnetworktdidrv+0xac45 ffffe00aeb1f7548 0a00000d
6950bb63 : 00000000c0000001 ffffb906
2e64a61c 0000000000000000 00000000
00000000 : 0xffffb905f16c3d30 ffffe00a
eb1f7550 00000000c0000001 : ffffb906
2e64a61c 0000000000000000 00000000
00000000 0000000000000001 : 0x0a00000d
6950bb63 ffffe00aeb1f7558 ffffb906
2e64a61c : 0000000000000000 00000000
00000000 0000000000000001 ffffe00a
eb1f75a0 : 0xc0000001 ffffe00aeb1f7560 00000000
00000000 : 0000000000000000 00000000
00000001 ffffe00aeb1f75a0 ffffe00a
eb1f7590 : 0xffffb906`2e64a61cExpected Behavior
No response
Actual Behavior
No BSOD.
Screenshots
Screenshot 1
Additional Information
070524-22437-01.dmp