From: Shiv Patel <spatel@cloudflare.com>
To: wireguard@lists.zx2c4.com
Cc: Thibault Martin-Lagardette <thibault-ml@cloudflare.com>,
Kyle Krum <kkrum@cloudflare.com>
Subject: WinTun - Blue Screen on Windows (DPC_WATCHDOG_VIOLATION)
Date: Fri, 5 May 2023 11:14:45 -0700 [thread overview]
Message-ID: <CADcrW6+_s9qyS2MfQxmkAY8TSis8+h1uXBwWTMJE3g+97k_eMw@mail.gmail.com> (raw)
I am a Product Manager at Cloudflare working on our WARP application.
As of Cloudflare WARP Version 2023.3.381.0, we are using WinTun to
setup our wireguard tunnel and it had been working great. In the last
few days we’ve received several reports regarding a Blue Screen of
Death on Windows 10 and Windows 11 devices when the product is turned
on.
The error code is DPC_WATCHDOG_VIOLATION(133). Args aren usually something like
Arg1: 0000000000000001, The system cumulatively spent an extended
period of time at DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8017a4fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK,
which contains additional information regarding the cumulative timeout
Arg4: 0000000000000000
The function is usually different each time, but all in tpcip.sys.
Here are a few examples
SYMBOL_NAME: tcpip!RtlAcquireScalableWriteLock+15
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
IMAGE_VERSION: 10.0.19041.1221
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 15
FAILURE_BUCKET_ID: 0x133_ISR_tcpip!RtlAcquireScalableWriteLock
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5c8b9f1f-7ae1-233f-1a70-950d5491c936}
OR
SYMBOL_NAME: tcpip!IppFindOrCreatePath+f47
MODULE_NAME: tcpipIMAGE_NAME: tcpip.sys
IMAGE_VERSION: 10.0.19041.1221
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: f47
FAILURE_BUCKET_ID: 0x133_ISR_tcpip!IppFindOrCreatePath
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {bf177f95-f651-3035-3f86-b46e476b90e2}
Followup: MachineOwner
OR
SYMBOL_NAME: tcpip!IppFindBestSourceAddressOnInterfaceUnderLock+107
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 107
FAILURE_BUCKET_ID: 0x133_ISR_tcpip!IppFindBestSourceAddressOnInterfaceUnderLock
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2e016b48-a7c2-0910-9f41-71eded0c9f01}
Has anyone seen this on WinTun? We can’t find any commonality between
windows versions, hardware, software on the devices. Hoping this is a
known issue.
reply other threads:[~2023-12-20 4:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADcrW6+_s9qyS2MfQxmkAY8TSis8+h1uXBwWTMJE3g+97k_eMw@mail.gmail.com \
--to=spatel@cloudflare.com \
--cc=kkrum@cloudflare.com \
--cc=thibault-ml@cloudflare.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).