BSOD upon wsl install command

Anonymous

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://filestore.community.support.microsoft.com/api/images/de858948-db57-4dbd-97fa-27d1e160e408?upload=true&fud_access=wJJIheezUklbAN2ppeDns8cDNpYs3nCYjgitr%2BfFBh2dqlqMuW7np3F6Utp%2FKMltnRRYFtVjOMO5tpbpW9UyRAwvLeec5emAPixgq9ta07Dgnp2aq5eJbnfd%2FU3qhn54fVl3y1rVLV4wV2ps85dc47VmCHTZWFf4fG5Wy0YC6f2MMH%2FBmr7dYX0LHy%2B7LjURmnoJIuonLP%2Bet2fHx7J5bzx%2FbrbqWz2xouBVoym0IxSeCUfxicmKTM9qEv%2Flvvg7%2BFBM%2FOFMaQYHtK0BIPSqFJrr3Baz%2BwQMX%2FNUCZpsoreMEnwFoDaAcGZSLeGjkNWhSWx2oClWmEvNzfuV7f%2Fbx%2F0zDUL6hMYrvBjN4aaGtP5nWuP1aUgC15ExDXhK7xvKRyufQcP4IhDOAmWwD7gZhnQYXL2%2B3tlVvbrMDRly4yw%3D)

