BSOD upon wsl install command

Question

After recent updates to my laptop (windows 10 Enterprise), upon starting docker desktop, laptop goes to bluescreen.

I have uninstalled docker desktop.

turned off wsl, hyper-v, restarted and turned on back

updated nvdia drivers.

still it goes to bluescreen after wsl --install with error

WslRegisterDistribution failed with error: 0x8037011e Error: 0x8037011e The host compute system service has disconnected unexpectedly.

![](https://learn-attachment.microsoft.com/api/attachments/de858948-db57-4dbd-97fa-27d1e160e408?platform=QnA

Answer 1

I had the same issue with Docker 4.28.0 causing BSOD it all started sometime after 3/25/2024.

And had been working fine for a few months before this started happening.

I have Windows 10 22H2, build 19045.4170, Enterprise

I tried all the usual things

graphic drivers,

dxdiag

sfc /scannow

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

Tried earlier versions of docker

uninstall/install wsl from windows features

wsl --update

Nothing worked.

As soon as docker was in the process of starting up, I would get the BSOD, showing:
SYSTEM_SERVICE_EXCEPTION

dxgkrnl.sys

As far as Windows updates here's what I show from Update History:

The only update that I see was installed on 3/25/2024:

"Security Update for Windows (KB5035845)"

This takes me to the same place as the 3/26/2024 update listed below.

March 12, 2024—KB5035845 (OS Builds 19044.4170 and 19045.4170) https://support.microsoft.com/en-us/topic/march-12-2024-kb5035845-os-builds-19044-4170-and-19045-4170-24e9864f-0756-457e-bce9-3f681020d591

Before that the last one was installed on: 2/15/2024 and it was working after that.

I installed this one on 3/26/2024, while troubleshooting just in case it would fix it, but it didn't:

"2024-03 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5035845)"
Same link as the Security Update above.

March 12, 2024—KB5035845 (OS Builds 19044.4170 and 19045.4170)

https://support.microsoft.com/en-us/topic/march-12-2024-kb5035845-os-builds-19044-4170-and-19045-4170-24e9864f-0756-457e-bce9-3f681020d591

memory.dmp file looked similar to above.

After 30+ attempts that each ended with BSOD, I finally gave up trying to make it work.

Uninstalled docker and reinstalled it to use Hyper-V instead of WSL and was able to get back up and running again.

Answer 2

Take ownership of a file or folder to C:\Windows\System32\drivers\dxgkrnl.sys

Create new system restore point before making changes

for a temporary fix, remove this dxgkrnl.sys file **** from this path *C:\Windows\System32\drivers*

Answer 3

I am seeing the same issue. My BSOD is identical (having trouble posting images)

winver 22H2 (OS Build 19045.3930)

I had wsl working fine with both ubuntu and kali distributions for about 2 months.

It all stopped working on 2/26.

I noticed 3 updates had been pushed by corporate IT. In the update dxgkrnl.sys had been updated (File Version 10.0.19041.3996).

• KB5034763
• KB5034466
• Servicing Stack 10.0.19041.3989

I tried

• removing all distributions and reinstalling.
• removing wsl itself and reinstalling.
• I ran dism and sfc
• updated all graphics drivers and repeated all the above

I uninstalled KB5034763 & KB5034466 but cant remove Servicing Stack 10.0.19041.3989.

Dxgkrnl.sys reverted to previous version. (1/19/2024)

File Version 10.0.19041.3758

Issue persists

The crash dump says

Caused_by_Driver [dxgkrnl.sys ]

Caused_by_Address [dxgkrnl.sys+25a0c ]

File_Description [DirectX_Graphics_Kernel ]

Product_Name [Microsoft®_Windows®_Operating_System ]

Company [Microsoft_Corporation ]

File_Version [10.0.19041.3758_(WinBuild.160101.0800) ]

Processor [x64 ]

Crash_Address [ntoskrnl.exe+3fd6f0 ]

Stack_Addr_1 [ ]

Stack_Addr_2 [ ]

Stack_Addr_3 [ ]

Computer_Name [ ]

Full_Path [C:\windows\DUmp\Minidump\031524-19828-01.dmp]

Processor_Count [12 ]

Major_Version [15 ]

Minor_Version [19041 ]

Dump_File_Size [2695771 ]

Dump_File_Time [3/15/2024__10:33:54_AM ]

Answer 4

Thanks for the reply.

Not sure why it shows that. here is the screenshot of the winver

Is there anything I can verify or can install?

Answer 5

Hi Paila,

Based on the logs it seems the devices is on an old build of Windows 10

Can you verify by running winver?

The logs are showing 10.0.19041.1 this is Windows 10 2004 released early 2020 with no updates

Supported versions of Windows 10 are listed here, updating to Build 19044 (21H2) or 19045 (22H2) will possibly fix your issue too.

https://learn.microsoft.com/en-us/windows/release-health/release-information