AnsweredAssumed Answered

Bug report: experiencing an Access Violation error with a particular compute shader, but only on amd adapter, not WARP.

Question asked by gfmatt on Aug 28, 2019
Latest reply on Aug 28, 2019 by elstaci

I've found that with some shaders, the ID3D11Device::CreateComputeShader function causes an access violation when the ID3D11Device in question is created with an AMD adapter.  I've been able to repro this consistently and have put together a project to demonstrate the problem, linked here:


Of note:

-the AV doesn't occur on the Microsoft Basic Render Driver.

-the AV can be reproduced with other shaders that use a similar nested if-pattern like the one found in the above project.

-the AV doesn't occur when using the DX12 api equivalent (WARP, AMD adapter, or otherwise).


The resolution of this error is of particular interest to me, as similar shaders of mine using this nested-if pattern have outperformed other patterns on DX12.


I'd greatly appreciate it if you could forward this to all relevant parties.  Thank you!