Blue Screen errors with WireGuardNT using two peers

Hiroshi Shirosaki h.shirosaki at
Wed Aug 4 00:34:13 UTC 2021

On Wed, Aug 4, 2021 at 2:25 AM Jason A. Donenfeld <Jason at> wrote:
> v0.4.1 is now released. Please see if that fixes the issue.

Thank you for the fix.
I tried and it works stably for now.

I confirmed windbg minidump result of the previous(v0.4.0) failure.
It shows the following.

2: kd> !analyze -v

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff801245e2d54, address which referenced memory

Debugging Details:

Hiroshi Shirosaki

More information about the WireGuard mailing list