Windows 11 running WSL2 crashes on hypervisor requesting CPU idle

[yakopov-dlg]

Windows Version

Microsoft Windows [Version 10.0.26100.8655]

WSL Version

2.7.8.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.18.33.1-microsoft-standard-WSL2

Distro Version

Ubuntu-26.04

Other Software

VSCode 1.126.0

Repro Steps

The problem does not seem to very clearly depend on specific activity conducted and from the user perspective reboots happen randomly (i.e. I cannot replicate them on purpose). The only way to replicate is to wait for it to happen (and it eventually does).

Expected Behavior

Apart from these sudden reboots I have no complaints and my Ubuntu seems to be working as expected, as does Windows.

Actual Behavior

I am running Windows 11 on Dell Pro 14 Plus PB14250 (Intel U235). After installing WSL2 and Ubuntu on it I started to experience periodical sudden crash-reboots (1-4 times a day on average), with the minidump files created before the crash pointing at the problem with Hypervisor trying to switch CPU state (please see this example minidump analysis attached).

Diagnostic Logs

Two example minidump (kd analyze output):
2026-06-22 minidump analysis.txt
2026-06-16 minidump analysis.txt

My drivers and firmware versions from Dell Command Center utility:
MySystemInformation.xml

[github-actions]

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:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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 networking instead, following the instructions in Collect WSL logs for networking issues

Once 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'.

[yakopov-dlg]

Attached the logs as requested. When running, log collection script complained about something but still finished:

>> .\collect-wsl-logs.ps1
Get-WindowsOptionalFeature: C:\Users\A245312\Desktop\Dell\collect-wsl-logs.ps1:188
Line |
 188 |  Get-WindowsOptionalFeature -Online > $folder/optional-components.txt
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Class not registered
Log collection is running. Please reproduce the problem and once done press any key to save the logs.
Saving logs...
100%  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]
Logs saved in: C:\Users\Username\Desktop\Dell\WslLogs-2026-06-26_15-53-12.tar.gz. Please attach that file to the GitHub issue.

WslLogs-2026-06-26_15-53-12.tar.gz

[github-actions]

Diagnostic information

Detected appx version: 2.7.8.0

[OneBlue]

/bsod

[yakopov-dlg]

I have provided minidump information in the ticket, but if a full dump is needed, then it may take time because it is a corporate laptop and I need to get a permission for that, and then wait for the crash to happen. I will update the ticket later.

[OneBlue]

@yakopov-dlg: I don't the minidump on the issue (only the analyze output)

/bsod

[microsoft-github-policy-service]

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!