Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andre Christanto <christantoandre@gmail.com>, wireguard@lists.zx2c4.com
Subject: Re: WireGuardNT BSOD Windows 10 21H1 Mullvad
Date: Tue, 3 Aug 2021 19:25:46 +0200	[thread overview]
Message-ID: <0253f078-4d5a-25ce-36c9-02d917dd2e54@zx2c4.com> (raw)
In-Reply-To: <3f38eb92-9ed6-5903-d96c-3161de5330f7@zx2c4.com>

On 8/3/21 5:00 PM, Jason A. Donenfeld wrote:
> On 8/3/21 12:20 PM, Andre Christanto wrote:
>> 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)
> 
> Thank you for the bug report. I fixed a similar sounding bug yesterday, 
> but perhaps this is a new one. Do you think you could send me the files 
> in the C:\windows\minidump directory? It's probably best to mail these 
> to me personally rather than sending them to the mailing list.

v0.4.1 is now released. Please see if that fixes the issue.

Jason

  reply	other threads:[~2021-08-03 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 10:20 Andre Christanto
2021-08-03 15:00 ` Jason A. Donenfeld
2021-08-03 17:25   ` Jason A. Donenfeld [this message]
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=0253f078-4d5a-25ce-36c9-02d917dd2e54@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=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).