Intermittent BSOD when using WSL2 #10263
Comments
|
WinDbg analyze -v on memory.dmp shows: Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64 Loading Dump File [C:\Windows\MEMORY.DMP] ************* Path validation summary **************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Debugging Details:Unable to load image \SystemRoot\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_fbb7d82167e332a4\igdkmd64.sys, Win32 error 0n2 KEY_VALUES_STRING: 1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: d1 BUGCHECK_P1: fffff804699d70e0 BUGCHECK_P2: 2 BUGCHECK_P3: 8 BUGCHECK_P4: fffff804699d70e0 READ_ADDRESS: fffff804699d70e0 IP_IN_PAGED_CODE: BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: vmmem DPC_STACK_BASE: FFFFF8045FAAEFB0 TRAP_FRAME: fffff80462e076e7 -- (.trap 0xfffff80462e076e7) UNALIGNED_STACK_POINTER: 028b000002f3e805 FAILED_INSTRUCTION_ADDRESS: STACK_TEXT: SYMBOL_NAME: dxgkrnl!DXG_SIGNAL_GUEST_CPU_EVENT_CBLT::ReleaseReference+0 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: AV_CODE_AV_PAGED_IP_dxgkrnl!DXG_SIGNAL_GUEST_CPU_EVENT_CBLT::ReleaseReference OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ae635c63-9e06-83a9-8a94-85ad66b99872} Followup: MachineOwner |
|
Thanks for reporting. Do you have crash reporting turned off? This kind of thing is more useful if the dumps are sent to Watson. The dumps can also be sent to secure@microsoft.com, considering there is what I think is an intel driver on that stack, it could be MS or Intel here. And as a general rule of thumb, don't post your kernel dumps on the public web. |
ghost
added
the
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
1 similar comment
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
|
Running into the same issue and found this post in a web search. System is stable until I start a Docker image with GPU acceleration enabled (using WSL2). Have run stress tests on CPU/memory and GPU for several hours without issue. I can run Hyper-V guests that have no GPU acceleration and have no stability issues there. The problem only seems to appear when I start up the docker image with the GPU acceleration, each time within an hour of it starting. |
|
BSOD here as well, how can I contribute to help solving this? did not turn off error reporting afaik. |
|
BUGCHECK_CODE: 18 see also closed but still an issue. the mentioned KB fix has nothing to do with it |
Windows Version
Microsoft Windows [Version 10.0.19045.3086]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
xrdp
Repro Steps
Not systematic. Intermittent. Could not find steps to reproduce more precise than:
Work with WSL2, involving remote desktop to access Linux GUI through xrdp, keep working for a few weeks.
Expected Behavior
No Blue Screen Of Death
Actual Behavior
BSOD happens intermittently:
070523-25968-01.dmp 7/5/2023 2:54:44 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff804
699d70e0 0000000000000002 0000000000000008 fffff804699d70e0 dxgkrnl.sys dxgkrnl.sys+d70e0 x64 ntoskrnl.exe+3fc030 C:\Windows\Minidump\070523-25968-01.dmp 8 15 19041 2,731,332 7/5/2023 2:59:06 PM060723-21187-01.dmp 6/7/2023 4:00:14 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff800
70c970e0 0000000000000002 0000000000000008 fffff80070c970e0 dxgkrnl.sys dxgkrnl.sys+d70e0 x64 ntoskrnl.exe+3fbca0 C:\Windows\Minidump\060723-21187-01.dmp 8 15 19041 2,660,596 6/7/2023 4:03:55 PM051723-21484-01.dmp 5/17/2023 1:18:19 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff807
3f6f60e0 0000000000000002 0000000000000008 fffff8073f6f60e0 dxgkrnl.sys dxgkrnl.sys+d60e0 x64 ntoskrnl.exe+3fbc10 C:\Windows\Minidump\051723-21484-01.dmp 8 15 19041 3,661,876 5/17/2023 1:24:08 PM032223-19937-01.dmp 3/22/2023 4:29:13 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff803
3eaa60e0 0000000000000002 0000000000000008 fffff8033eaa60e0 dxgkrnl.sys dxgkrnl.sys+d60e0 x64 ntoskrnl.exe+3fa110 C:\Windows\Minidump\032223-19937-01.dmp 8 15 19041 3,338,612 3/22/2023 4:32:12 PM032223-21078-01.dmp 3/22/2023 12:43:49 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffff805
860d60e0 0000000000000002 0000000000000008 fffff805860d60e0 dxgkrnl.sys dxgkrnl.sys+d60e0 x64 ntoskrnl.exe+3fa110 C:\Windows\Minidump\032223-21078-01.dmp 8 15 19041 2,991,428 3/22/2023 12:46:35 PMCall stack in this memory.dmp, and in previous dumps, as well, shows:
nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x463
dxgkrnl!DXG_SIGNAL_GUEST_CPU_EVENT_CBLT::ReleaseReference
dxgkrnl!DXG_HOST_GLOBAL_VMBUS::VmBusSendSignalGuestEventCblt+0xe5
dxgkrnl!DXG_HOST_GLOBAL_VMBUS::VmBusSendSignalGuestEvent+0x41
dxgmms2!VidSchiUnwaitMonitoredFences+0x11cf7
dxgmms2!VidSchiCompleteSignalSyncObject+0x9b
dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x1e5
dxgmms2!VidSchiProcessDpcCompletedPacket+0x70c
dxgmms2!VidSchDdiNotifyDpc+0x225
dxgkrnl!DxgNotifyDpcCB+0x92
igdkmd64+0x3b6a07
igdkmd64+0x80531
igdkmd64+0x65419
dxgkrnl!DpiFdoDpcForIsr+0x67
nt!KiExecuteAllDpcs+0x30e
nt!KiRetireDpcList+0x1f4
nt!KxRetireDpcList+0x5
nt!KiDispatchInterruptContinue
nt!KiDpcInterruptBypass+0x25
nt!KiInterruptDispatch+0xb1
0xfffff803`329c0003
nt!HvcallpExtendedFastHypercall+0x51
nt!HvcallpExtendedFastHypercallWithOutput+0x17
nt!HvcallFastExtended+0xc1ce8
winhvr!WinHvpVpDispatchLoop+0x326
winhvr!WinHvRunVpDispatchLoop+0x136
Vid!VidXSchedulerVpThreadStartRoutine+0x1af
nt!PspSystemThreadStartup+0x55
nt!KiStartSystemThread+0x28
NB: the same problem was happening with my previous machine as well.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: