Getting BSOD saying dxgkrnl.sys failed after upgrade to wsl 2.0.9.0

[ballen-bw]

Windows Version

Microsoft Windows [Version 10.0.19045.3570]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 20.04 (possibly 22.04 - not sure since I wasn't able to access it anymore after the BSOD

Other Software

None

Repro Steps

After a fresh reboot, as soon as I try to start wsl, I get a BSOD that says "Stop code: SYSTEM_SERVICE_EXCEPTION, What failed: dxgkrnl.sys"

Expected Behavior

Expecting to see my Ubuntu wsl window open up

Actual Behavior

As soon as I try to start wsl, I get a BSOD that says "Stop code: SYSTEM_SERVICE_EXCEPTION, What failed: dxgkrnl.sys"

Diagnostic Logs

See minidump debug output below

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Windows BSOD / hangs on boot when using WSL2 (#5783), similarity score: 0.77

Closed similar issues:

• WSL 2 shows a KMODE_EXCEPTION_NOT_HANDLED BSOD upon installing a distro. (#7514), similarity score: 0.80
• Intermittent BSOD when using WSL2 (#10263), similarity score: 0.79
• After enabling WSL, if i open AIDA64, it will causes BSOD. (#5773), similarity score: 0.77
• enable wsl2 cause random bsod bluescreeen on win11 (#8205), similarity score: 0.76
• Errors on startup after upgrading to WSL2 2.0.0+ (#10585), similarity score: 0.76
• KB4566782 (OS Build 19041.450) breaks WSL 2 (#5760), similarity score: 0.76
• WSL throws error after upgrade to WSL2 (#10001), similarity score: 0.76
• Two drivers related to WSL causing Kernel Mode Heap Corruption BSOD? (#4504), similarity score: 0.75
• WSL2 fails to run any distros with error 0x80370102 (#7068), similarity score: 0.75

You can give me feedback by thumbs upping or thumbs downing this comment.

[ballen-bw]

Windows BSOD minidump debug output from windbg
dxgkrnl minidump debug.txt

[arnisjuraga]

+1

[Pitonuss]

+1

[shish456]

+1 Anyone know of a workaround?

[hetket]

+3 (3 machines in my group all facing this issue, probably more to come.

NOTE: I don't find any evidence of Windows updates in the log, so maybe this is something that changed on a server somewhere?

[arnisjuraga]

+1 Anyone know of a workaround?

Temporary workaround - disable all Virtualization settings in PC BIOS.
This will disable WSL in Windows, but will be able to login and use PC.

[hetket]

Actually, that doesn't work around the problem. WSL is what I need!

Also, my machine seems to be fine other than starting up WSL.

Another observation, WSL1 seems to work, only WSL2 fails to start.

[arnisjuraga]

@ballen-bw On what hardware/setup are you running your Windows? I have this issue on Dell laptop.

[shish456]

For us we have two Lenovo and two Dell laptops. I did all driver and Win updates yesterday on my Lenovo and no difference. We all have Win 10. We haven't tried Win 11 yet. We suspect the common hardware is NVIDIA video cards, but not sure about that.

Regarding @ballen-bw's log. It looks like a null pointer dereference. The mov instruction tries to read from rcx+0x164, and rcx is zero. 0x164 =356d, maybe someone can dig around the code to see what that might be. Maybe the source is online and wsl-specific (i.e. not related to the hardware)? Here are some links I found regarding dxgkrnl.sys:

https://www.theregister.com/2020/05/20/microsoft_directx_wsl_linux/
https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/display/directx-graphics-kernel-subsystem.md

If the issue is found, maybe it could be worked around with some hooks?:

https://github.com/NullTerminatorr/NullHook

[ballen-bw]

I'm running a Dell Latitude 7420. I think the problem was likely caused by one of the below "2023-11 Cumulative" Microsoft updates because my problems started on 11/14, the same day they were released. A couple of coworkers had the same problem just this week because my company pushes the updates out in phases so they weren't affected at the same time as me. I never found a work around - I ended up completely uninstalling WSL and using a VMWare workstation for now.

https://support.microsoft.com/en-us/topic/november-14-2023-kb5032189-os-builds-19044-3693-and-19045-3693-fe81e7e5-06bd-4e13-8233-4f7c07b1c512

https://support.microsoft.com/en-us/topic/november-14-2023-kb5032339-cumulative-update-for-net-framework-3-5-4-8-and-4-8-1-for-windows-10-version-22h2-5a292b74-4189-4c79-92f5-9f91544142ad

[ballen-bw]

Actually I think it may have been the 2023-10 Microsoft updates because I just found my coworker's problems started on 11/30 and they didn't have the 2023-11 updates installed yet, only the 2023-10 updates. Or it might have been the 2.0.9.0 WSL update:

[shish456]

We've had three people confirm that this is not a problem in Win 11.

[MrLesk]

We also have this problem. We all have Lenovo but only the ones that have dedicated Nvidia GPUs of series 1*** are affected

[cat-turnec9]

I have also started encountering this problem on a Dell Precision laptop running Windows 10. I have tried updating to the latest release 2.0.14.0 and the crash continues:

C:\> wsl --version
WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3693

[cotste]

I was able to stop the BSOD by adding gpuSupport=false to my $HOME/.wslconfig file, however, I am now getting a RPC failure mounting C:\Program Files\WSL\system.vhd. When this happens an event is logged to the application log stating vmcompute.exe has crashed calling kernelbase.dll.

I am able to mount system.vhd to a Linux VM in Hyper-V with no issues.

[cat-turnec9]

I was able to stop the BSOD by adding gpuSupport=false to my $HOME/.wslconfig file, however, I am now getting a RPC failure mounting C:\Program Files\WSL\system.vhd. When this happens an event is logged to the application log stating vmcompute.exe has crashed calling kernelbase.dll.

I can confirm that adding gpuSupport=false to .wslconfig avoids the bluescreen crash but also results in WSL failing to load with an error logged for vmcompute.exe in the Application Log:

Faulting application name: vmcompute.exe, version: 10.0.19041.3636, time stamp: 0x55bcba44
Faulting module name: KERNELBASE.dll, version: 10.0.19041.3636, time stamp: 0x326edcef
Exception code: 0xc06d007e
Fault offset: 0x000000000002cf19
Faulting process id: 0x4a40
Faulting application start time: 0x01da2d598064a20c
Faulting application path: C:\windows\system32\vmcompute.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll

[cotste]

We made some progress on this and identified a third party DLL that is causing the issue. The DLL is related to escalation management for non admin users - if you are using something like that this might be beneficial.

1. Manually started the vmcompute.exe process (Hyper-V Host Compute Service)
2. Identified the PID for vmcompute.exe
3. Executed: procdump64.exe -ma -e PID
4. Launched WSL2 distro which crashed vmcompute.exe
5. Analyzed the dump with WinDbg

It was pretty clear which DLL was faulting in the analysis, we uninstalled that software and WSL worked as expected.

[MrLesk]

After following the instructions from @cotste we found the problem being
c:\Program Files\Avecto\Privilege Guard Client\PGHook.dll

after renaming this dll to something else as a test, we didn't have any blue screen. We are still investigating if this software has a patch that fixes the problem.

[shish456]

Renaming PGHook.dll fixed it for me too. Thanks!

[soobinrho]

After following the instructions from @cotste we found the problem being c:\Program Files\Avecto\Privilege Guard Client\PGHook.dll

after renaming this dll to something else as a test, we didn't have any blue screen. We are still investigating if this software has a patch that fixes the problem.

@MrLesk Did Avecto release any patch that fixes this problem?

[MrLesk]

Hi @soobinrho
the affected dll seems to be related with BeyondTrust Privilege management V23.9.261.0

After updating to v 24.1.98.0 we didn't experience the problem again and no workaround was needed

[soobinrho]

Hi @soobinrho the affected dll seems to be related with BeyondTrust Privilege management V23.9.261.0

After updating to v 24.1.98.0 we didn't experience the problem again and no workaround was needed

Thank you! I really appreciate it.

[raffaeler]

Looks like this same issue:
BSOD on dxgkrnl when calling IsWsl2Guest

STACK_TEXT:  
fffff48a`e3ebec88 fffff806`3e9a5af5 : ffffd48e`1a820730 fffff806`3011a179 ffffd48e`1a820080 ffffe48d`67ae9818 : dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest
fffff48a`e3ebec90 fffff806`3e9a06cc : 00000000`00000000 ffffd48e`11b40050 ffffd48e`15ee1920 00000000`00000004 : dxgkrnl!DXGK_VIRTUAL_GPU_PARAV::ReadVirtualFunctionConfig+0x105
fffff48a`e3ebed10 fffff806`3e9a1911 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::ReadVirtualFunctionConfig+0x8c
fffff48a`e3ebed60 fffff806`3e7c7f4b : 00000000`00000000 fffff48a`e3ebeee0 00000000`00000000 00000000`00000004 : dxgkrnl!DxgkDdiReadVirtualFunctionConfig+0x51
fffff48a`e3ebedd0 fffff806`424d589d : ffffd48e`1fcfb410 fffff48a`e3ebeeb0 00000000`00000000 ffffd48e`1fcfbb00 : dxgkrnl!DpiDdiReadVirtualFunctionConfig+0x7b
fffff48a`e3ebee30 fffff806`424da1a0 : 00000000`00000001 ffffd48e`1fcfb6f0 ffffd48e`2cce0c18 00000000`00000000 : vpcivsp!MuxReadVfConfig+0x35
fffff48a`e3ebee70 fffff806`424bb760 : 00000000`00000000 ffffd48e`1fcfb410 00000000`00000000 00000000`00000000 : vpcivsp!VirtualDeviceSetBusMasterEnable+0x130
fffff48a`e3ebeee0 fffff806`424dfee5 : 00000000`00000000 00000000`00000000 ffffd48e`1fcfb410 fffff48a`e3ebf009 : vpcivsp!VirtualDeviceUnmapBARs+0x2e4
fffff48a`e3ebef50 fffff806`424e1403 : ffffd48e`2cce0c00 fffff48a`00000000 00002b71`d331f600 ffffd48e`0afd0a00 : vpcivsp!VirtualDeviceRemove+0x49
fffff48a`e3ebef80 fffff806`33fd9667 : ffffd48e`144b4d70 ffffd48e`145c6eb0 00002b71`d331f6c8 ffffd48e`14560220 : vpcivsp!VspEvtFileClose+0x243
fffff48a`e3ebf070 fffff806`33fd6dd5 : 00000000`00000000 fffff806`3003c500 00000000`00000008 ffffffff`ffffff00 : Wdf01000!FxPkgGeneral::OnClose+0xd7 [minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp @ 1791] 
fffff48a`e3ebf110 fffff806`33fda907 : 00000000`00000020 fffff806`30035ed2 ffffd48e`3754b920 ffffd48e`26c32920 : Wdf01000!FxPkgGeneral::Dispatch+0xa5 [minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp @ 808] 
fffff48a`e3ebf1e0 fffff806`30170847 : 00000000`00000000 ffffd48e`06d43a00 ffffd48e`144b6040 ffffd48e`1fe9ea80 : Wdf01000!FxDevice::DispatchWithLock+0x157 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] 
fffff48a`e3ebf240 fffff806`3030892b : ffffd48e`1fe9ea80 00000000`00000001 ffffd48e`144b6040 fffff806`301063f0 : nt!IopfCallDriver+0x53
fffff48a`e3ebf280 fffff806`3022d579 : ffffd48e`1fe9ea80 00000000`00000000 00000000`00000000 fffff48a`e3ebf2d8 : nt!IopPerfCallDriver+0xb3
fffff48a`e3ebf2b0 fffff806`3044289f : fffff48a`e3ebf4f9 ffffd48e`1fe9ea80 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x1f78d9
fffff48a`e3ebf2f0 fffff806`30446040 : ffffd48e`06d43a60 00000000`00000001 ffffd48e`1fe9ea50 ffffd48e`26c32920 : nt!IopDeleteFile+0x14f
fffff48a`e3ebf370 fffff806`30045c07 : 00000000`00000000 00000000`00000000 fffff48a`e3ebf4f9 ffffd48e`1fe9ea80 : nt!ObpRemoveObjectRoutine+0x80
fffff48a`e3ebf3d0 fffff806`3044b8a9 : ffffd48e`1fe9ea50 00000000`00000000 00000000`00000000 ffffd48e`1fe9ea50 : nt!ObfDereferenceObjectWithTag+0xc7
fffff48a`e3ebf410 fffff806`304ed885 : ffffd48e`12818078 fffff806`30045ef9 00000000`00000000 00000000`00000000 : nt!ObCloseHandleTableEntry+0x6c9
fffff48a`e3ebf550 fffff806`303e908d : ffffd48e`12818040 ffffd48e`1a820080 ffffffff`ffffff01 ffffd48e`26ffa4d8 : nt!ExSweepHandleTable+0xd5
fffff48a`e3ebf600 fffff806`30485ef0 : ffffffff`ffffffff ffffd48e`26ffa080 fffff48a`e3ebf650 fffff806`303f4604 : nt!ObKillProcess+0x35
fffff48a`e3ebf630 fffff806`3048da4e : ffffd48e`26ffa080 ffffe48d`4a5175f0 fffff48a`e3ebf859 00000000`00000000 : nt!PspRundownSingleProcess+0x204
fffff48a`e3ebf6c0 fffff806`30507f48 : ffffd48e`0000042b fffff806`30040801 00000000`00000001 0000007d`d86af000 : nt!PspExitThread+0x5f6
fffff48a`e3ebf7c0 fffff806`300c872d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
fffff48a`e3ebf800 fffff806`30202ee0 : 00000000`00000000 fffff48a`e3ebf8c0 fffff48a`e3ebfa00 00000000`00000000 : nt!KiDeliverApc+0x60d
fffff48a`e3ebf8c0 fffff806`3021161f : ffffd48e`1a820080 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff48a`e3ebfa00 00007ffb`e9d6d064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
0000007d`d8f7fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtWaitForSingleObject+0x14

[rob-nice]

We've also experienced this, and again found it was an issue with BeyondTrust. We tried updating to 24.1.108.0 but the issue still occurred.

Removing BeyondTrust from the system fixed it for us.

[raffaeler]

Removing BeyondTrust from the system fixed it for us.

@rob-nice Could you please elaborate this?

This could be my last action before removing WSL at all and switching to Ubuntu on the laptop as well.

[rob-nice]

Removing BeyondTrust from the system fixed it for us.

@rob-nice Could you please elaborate this?

This could be my last action before removing WSL at all and switching to Ubuntu on the laptop as well.

There are 2 installed programs that make up BeyondTrust BeyondTrust Privilege Management Cloud Adapter and Privilege Management for Windows.

I uninstalled both via windows "add or remove programs", rebooted the system when prompted and WSL worked without a BSOD again.

[raffaeler]

Thank you @rob-nice but I don't jave any of those installed on my machine.
Anyway, I occasionally see the same BSOD.
I'll have to uninstall WSL2 entirely then.

[TMWRA]

Removing BeyondTrust from the system fixed it for us.

@rob-nice Could you please elaborate this?
This could be my last action before removing WSL at all and switching to Ubuntu on the laptop as well.

There are 2 installed programs that make up BeyondTrust BeyondTrust Privilege Management Cloud Adapter and Privilege Management for Windows.

I uninstalled both via windows "add or remove programs", rebooted the system when prompted and WSL worked without a BSOD again.

This is exactly what happened with my office PC. I uninstalled them both and reinstalled the WSL. It works now.

[ajkessel]

Possibly same issue here. The problem is not consistently reproducible but I do get a dxgkrnl BSOD occasionally when restarting vmcompute to get around #5401 .

Windows 10.0.19045 / WSL 2.2.3
Device info

System SKU LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
Processor 12th Gen Intel(R) Core(TM) i7-1260P, 2100 Mhz, 12 Core(s), 16 Logical Processor(s)

windbg says

Kernel base = 0xfffff802`47400000 PsLoadedModuleList = 0xfffff802`4802a790
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8025e22596c, Address of the instruction which caused the BugCheck
Arg3: ffff838a10cfe4e0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4796

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11090

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

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

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


FILE_IN_CAB:  070524-17765-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8025e22596c

BUGCHECK_P3: ffff838a10cfe4e0

BUGCHECK_P4: 0

CONTEXT:  ffff838a10cfe4e0 -- (.cxr 0xffff838a10cfe4e0)
rax=0000000000000001 rbx=ffff838a10cff000 rcx=0000000000000000
rdx=0000000000000002 rsi=ffffdf046ce81a00 rdi=00000000000000d0
rip=fffff8025e22596c rsp=ffff838a10cfeee8 rbp=0000000000000000
 r8=0000000000000000  r9=ffff838a10cfedd8 r10=fffff8025e2b1220
r11=ffff838a10cfee10 r12=0000000000000000 r13=0000000000000004
r14=0000000000000002 r15=ffffdf045f021050
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:
fffff802`5e22596c 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

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  vmwp.exe

STACK_TEXT:  
ffff838a`10cfeee8 fffff802`5e434a55     : ffffdf04`68d679f0 fffff802`476afbc9 ffffdf04`68d67340 ffffa78d`916e9208 : dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest
ffff838a`10cfeef0 fffff802`5e42f62c     : 00000000`00000000 ffffdf04`5f022070 ffffdf04`612e58b0 00000000`00000004 : dxgkrnl!DXGK_VIRTUAL_GPU_PARAV::ReadVirtualFunctionConfig+0x105
ffff838a`10cfef70 fffff802`5e430871     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::ReadVirtualFunctionConfig+0x8c
ffff838a`10cfefc0 fffff802`5e257e4b     : 00000000`00000000 ffff838a`10cff140 00000000`00000000 00000000`00000004 : dxgkrnl!DxgkDdiReadVirtualFunctionConfig+0x51
ffff838a`10cff030 fffff802`7077589d     : ffffdf04`8c9d41e0 ffff838a`10cff110 ffffdf04`8c9d4900 ffffdf04`8c9d48d0 : dxgkrnl!DpiDdiReadVirtualFunctionConfig+0x7b
ffff838a`10cff090 fffff802`7077a1a0     : 00000000`00000001 ffffdf04`8c9d44c0 fffff802`707635e0 00000000`00000000 : vpcivsp!MuxReadVfConfig+0x35
ffff838a`10cff0d0 fffff802`7075b760     : 00000000`00000000 ffffdf04`8c9d41e0 ffffdf04`8c9d0000 ffffdf04`8c9d4900 : vpcivsp!VirtualDeviceSetBusMasterEnable+0x130
ffff838a`10cff140 fffff802`7076f8b6     : 00000000`00000000 00000000`00000000 ffffdf04`8c9d41e0 ffffdf04`8ead7d30 : vpcivsp!VirtualDeviceUnmapBARs+0x2e4
ffff838a`10cff1b0 fffff802`7076ca1e     : ffffdf04`68cd8540 000020fb`a0b6f588 ffff838a`10cff250 000020fb`820a3dc8 : vpcivsp!VpciIoctlUnmapMmioResources+0x18e
ffff838a`10cff200 fffff802`48fd9033     : ffffdf04`7df5c230 00000000`0022c078 ffffdf04`5f291de0 00000000`00000000 : vpcivsp!VspEvtIoDeviceControl+0x47e
ffff838a`10cff280 fffff802`48fd8a00     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`49062820 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x163 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3325] 
ffff838a`10cff320 fffff802`48fd7dfe     : ffffdf04`5f4f1020 ffffdf04`5f4f1000 00000000`00000000 fffff802`49067c88 : Wdf01000!FxIoQueue::DispatchEvents+0x520 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3125] 
ffff838a`10cff3f0 fffff802`48fd7b97     : ffffdf04`68d67300 00000000`000001d0 ffffdf04`68cd0000 ffffdf04`7b7f2010 : Wdf01000!FxPkgIo::EnqueueRequest+0x22e [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 697] 
ffff838a`10cff480 fffff802`7076c4f6     : 00000000`00000028 ffffdf04`5f490a70 00000000`00000000 ffffdf04`7df5c230 : Wdf01000!imp_WdfDeviceEnqueueRequest+0xc7 [minkernel\wdf\framework\shared\core\fxdeviceapi.cpp @ 2101] 
ffff838a`10cff4e0 fffff802`48fd7814     : 00000000`00000000 ffffdf04`54010000 ffffdf04`5f4bbc58 00000000`00000000 : vpcivsp!VspEvtIoInCallerContext+0x1a6
ffff838a`10cff5b0 fffff802`48fd723d     : ffff7865`a5149f00 ffffdf04`7b7f2010 ffffdf04`7df5c230 00000000`00000000 : Wdf01000!FxPkgIo::DispatchStep1+0x5c4 [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324] 
ffff838a`10cff670 fffff802`48fda907     : ffffdf04`7b7f2010 00000000`000000c0 00000000`000000e0 fffff802`47a2f321 : Wdf01000!FxPkgIo::Dispatch+0x5d [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 119] 
ffff838a`10cff6d0 fffff802`4762d935     : 00000000`00000000 00000000`00000000 ffffdf04`718e82c0 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0x157 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] 
ffff838a`10cff730 fffff802`47a2e30c     : 00000000`00000002 00000000`00000000 ffffdf04`70ca4780 ffffdf04`78c9a080 : nt!IofCallDriver+0x55
ffff838a`10cff770 fffff802`47a2df5a     : 00000000`0022c078 ffff838a`10cffac0 00000000`00000005 00000000`0022c078 : nt!IopSynchronousServiceTail+0x34c
ffff838a`10cff810 fffff802`47a2d236     : 00000000`00000000 00000000`00000a29 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xd0a
ffff838a`10cff960 fffff802`478119c5     : ffffdf04`68d67340 00000038`d947efa8 ffff838a`10cff9e8 00000038`d947f198 : nt!NtDeviceIoControlFile+0x56
ffff838a`10cff9d0 00007ff8`1514d0c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000038`d947efa8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`1514d0c4


SYMBOL_NAME:  dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest+0

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.4239

STACK_COMMAND:  .cxr 0xffff838a10cfe4e0 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_dxgkrnl!DXGVIRTUALMACHINE::IsWsl2Guest

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------