WSL: Random crashes after latest upgrade to Windows 10 version 2004
(Apologies in advance if this is not the place to talk about this)
Environment
Windows build number: 10.0.19041.0
Your Distribution version: 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 2
Steps to reproduce
Ever since I had upgraded to windows version 2004 to use WSL2 (which is phenomenal btw), I’ve been experiencing random crashes in that there would be no BSOD but the laptop (x1 carbon) would abruptly shutdown. Looking at the event viewer I came across a Hypervisor warning event that appears to show up every time this shutdown occurs. This is the following message:
The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.
So I ran the command but I still got a random shutdown and this time the event preceeding the shutdown was the following informational level event:
Hypervisor configured mitigations for CVE-2019-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 for virtual machines.
Processor not affected: true
Processor family not affected: false
Processor supports microarchitectural buffer flush: false
Buffer flush needed: false
I’m not entirely sure if these mitigations are what’s causing the problems or if it’s just a red herring. I tried looking for this online but only came to this post https://answers.microsoft.com/en-us/windows/forum/all/random-shutdowns/1e10ef74-3247-444b-ab64-c0ad18543f80 with no clear resolution. Any guidance around this would be great!
Expected behavior
Don’t randomly cause crashes.
Actual behavior
Randomly causing crashes
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 3
- Comments: 51 (3 by maintainers)
Doesn’t look like Windows 11 fixed the issue either. I’m having this issue ever since I started using WSL on windows 11 22000.438
should we execute the command
as ig it might cause the VMWare/Virtual box to stop working.
I spoke too soon 😢 The problem occurred again but with a new event log saying
The driver \Driver\WUDFRd failed to load for the device ROOT\DISPLAY\0000.I’m getting this error after the latest windows update and I don’t even have WSL. 😠
I guess it’s all operating system in virtualization that to always running, so it can sometimes crash as many virtual tools stop responding, so does wsl. So my advice is to
whenever we are not using ubuntu, by the fact to learn more in-depth features of Linux we should use Virtual box or VMWare workstation as some internal features are stopped Overall it is a Pretty good part of windows to get Linux on windows.