You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run my Application in "AMD Radeon 780M " display card, when I mouse click some region, I will create vertex Buffer and index buffer, But I get a runtime error: "Message = "HRESULT: [0x887A0005], Module: [Vortice.DXGI], ApiCode: [DXGI_ERROR_DEVICE_REMOVED/DeviceRemoved], Message: [GPU 设备实例已经暂停。使用 GetDeviceRemovedReason 以确定相应的措施。\r\n]" with ResultCode "887A0005". But some time is ok, some time is get this error! I try to get removed reason by device.DeviceRemovedReason, it tell me: "Description = "GPU 不响应更多的命令,最为可能的原因是调用应用程序传递了无效的命令。\r\n", and NativeApiCode = "DXGI_ERROR_DEVICE_HUNG". My create vertex buffer and index buffer code is follow:
My System is Windows11 and CPU is "AMD Ryzen 7 7840H", display card is "AMD Radeon 780M Graphics". I try use Sharp.Dx run same logic code, it is ok, but use Vortice, it get error. Can you help me solve this problem?
The text was updated successfully, but these errors were encountered:
I run my Application in "AMD Radeon 780M " display card, when I mouse click some region, I will create vertex Buffer and index buffer, But I get a runtime error: "Message = "HRESULT: [0x887A0005], Module: [Vortice.DXGI], ApiCode: [DXGI_ERROR_DEVICE_REMOVED/DeviceRemoved], Message: [GPU 设备实例已经暂停。使用 GetDeviceRemovedReason 以确定相应的措施。\r\n]" with ResultCode "887A0005". But some time is ok, some time is get this error! I try to get removed reason by
device.DeviceRemovedReason
, it tell me: "Description = "GPU 不响应更多的命令,最为可能的原因是调用应用程序传递了无效的命令。\r\n", and NativeApiCode = "DXGI_ERROR_DEVICE_HUNG". My create vertex buffer and index buffer code is follow:My System is Windows11 and CPU is "AMD Ryzen 7 7840H", display card is "AMD Radeon 780M Graphics". I try use Sharp.Dx run same logic code, it is ok, but use Vortice, it get error. Can you help me solve this problem?
The text was updated successfully, but these errors were encountered: