WireGuardNT BSOD Windows 10 21H1 Mullvad

Peter Whisker peter.whisker at gmail.com
Wed Aug 4 10:02:07 UTC 2021


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. :)


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

More information about the WireGuard mailing list