The error is in the kernel, but somehow the DisplayLink driver is triggering it. I just used the commands from the link and according to those commands the DisplayLink driver shows up as the cause (I'm not a windbg expert, so I wasn't sure the commands to use until I found that link). I agree, the crash is different than the link I posted. Ref: 29287 - BSoD at sleep resume after updating to RS5 v1809 w/ Intel HD 4600 I need someone from engineering to look at that. There's no easy culprit visible from the tool as the last calls and the trip are with DirectX.Īs expected, our driver is no in the stack as it's a kernel crash. I've ran the windbg tool and your BSoD code is the same as the website you quoted, but the reason it trips is different.įAILURE_BUCKET_ID: 0x9F_3_dxgkrnl!DpiFdoHandleDevicePower
0 kommentar(er)
