One of our staff encountered an interesting crash in WireGuard for
Windows 0.3.9 today. At first, the WireGuard log was slammed by this
message repeatedly:

Failed to send data packet: An operation on a socket could not be
performed because the system lacked sufficient buffer space or because
a queue was full.

It looks like WireGuard eventually hit a panic in rio_windows.go [1]
and died. The panic message was "cq is corrupt".

The computer is a Lenovo ThinkPad P15v, model 20TRS00Q00. It's running
Windows 10 20H2 and WireGuard for Windows version 0.3.9.

We checked the Windows Update history and it didn't look like any
relevant Windows or driver updates coincided with the crash. We didn't
see anything in the Windows System or Application event logs that
pointed to a root cause.

What was left of the WireGuard log is attached. If we can provide any
further information to help with debugging let us know.

[1] https://github.com/WireGuard/wireguard-go/blob/3c11c0308e4e9fae76e1531f4f49a39f1ae24253/conn/winrio/rio_windows.go#L196

Joshua Sjoding
SCJ Alliance
IT Specialist
www.scjalliance.com