I have been dealing with this since last week. it appears to be some kind of incompatibility with Nvidias new drivers that they have updated twice withing the last week and the DUSTY OLD OUT OF DATE DirectX libriaries Blizzard is using in the games directory.
Took me hours to track this down, because the generic answer I constantly hear is “Well you have a 14900KS, it migth be degrading” I assure you its not. It’s just wow.
Anyways. Digging through logs and 35 crash reports worth of data, it appears to be Blizzard is using outdated d3d12.dll, and d3d12core.dll. I didn’t bother with the other two since they are for windows 7 compatibility.
What sent me down the rabbit-hole is every error log pointed to the same set of dynamicaly loadable lbraries. d3d12.dll, and d3d12core.dll
Blockquote
Exception.Summary:
ACCESS_VIOLATION - The instruction at “0x00007ffaa1241582” referenced memory at “0x0000000000f21a78”.
The memory could not be “read”.
(DBG-OPTIONS DBG-ADDR<00007ffaadfd0c03>(“D3D12Core.dll”) ← DBG-ADDR<00007ff7184874a3>(“Wow.exe”) ← DBG-ADDR<00007ff71847ef37>(“Wow.exe”) DBG-OPTIONS<>)
<:Exception.Summary>
Did a whole lot of digging because i ran into this issue before using specifc games where the problem was outdated or corrupted. DirecrX libraries.
Double checked, saw Blizzard had very ancient DirectX libraries of the wrong size, replaced with proper recent versions… POOF problem solved, so far.
Kept happening after intense combat in M+ keys. Only an hour in i’ll update after a few more runs to see if the problem comes back up.
Blockquote
Update note: This is after 35 solid ingame M+ crashes. All starting on SPECIFICALLY 03/07/2025. What ever changed that day or night is the problem. I have had ZERo crashes like this previous.