robmikh
commented
5 hours ago Generally, crashes will be reported to us through diagnostic systems.
These seem unrelated to your previous issue. Unfortunately, the first and third dumps don't seem to have any actionable information. Your second dump seems to be caused by a device lost event, as the error code is DXGI_ERROR_DEVICE_REMOVED. It appears there's a bug internally that if this happens at an inopportune time, we don't properly bubble up the error. Thanks for bringing it to our attention, I've filed a bug internally.
In general, when you receive DXGI_ERROR_DEVICE_REMOVED, you'll need to create a new D3D11 device and recreate all of your D3D11 resources. After that you will need to call Recreate on your frame pool with the new device.
I'm going to close this issue for now. Feel free to ask questions.
Based on the code implementation logic in the previous post(https://github.com/microsoft/Windows.UI.Composition-Win32-Samples/issues/138), I also encountered a crash issue on GraphicsCapture!winrt::throw_hresult. Can anyone give me some optimization suggestions to resolve this? The following is the relevant crash dump and call stack. may be it can locate the problem faster sdkdump-2024-11-05-15-08-09.dmp
sdkdump-2024-10-29-15-41-51.dmp
sdkdump-2024-11-05-07-47-08.dmp