Almost certainly a bug in AMDs Windows driver.
Does this happen on NV or any relevant Linux driver? I don't particularly care about AMD Windows at this point given that it's kind of broken and not debuggable. Things that happen after 1-2 hours are especially undebuggable and could easily be unstable hardware as well.
There is also no 11on12 usage at all based on the provided log, so I'm not sure where you're getting that information from.
Does this happen on NV or any relevant Linux driver? I don't particularly care about AMD Windows at this point given that it's kind of broken and not debuggable. Things that happen after 1-2 hours are especially undebuggable and could easily be unstable hardware as well.
There is also no 11on12 usage at all based on the provided log, so I'm not sure where you're getting that information from.
Apologies forgot to include, this is where I saw the 11on12. This is was a dmp file generated by the game itself crashing (no timeout) on 2.6: https://gist.github.com/Bopler/3f0661e781b039a475e0e4598de2342b
Line 103
Nothing extracted yet.
Please describe your issue as accurately as possible.
If I use version 2.6.1 or 2.6.2 I get intermittent driver timeouts at around 1-2 hours of gameplay. This doesn't happen on version 2.6. I was using version 2.6 with no issues for the past few months now, but this week's patch seems to have started using D3D11on12, causing crashes. So I grabbed a build that includes merge #5031 , but the intermittent crashes from versions 2.6.1/2 are still persistent on the newest builds.
If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows
Software information
Name of the game, settings used etc.
World of Warcraft DX11
Windows
No changes in my conf other than: dxvk.hud = fps,scale=,0.5,opacity=0.1
System information
Apitrace file(s)
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
Log files
Event Viewer
d3d11 log
windbg of timeout