Blue Screen errors with WireGuardNT using two peers

[Jason A. Donenfeld]

Hi Hiroshi,

> I confirmed windbg minidump result of the previous(v0.4.0) failure.
> It shows the following.
>
> 2: kd> !analyze -v
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
> 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.
> Arguments:
> Arg1: 0000000000000024, memory referenced
> Arg2: 0000000000000002, IRQL
> Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
> Arg4: fffff801245e2d54, address which referenced memory
>
> Debugging Details:
> ------------------
> (snip)

Thank you for letting me know that 0.4.1 fixes the issue. With regards
to your windbg - could you send the snipped part, just to be sure?

Jason