From: Andre Christanto <christantoandre@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: WireGuardNT BSOD Windows 10 21H1 Mullvad
Date: Tue, 3 Aug 2021 17:20:35 +0700 [thread overview]
Message-ID: <CAB5RCdEyyeGdeBrviTTjF3EyrfNWrCsUXqFbW+RUgqjKeDUrNQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi all,
Thank you very much for developing WireGuard. I have been using it
daily for all my VPN needs.
This is my first time using mailing list, so please give me feedback
if I'm using this wrong.
Today after I received notification that an update was available, I
immediately update my WireGuard installation and while waiting for the
installation to complete, I enabled the ExperimentalKernelDriver flag.
After the update was completed and WireGuard automatically reconnected
my VPN connection, my Windows almost immediately got BSOD (~2-3s after
VPN connected notification) and keep getting it after restarts (I set
my account to auto-login). Thinking that maybe I shouldn't enable the
flag immediately after an update, I disabled the flag through Safe
Mode. But after a restart and enablement of the flag, I still got BSOD
after WireGuard was connected. In the end, I decided to disable
WireGuardNT for now and report this feedback.
I am using WireGuard on my Windows 10 x64 21H1 installation. My VPN
provider is Mullvad and I am connected through wireless (Wi-Fi 5)
connection using Intel 9260 network card. I also attached WireGuard's
log to this email.
Please let me know if you need more information.
Thank you very much for the support!
Best regards,
Andre Christanto
[-- Attachment #2: wireguard-log-2021-08-03T170801.zip --]
[-- Type: application/x-zip-compressed, Size: 16017 bytes --]
next reply other threads:[~2021-08-03 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 10:20 Andre Christanto [this message]
2021-08-03 15:00 ` Jason A. Donenfeld
2021-08-03 17:25 ` Jason A. Donenfeld
2021-08-04 10:02 ` Peter Whisker
2021-08-04 11:17 ` Jason A. Donenfeld
2021-08-04 15:54 ` Peter Whisker
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=CAB5RCdEyyeGdeBrviTTjF3EyrfNWrCsUXqFbW+RUgqjKeDUrNQ@mail.gmail.com \
--to=christantoandre@gmail.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).