Only happens to me in the new raid, nowhere else, which makes me think has do with weakauras or addons using too much memory and something crashes and re-renders everything. But weird only happens DX12.
It still happened to me in a new windows install with a fresh wow and Nvidia drivers install, no addons, in both Stormwind and Donogal with Directx11 activated.
Problem went away last week went I decided to start over to check each step, did a WoW repair and Installed latest Nvidia drivers with the clean install option checked and reset the WoW settings through battlenet.
I down know if it was either corrupt/faulty WoW files or that my Nvidia drivers were installed wrong.
I work in cybersecurity for a living; Iām fine with making the exceptions, the layers of my home onion are numerous.
I have a 4-firewall deep network edge:
- inline IPS
- outside firewall
- DMZ switch with DMZ-based Server 2025 domain for DoHCrypt DNS on VMware ESXi 8.0U3 in two hypervisor pairs
- inside IPS
- inside firewall
Inside LANās connect into a 6 host ESXi datacenter in 2 clusters, 150 TBās of SSD storage and vSAN.
Apart from that I use a Server 2025 domain with an ESAE, a couple pairs of tier 4 PKI, FIDO2, 2 SIEMās, and I make full use of the Defender XDR stack via a M365 E5 license. 
Networking for me is 10G fiber from ISP with a 500 meg backup, 25G backbone core switch, and 10G distro/access layer networking and WiFi 6.
Using VMware vExpert licensing and Visual Studio Pro annual server licensing.
Plus āVerify Heap Integrityā is disabled for just the applications and not blanket for the device, so the risk exposure has compensating controls.
1 Like
Again, none of that likely matters. This is a WoW-Windows-Nvidia/AMD issue. The only thing out of the that list that would have any effect on things would be the Nvidia driver version and making sure the game and launcher have appropriate access to read/write(like when people get stuck with the infinite updater loop because folder permissions are borked).
No, it doesnāt. The app is what you want heap integrity for. Granted, I wouldnāt be too worried about WoW trying to do some 0-day exploit on your PC, but in other apps, the app could exploit the heap through a bunch of various methods like buffer overflows and then screw with things elsewhere, even if securities are enabled for the rest of the OS. So I would not get in the habit of selectively disabling security measures for apps on a placebo whim.
In 95% of cases, just simply restarting the game client will have an identical effect on perceived āstability,ā compared to tinkering around with things and then restarting the game. Iām not going to ramble about shader compilation and shader caches, but unless youāre completely clearing ALL of the shader caches between relaunches of the client, your testing is null and void.
1 Like
And the problem still persistsā¦ Unbelievable that they havenāt fixed this yet.
3 Likes
Yeah all the changes mentioned above made it look promising for a few hours of gameplay but the sudden microfreezing and re-rendering happened again. Iām just going to go DirectX11 for now.
2 Likes
Its happened before in the past - Nov 7th. Patch 10.2: Guardians of the Dream- back in dragonflight. Same dx12 issue. And the fixes were just to revert to dx 11 til Blizz found a fix. Maybe they can look way back then see what went wrong there.
1 Like
Please look at my other posts; but found an article for the most recent Microsoft patches, they speak to the things Iāve used to get around the problem; but I also have a brand-new NVMe SSD I have the game installed on externally and wasnāt plugged in when I did this monthās update.
The issues might be correlated to corrupt disk blocks and/or the changes to Defender Iāve been preaching.
Hope this provides some direction for everyone; it may not be Blizzard, but Microsoft.
Problem is, the game performance is so much worse, especially for raid and pvp and even just regular questing in Kāaresh. Lots of microstuttering and Iām playing on a rather low graphics setting. Not the issue at all on DX12.
1 Like
Yeah I know. Itās a shame that Direct12 is not stable.
DirectX11 also doesnāt fix the problem. Yesterday I had horrible freezes while using DirectX11.
on other tech forums of other games, its linked to the last two months of Windows updates. Also seems removing said updates doesnāt fix it. Short of a fresh install and reformat of your installation drive and not doing windows updates; seems to be about the only way to go. Even then the latest Nvidia drivers may require windows updates to a certain recent months, so it really a ying/yang scenario.
I use Veeam at home and restored my O/S to June patch levels from my 6/20/25 system backup and installed the last Nvidia drivers, and right now the game is stable. All my profile documents are stored on my Server 2025 file server, so wasnāt too worried about losing files or bookmarks.
Yeah, youāre right. I thought it was fixed but I had a few more instances of the problem today when in DX11 mode. Oh well.
1 Like
Honestly, I donāt know what else to do. Iāve already reported it under āBug Report.ā I donāt think thereās anything more I can do. Iāve tried everything.
3 Likes
I had this issue once and after disabling NVidia reflex, only thing i did despiste updating addons and wa, etcā¦ When It happened i took a look in gx log on wow folder and It indicated to disable this function as a workaround to possible driver instability. I guess It worked. Take a look yourself If your gx log indicates any change to be made or If this fix works for you. Has been more than a week of intense gameplay.
1 Like
I disabled NVidia Reflex and played a few hours in DX12 without any issues. Iāll keep my fingers crossed. Thanks for the suggestion
Still waiting on some sort of response or acknowledgement that this issue is being looked into and a solution is coming. Itās been happening since the Visions went live. No answers here or on the EU forums. Swapping to DX11 is not a real solution. Itās happening on two systems with NVIDA and Radeon Graphics Cards. One is Windows 10 and the other is Windows 11. Itās not an issue with just one type of system/hardware. Something is broken in the code some place within the client.
6 Likes
Itās incredibly unlikely youāll see that in this forum, since all of the forum Tech Support agents (employees) were reassigned or moved on from Blizz. Itās only volunteers in here.
Since it has been brought to our attention that we will gain no traction here with the QA/Dev team, I have created a topic over on the Bug Forms, summarizing everyoneās posts here and the problems weāre facing, as well as the things weāve tried.
Please lend your voice to this post so that we can continue to voice our issues here, and hope to get a Blue to recognize the issues weāre facing.
Thanks!
7 Likes
A few more hours of play with zero issues after disabling NVidia Reflex.