I looked at the memory dump it generated:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`21800000 PsLoadedModuleList = 0xfffff807`2242a770
Debug session time: Thu Mar  7 08:59:56.328 2024 (UTC - 6:00)
System Uptime: 0 days 0:02:53.989
Loading Kernel Symbols
...............................................................
................................................................
.............................Page 85ac28 not present in the dump file. Type ".hh dbgerr004" for details
...................................
................................................................
.......
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000a5`0ee4b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`21bfd5b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc805`28e8d5a0=000000000000003b
14: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80738425a0c, Address of the instruction which caused the BugCheck
Arg3: ffffc80528e8dea0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

*** WARNING: Check Image - Checksum mismatch - Dump: 0x3a4217, File: 0x3b2d78 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\6DD22F2D3aa000\dxgkrnl.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3374

    Key  : Analysis.Elapsed.mSec
    Value: 3516

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 406

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2417

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 112

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x3b

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest

    Key  : Failure.Hash
    Value: {1653d76e-587a-827c-afc4-0327e70c52dc}

    Key  : Hypervisor.Enlightenments.Value
    Value: 68673420

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 417df8c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80738425a0c

BUGCHECK_P3: ffffc80528e8dea0

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY.DMP

CONTEXT:  ffffc80528e8dea0 -- (.cxr 0xffffc80528e8dea0)
rax=0000000000000001 rbx=ffffc80528e8e9c0 rcx=0000000000000000
rdx=0000000000000002 rsi=ffffb5846ef92a60 rdi=00000000000000d0
rip=fffff80738425a0c rsp=ffffc80528e8e8a8 rbp=0000000000000000
 r8=0000000000000000  r9=ffffc80528e8e798 r10=fffff807384b2230
r11=ffffc80528e8e7d0 r12=0000000000000000 r13=0000000000000004
r14=0000000000000002 r15=ffffb5845de20030
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest:
fffff807`38425a0c 8a8164010000    mov     al,byte ptr [rcx+164h] ds:002b:00000000`00000164=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  vmwp.exe

STACK_TEXT:  
ffffc805`28e8e8a8 fffff807`38635bc5     : ffffb584`6c2e1730 fffff807`21b1a199 ffffb584`6c2e1080 ffff800d`d21ca778 : dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest
ffffc805`28e8e8b0 fffff807`3863079c     : 00000000`00000000 ffffb584`5de21050 ffffb584`6609a830 00000000`00000004 : dxgkrnl!DXGK_VIRTUAL_GPU_PARAV::ReadVirtualFunctionConfig+0x105
ffffc805`28e8e930 fffff807`386319e1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::ReadVirtualFunctionConfig+0x8c
ffffc805`28e8e980 fffff807`38457fcb     : 00000000`00000000 ffffc805`28e8eb00 00000000`00000000 00000000`00000004 : dxgkrnl!DxgkDdiReadVirtualFunctionConfig+0x51
ffffc805`28e8e9f0 fffff807`604e589d     : ffffb584`7052e560 ffffc805`28e8ead0 ffffb584`7052ed00 ffffb584`7052ec50 : dxgkrnl!DpiDdiReadVirtualFunctionConfig+0x7b
ffffc805`28e8ea50 fffff807`604ea1a0     : 00000000`00000001 ffffb584`7052e840 fffff807`604d35e0 00000000`00000000 : vpcivsp!MuxReadVfConfig+0x35
ffffc805`28e8ea90 fffff807`604cb760     : 00000000`00000000 ffffb584`7052e560 ffffb584`70520000 ffffb584`7052ed00 : vpcivsp!VirtualDeviceSetBusMasterEnable+0x130
ffffc805`28e8eb00 fffff807`604df8b6     : 00000000`00000000 00000000`00000000 ffffb584`7052e560 ffffb584`618dab00 : vpcivsp!VirtualDeviceUnmapBARs+0x2e4
ffffc805`28e8eb70 fffff807`604dca1e     : ffffb584`7d664340 00004a7b`a19faa88 ffffc805`28e8ec10 00004a7b`936a6e08 : vpcivsp!VpciIoctlUnmapMmioResources+0x18e
ffffc805`28e8ebc0 fffff807`23bd9033     : ffffb584`6c9591f0 00000000`0022c078 ffffb584`5ec22880 00000000`00000000 : vpcivsp!VspEvtIoDeviceControl+0x47e
ffffc805`28e8ec40 fffff807`23bd8a00     : ffffb584`6ffd6540 ffffb584`00000100 00000000`00000000 fffff807`23c62820 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x163 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3325] 
ffffc805`28e8ece0 fffff807`23bd7dfe     : ffffb584`5ec68020 ffffb584`5ec68000 00000000`00000000 fffff807`23c67c88 : Wdf01000!FxIoQueue::DispatchEvents+0x520 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3125] 
ffffc805`28e8edb0 fffff807`23bd7b97     : ffffb584`6c2e1000 00000000`000001d0 ffffb584`7d660000 ffffb584`61c0c990 : Wdf01000!FxPkgIo::EnqueueRequest+0x22e [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 697] 
ffffc805`28e8ee40 fffff807`604dc4f6     : 00000000`00000028 ffffb584`5e605570 00000000`00000000 ffffb584`6c9591f0 : Wdf01000!imp_WdfDeviceEnqueueRequest+0xc7 [minkernel\wdf\framework\shared\core\fxdeviceapi.cpp @ 2101] 
ffffc805`28e8eea0 fffff807`23bd7814     : 00000000`00000000 ffffb584`3f602000 ffffb584`5eba39a8 00000000`00000000 : vpcivsp!VspEvtIoInCallerContext+0x1a6
ffffc805`28e8ef70 fffff807`23bd723d     : ffffa9eb`5ccd9a00 ffffb584`61c0c990 ffffb584`6c9591f0 00000000`00000000 : Wdf01000!FxPkgIo::DispatchStep1+0x5c4 [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324] 
ffffc805`28e8f030 fffff807`23bda907     : ffffb584`61c0c990 00000000`000000c0 00000000`000000d0 fffff807`21e461f1 : Wdf01000!FxPkgIo::Dispatch+0x5d [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 119] 
ffffc805`28e8f090 fffff807`21a35cf5     : 00000000`00000000 00000000`00000000 ffffb584`60db00e0 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0x157 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] 
ffffc805`28e8f0f0 fffff807`21e451dc     : 00000000`00000002 00000000`00000000 ffffb584`713219a0 ffffb584`70abd080 : nt!IofCallDriver+0x55
ffffc805`28e8f130 fffff807`21e44e33     : 00000000`0022c078 ffffc805`28e8f480 00000000`00000005 00000000`0022c078 : nt!IopSynchronousServiceTail+0x34c
ffffc805`28e8f1d0 fffff807`21e44106     : 00000000`00000000 00000000`00000779 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xd13
ffffc805`28e8f320 fffff807`21c11135     : ffffb584`6c2e1080 000000a5`1077ed38 ffffc805`28e8f3a8 000000a5`1077ef28 : nt!NtDeviceIoControlFile+0x56
ffffc805`28e8f390 00007ffc`9b98d0c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000a5`1077ed38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`9b98d0c4

SYMBOL_NAME:  dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest+0

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

STACK_COMMAND:  .cxr 0xffffc80528e8dea0 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1653d76e-587a-827c-afc4-0327e70c52dc}

***moved from Windows / Windows 10 / Windows update, recovery, and backup***

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

11 answers

Anonymous

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

Anonymous

2024-03-09T15:36:37+00:00

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?
Please sign in to rate this answer.

0 comments No comments
Anonymous

2024-03-25T20:12:47+00:00

Isn't this driver essential for WSL to work?

https://devblogs.microsoft.com/directx/directx-heart-linux/
Please sign in to rate this answer.

0 comments No comments
Anonymous

2024-03-15T19:22:15+00:00
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 ]
Please sign in to rate this answer.

0 comments No comments
Anonymous

2024-03-16T11:19:23+00:00

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*
Please sign in to rate this answer.

0 comments No comments

Share via

BSOD upon wsl install command

11 answers