Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL 2 shows a KMODE_EXCEPTION_NOT_HANDLED BSOD upon installing a distro. #7514

Closed
1 of 2 tasks
catink123 opened this issue Oct 9, 2021 · 6 comments
Closed
1 of 2 tasks

Comments

@catink123
Copy link

catink123 commented Oct 9, 2021

Windows Build Number

Microsoft Windows [Version 10.0.22000.194]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

Enable Windows Subsystem for Linux feature.
Change to WSL 2 with wsl --set-default-version 2.
Install 'Ubuntu' from Microsoft Store.
Launch the Ubuntu application.

Expected Behavior

Ubuntu installs itself and shows first time setup.

Actual Behavior

The window shows 'Installing, this may take a few minutes`. Then, after 2-3 seconds the whole system hangs and then a BSOD pops up with error KMODE_EXCEPTION_NOT_HANDLED. The file that it shows is dxgmms2.sys.

Diagnostic Logs

No response

@larahfelipe
Copy link

I'm having the exact same issue after installed Windows 11. I've tried to find for some solution, but I didn't have any success.. Idk, but seems like it's some kind of incompatibility between the Windows 11 kernel and the graphic drivers currently available - in my case, AMD. Guess we'll have to wait for updates..

@obrobrio2000
Copy link

obrobrio2000 commented Oct 23, 2021

I'm having the exact same issue after installed Windows 11. I've tried to find for some solution, but I didn't have any success.. Idk, but seems like it's some kind of incompatibility between the Windows 11 kernel and the graphic drivers currently available - in my case, AMD. Guess we'll have to wait for updates..

Same for me (AMD also in my case). Had to go back to Win10 just because of this. I already tried solutions like setting TdrDelay in registry, reinstalling GPU drivers etc. but the issue persists. If you enable not only WSL (and Virtual Machine Platform) but also HyperV and Hypervisor Platform the BSOD happens at boot, I couldn't even go past the logon screen.

EDIT: It happens both with WSL optional function and with WSL store app.

@catink123
Copy link
Author

I have an AMD processor, so I think it is the compatibility problem. I also tried reinstalling GPU drivers and everything suggested by guides online, none of it worked. At first I thought there were problems with two things: the fact that my CPU (AMD FX-6300) doesn't support TPM at all and that I updated from Windows 10 to Windows 11 using some hacky guides with scripts. Yesterday I made a fresh install of Windows 11 and I still have the same BSOD. I guess we'll have to wait for compatibility fixes for AMD CPUs (or maybe I just need to upgrade my machine already)... Thanks for all the responses!

@asvishnyakov
Copy link

Hi guys, did you had a chance to solve issue?

@catink123
Copy link
Author

Nope, still using Windows 10 with WSL2 as I thought that my processor/motherboard is old enough for everything to break on Windows 11. However, using Windows 11 on a 9 year old unsupported laptop is flawless and even WSL2 works fine. Maybe it's about the difference between Intel and AMD processors.

@larahfelipe
Copy link

No. as expected, it's definitely an incompatibility between old hardware and Windows 11. In my case, I've hacked to install Windows 11 without TPM 2, since my old AMD FX processor and motherboard don't support it, but after many incompatibility issues that I've experienced, I got back to Windows 10.
Tbh, I don't think there's much you can do about it. If you really want to use Windows 11, then you probably should consider upgrading your PC to more recent hardware like I did last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants