What worked for me was removing the Wow.dxvk-cache file which can be found in the same directory as Wow.exe. The reason I tried this were the memory access errors found in the Errors directory. I figured the cache may be stale and dxvk isn’t able to clear it before crashing.
Heading from my last 2019-11-12 00.28.12 Crash - 258.txt:
==============================================================================
World of Warcraft: Retail Build (build 32305)
Exe: C:\Program Files (x86)\World of Warcraft\_retail_\Wow.exe
Command: "C:/Program Files (x86)/World of Warcraft/_retail_/WoW.exe" -launcherlogin -uid wow
Time: Nov 12, 2019 12:28:12.045 AM
User: XXX
Computer: XXX
------------------------------------------------------------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft\_retail_\Wow.exe
ProcessID: 258
Exception: ACCESS_VIOLATION
The instruction at "0x000000006a3bcf70" referenced memory at "0x00007fb6514dab00".
The memory could not be "read".
<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<000000006a414dd6>("d3d11.dll") <- DBG-ADDR<00000001405d58f0>("Wow.exe") <- DBG-ADDR<00000001405c85ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x000000006a3bcf70" referenced memory at "0x00007fb6514dab00".
The memory could not be "read".
<:Exception.Summary>