WireGuardNT BSOD Windows 10 21H1 Mullvad

WireGuardNT BSOD Windows 10 21H1 Mullvad

[Andre Christanto]

[-- 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 --]

Re: WireGuardNT BSOD Windows 10 21H1 Mullvad

[Jason A. Donenfeld]

Hi Andre,

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.

Thanks,
Jason

Re: WireGuardNT BSOD Windows 10 21H1 Mullvad

[Jason A. Donenfeld]

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

Re: WireGuardNT BSOD Windows 10 21H1 Mullvad

[Peter Whisker]

Hi

Yes, I saw similar BSOD on a workstation I run yesterday but as it is 
remote it's a nuisance if I have to go and restart it in safe mode to 
disable the kernel flag. I may get to re-try it later in the week.

However my work laptop has been rock solid with the WireguardNT driver 
and now works both directly and also through a PulseSecure tunnel, 
running a total of three tunnels and six peers simultaneously. :)

Peter

On 03/08/2021 11:20, Andre Christanto wrote:
> 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

Re: WireGuardNT BSOD Windows 10 21H1 Mullvad

[Jason A. Donenfeld]

On Wed, Aug 4, 2021 at 12:05 PM Peter Whisker <peter.whisker@gmail.com> wrote:
> Yes, I saw similar BSOD on a workstation I run yesterday but as it is
> remote it's a nuisance if I have to go and restart it in safe mode to
> disable the kernel flag. I may get to re-try it later in the week.

Can you confirm that the BSOD was on 0.4 and not on 0.4.1? It's
important for me to know whether this is a new bug or just a
non-contributing "me too" for the old one. If this is a crash on
0.4.1, can you send me C:\windows\memory.dmp or
C:\windows\minidump\*.dmp ?

Thanks,
Jason

Re: WireGuardNT BSOD Windows 10 21H1 Mullvad

[Peter Whisker]

The original 0.4

On 04/08/2021 12:17, Jason A. Donenfeld wrote:
> On Wed, Aug 4, 2021 at 12:05 PM Peter Whisker <peter.whisker@gmail.com> wrote:
>> Yes, I saw similar BSOD on a workstation I run yesterday but as it is
>> remote it's a nuisance if I have to go and restart it in safe mode to
>> disable the kernel flag. I may get to re-try it later in the week.
> Can you confirm that the BSOD was on 0.4 and not on 0.4.1? It's
> important for me to know whether this is a new bug or just a
> non-contributing "me too" for the old one. If this is a crash on
> 0.4.1, can you send me C:\windows\memory.dmp or
> C:\windows\minidump\*.dmp ?
>
> Thanks,
> Jason