I have found quite some other things being affected by the issue while doing the google research. Some goes back as far as 2014!! Amazing this issue still around.
Application reports what Windows’ DirectX reports (that DXGI_… comes from DirectX) and as it does not know how to handle such error, it aborts… again, trying to send commands after this error is most of the times BSOD or Windows freeze, due to invalid handles.
For DirectX behave like that you have few options:
- UE or any other DX application not sending proper command sequence
- UE or any other DX sending command with wrong data size (so DirectX will wait for the remaining of data if still not reaching size)
- Graphics’ Card Driver not behaving properly (doesn’t they need to pass a battery of tests by Microsoft? If, so Microsoft is to blame on the tests)
- Graphics’ Card BIOS not behaving properly with Graphics’ Card Driver (Is there any BIOS update?)
- issues on Graphics’ Card Driver installation
- issues on DirectX installation (in case older Windows versions)
Sorry to the OP to include in the post such amount of technical stuff, I promise I will stop before having thread moderated.