Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Hiroshi Shirosaki <h.shirosaki@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Blue Screen errors with WireGuardNT using two peers
Date: Wed, 4 Aug 2021 09:34:13 +0900	[thread overview]
Message-ID: <CAOWZXk0q0ST7LA-S53UZYXqzhYeGzCtQGXfjuW=BJAONG9knkg@mail.gmail.com> (raw)
In-Reply-To: <50d9869c-0b89-c62e-35ff-79186413727c@zx2c4.com>

On Wed, Aug 4, 2021 at 2:25 AM Jason A. Donenfeld <Jason@zx2c4.com> 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.

FYI
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)

Thanks,
Hiroshi Shirosaki

  reply	other threads:[~2021-08-04  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  5:06 Hiroshi Shirosaki
2021-08-03 15:01 ` Jason A. Donenfeld
2021-08-03 17:25   ` Jason A. Donenfeld
2021-08-04  0:34     ` Hiroshi Shirosaki [this message]
2021-08-04  0:36       ` Jason A. Donenfeld

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='CAOWZXk0q0ST7LA-S53UZYXqzhYeGzCtQGXfjuW=BJAONG9knkg@mail.gmail.com' \
    --to=h.shirosaki@gmail.com \
    --cc=Jason@zx2c4.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).