Repository navigation
Description
Windows Version
Microsoft Windows [Version 10.0.26300.9818] (Windows 11 Pro 26H2)
WSL Version
2.7.14.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.33.2-microsoft-standard-WSL2
Distro Version
Debian GNU/Linux 13 (trixie)
Other Software
vfpext.sysfile version 10.0.26100.9168- Hardware: Intel NUC 13 Extreme (i5-13600K), AMD RX 6900 XT, Intel I226-V + Marvell AQtion 10GbE NICs, Killer AX1690i Wi-Fi
- Sleep state: S3 (Modern Standby disabled via
PlatformAoAcOverride=0); VBS/HVCI enabled - Several virtual NICs present at the time of the crash: WireGuard for Windows (wireguard-nt 1.1.0.0, 2 active tunnels + 4 orphaned adapters, one on driver 0.10.0.0), a commercial WireGuard-based VPN client, OpenVPN 2.7 (TAP-Windows6 + DCO adapters), Npcap 0.9982 loopback, Bluetooth PAN
.wslconfig:
[wsl2]
networkingMode=mirrored
firewall=trueRepro Steps
- Run WSL 2 with
networkingMode=mirroredon a host with multiple physical and virtual NICs. - Keep a distro running and put the machine to sleep (S3).
- Resume with the power button after several hours.
Not deterministically reproducible: the machine resumes fine most of the time. This crash happened once after a session with 12 days of uptime and multiple successful sleep/resume cycles.
Expected Behavior
The system resumes from S3 and WSL keeps running.
Actual Behavior
Bugcheck 7 seconds into resume, followed by a cold boot. All running WSL sessions (and everything else) are lost.
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation
Arg4: fffff8044ce25b88, address which referenced memory
PROCESS_NAME: svchost.exe
SYMBOL_NAME: vfpext!SxFindContextByName+1b4
IMAGE_NAME: vfpext.sys
FAILURE_BUCKET_ID: AV_vfpext!SxFindContextByName
Debug session time: Tue Nov 10 13:56:47.202 2026 (UTC + 1:00)
System Uptime: 12 days 11:55:19.309
Stack:
nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x478
vfpext!SxFindContextByName+0x1b4
vfpext!VfpDeviceIoControl+0x1d3
ndis!ndisDummyIrpHandler+0x65
nt!IofCallDriver+0x84
nt!IopCallDriverReference+0xe6
nt!IopSynchronousServiceTail+0x30b
nt!IopXxxControlFile+0x9a3
nt!NtDeviceIoControlFile+0x5e
nt!KiSystemServiceCopyEnd+0x25
So a user-mode svchost.exe (presumably HNS, configuring the mirrored vSwitch ports as the host NICs come back up on resume) issues an IOCTL to VFP, and SxFindContextByName dereferences NULL at DISPATCH_LEVEL.
Possibly related observation: in the hours before the machine went to sleep, the System log contained a Microsoft-Windows-Hyper-V-VmSwitch event 291 ("RSC offload modified for NIC ... (Friendly Name: )") every 2 to 5 minutes, i.e. the mirrored NIC was being reconfigured continuously.
Diagnostic Logs
collect-wsl-logs.ps1 could not be captured: the crash happens during resume and takes down the host, so there is no live session to trace.
The kernel minidump (111026-24218-01.dmp, ~5 MB) is available. I'd rather not attach it publicly because a minidump can contain memory contents. Happy to share it privately (e.g. via Feedback Hub, or by email to a Microsoft address) if that's useful.
Activity
github-actions commentedon Nov 10, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
OneBlue commentedon Nov 10, 2026
/bsod
microsoft-github-policy-service commentedon Nov 10, 2026
Hello! Could you please provide a kernel dump to help us better diagnose your issue? To collect a kernel dump, follow 10) Reporting a Windows crash (BSOD)
Thank you!