they’re trying its just a small indie company cut em some slack lmao 
We are helping a friend with this problem, and after reading a lot of forums, seems each person has a diferent solution for it, and don’t work for our friend.
The worst thing is Blizzard doesn’t help and just say “Search in forums” or trivial solutions. In EU forums I didn’t read any MVP Tech, in US at least they try to help.
Well, I think the unique option always work is formating Windows, but it’s a Blizzard problem sadly…
yeah it’s frustrating to figure out the issue and what causes it to crash and it seems like the crash can occur at totally random times, while sitting in main cities afk doing nothing. Like Frumi said “Overall looks like everything can make this game crash” for some turning off the async resource creation setting might help and for others it doesnt help.
For me disabling async resource creation helped and had no crashes for weeks. Few days ago started crashing again. There is no single fix which will work in each case. New patch almost always = more crashes. since im lazy this is i think good explanation from ai:
You’re absolutely right — and your experience matches what many players have been going through:
You apply a fix, WoW is stable for days or weeks… then suddenly the exact same crash returns.
Here’s a direct breakdown of why this happens — technically and practically:
1. Race Conditions in DX12 + Driver Stack
The crash is tied to multi-threaded GPU work using DirectX 12 — especially with features like:
- Async Resource Creation
- Advanced Work Submission
- Multithreaded Rendering
These rely on precise memory handling and threading timing. But:
- Timing bugs = nondeterministic
They don’t always crash on day one. A different load, animation, or area can tip the balance. - If something loads too fast/slow or in an unusual order, a bad pointer can get used → access violation crash.
You might not crash for weeks… until the stars align to hit that exact condition again.
2. Memory Corruption from Add-ons, Overlays, or Background Tools
Even if WoW itself is clean, external things can poison memory over time:
- Armoury Crate
- RGB or peripheral SDKs (like Logitech, Corsair, ASUS, Razer)
- Overlays (Discord, NVIDIA, Overwolf, ReShade)
- Add-ons that misuse texture or model APIs (e.g. Plater + certain WeakAuras)
Some memory corruption builds up slowly — only after certain content is loaded or after many hours in-game.
That’s why restarting or disabling one add-on seems to fix it for a while — then it returns later once conditions recreate the fault.
3. Driver-Level Instability with Specific DX12 Calls
NVIDIA’s nvwgf2umx.dll is involved in your crash stack. This means:
- Even old drivers like 572.60 still sometimes expose the bug.
- Later drivers (e.g. 576.40+) introduce new problems of their own.
You can’t really “lock in” a 100% stable stack unless both:
- Blizzard’s DX12 implementation gets patched
- NVIDIA drivers become more tolerant of misused or legacy DX12 calls
Until that happens?
You’re dancing on the edge of GPU race conditions.
4. WoW’s Streaming Engine & Hotfixes Are Live
WoW streams:
- Models, textures, terrain, spells, animations — while you’re playing
- Blizzard also pushes background hotfixes that can change behavior on the fly
So even if nothing changes on your PC:
- A new weekly update
- Or a dungeon you haven’t entered for weeks
- Or a hotfixed model or visual
…can change the outcome of a GPU thread and trigger a crash again.
5. “Silent Failures” Accumulate Before the Crash
- Certain bugs don’t cause an instant crash — they corrupt memory first
- Hours (or days) later, a completely different part of the engine accesses that memory = crash
So a crash at D3D12Core.dll could be caused by:
- Add-on corruption
- An overlay
- Memory pressure
- A bad driver interaction
from hours ago
This is why many “solutions” only buy time.
What You Can Do
You’ve already tried most of the good ones, but to recap:
| Stability Boost | Why It Helps |
|---|---|
 Async Resource Creation |
Disables dangerous multi-threaded asset loading |
| Advanced GPU Features |
Avoids GPU driver miscoordination |
| DX11 Mode |
Fully avoids DX12 threading bugs |
| Minimal Add-ons |
Reduces risk of texture/memory poisoning |
| Disable Overlays & Armoury Crate |
Removes extra hooks into DX APIs |
| Keep WoW windowed/borderless |
Avoids display mode flicker bugs |
| Cap FPS (e.g. 120) |
Prevents spikes that trigger crashes in overload |
The Bottom Line
You’re not doing anything wrong.
You’re navigating a fragile GPU and game engine balance, where:
- Tiny timing shifts
- Live hotfixes
- Driver changes
- Or even which dungeon you run
…can revive the bug.
The only true fix will come when Blizzard releases a client patch that updates their DX12 implementation or officially disables broken GPU features.
Until then, yes — unfortunately — your fixes might work for a while and then need to be re-applied or adjusted. That’s the nature of non-deterministic access violations in a complex, multithreaded game.
Hey Frumi hows it going now with the wow crashes do u still crash with async resource creation off? or did u fix it?
No now im not crashing even with async resource creation on:P I was trying some things but no idea if it helped or they fixed something. using some last year nvidia drivers did some small tweaks in process lasso application but also deleted some addons etc. Not really sure . WAs also trying to lower some cpu boost mutiplier in bios but result was black screen so i rested setting maybe this helped? Really no idea but atm it works. So much smoother with async rc on
1 Like
Roll Back NVIDIA Drivers: For those with NVIDIA GPUs, reverting to an older driver has proven helpful. Players have specifically cited driver v572.60 (late Feb 2025) or any 572.xx series as stableeu.forums.blizzard.com. Using a tool like DDU to fully uninstall the current driver and installing the older version stopped the crashes for some users over many days of testingeu.forums.blizzard.com. This supports the theory that something changed in the 576.xx drivers. (Note: If you try this, you may want to also block Windows Update from pushing a newer driver, until you’re ready to update again.)
Best Process Lasso Settings for WoW.exe
1. Launch WoW, then open Process Lasso
Right-click Wow.exe → CPU Affinity → Always → Select CPUs…
2. Set Affinity to P-Cores Only
Check only:
nginx
CopyEdit
CPU 0 CPU 1
CPU 2 CPU 3
CPU 4 CPU 5
CPU 6 CPU 7
CPU 8 CPU 9
CPU 10 CPU 11
CPU 12 CPU 13
CPU 14 CPU 15
Uncheck:
scss
CopyEdit
CPU 16–31 (the E-cores)
3. Optional: Use Half the P-cores Only
If you want ultra-stable behavior, try:
- Just CPU 0–7 (4 P-cores w/ HT = 8 threads)
This can reduce microstutters and crashes on unstable DX12 paths.
Other Process Lasso Settings (Recap)
| Setting | Value |
|---|---|
| CPU Priority | Always > High |
| Power Profile | Bitsum Highest Performance |
| ProBalance | Enabled (but exclude WoW) |
| Induce Performance Mode | Enabled for WoW.exe |
2 Likes
Also tried this but i got blue screens so loaded some saved settings and dont have it atm:
"This might require you to delve into the BIOS. If you are using an Intel processor, namely a 13th/14th/15th gen processor, you will want to go into the BIOS and find P-Core Ratio. By default, it’s usually set to auto/default, which is 57 (5.7GHz). What you want to do is set it to 53 (5.3GHz).
You get far more stability, some cooler temps, and less issues with certain older games, all for a mere 1-3% FPS loss. It stopped crashes in WoW, ESO, and other older games for me. Turns out older games really just don’t like when your modern Intel CPU can suddenly spike to 5.7 GHz to 6.2 GHz for whatever reason.
It’s probably worth commenting on that if your P-Core Ratio is, by default, is lower than 53 (5.3 GHz), then the issue is not your BIOS settings, but something else."
oh thats great assuming it helped. i havent crashed yet since the latest patch, maybe something got fixed? have no idea. But if i crash i will try what u did with process lasso and older drivers etc. thanks for the info btw 
For me so far so good no new crashes . Will see after patch this is always worst time
thats awesome. lets hope it stays that way 
I just want to chime in — this error is driving me crazy.
After today’s patch, I can’t even play for an hour anymore. I now get Access Violation crashes after about 10 minutes.
I’ve tried turning off Async Compute, switching to DX11, clean uninstalling (DDU) and reinstalling the latest AMD drivers — nothing works. It simply keeps crashing.
1 Like
Maybe some addon?
Try also scan and repair.
Disabling all kinds of overlays. (Discord etc)
For me not sure if this was fix but not using newest drivers im intentionally using quite old ones. But im on nvidia so not sure what is situatioon with amd.
What is your cpu?
Having this now since the latest update. Happened on Wednesday and now tonight. Didnt run a scan and repair on Wednesday but did today after it happened. Annoyingly was in an LFR for LoU that took hours to get in, right at the start. Whats odd is the game was fine prior and I’d run LoU (Dino/Monkey boss and Rik) with no issues. It was before Stix it happened.
No reliability report for it either, which probably means little, but I’ve had no memory issues prior to this or any WoW errors for that matter. Seems tied to this current patch, unless its the latest windows update, but that was last week and didnt have any issues until this week, so I cant see it being that.
/push … since patch sooo many errors. weirdly in dungeons / delve with OBR ^^ not in mythic raid
Is this the " Int divide by zero " crash? I’ve had 5 of those in the past 2 days. I’ve read it might be a problem related to the i7 and I did have these crashes in the past but they stopped and 11.7 brought them right back.
Topic is about errors like this :
Exception: ACCESS_VIOLATION - The instruction at “0x00007ff7244578b7” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.
Ive never seen "divide by zero " one.
These issues seems to be caused by so many things and there are so many factors i don’t even think there is one “solution”.
First game worked super stable for months then it started crashing after patch.
Then i tried some things and it helped more or less. then again game worked stable then again patch and crashes.
Maybe intel cpus are a factor especially combined with fast gpus like 4090 but it happens also on amd. For sure if someone is on 13th 14th generation this is super important to update bios and try some things to make your cpu more stable but sometimes after patch it will probably start crashing again and then it will stop.
Atm i think i have only small things applied i stopped even using process lasso and all affinity, disabling cores etc. and game is super stable still.
I think only notable "fix"i still keep is using older nvidia drivers which are reported to be more stable (v572.60).
Removed also some not up to date addons and overall minimized use of addons. I also do scan and repair every now and then .
Blzzard officially pretends there is no issue but im sure they are aware and trying to fix it.
It is also funny when for some people updates fix problem but then new people start having same problem:P
I got banned for my post about same issue seeminly they dont care didn’t violate any rules and i was silenced
1 Like
This error was common a few months ago but then went away just to suddenly re-appear again today. I havent crashed in wow for any reason in the past 3 months or so but now I got the “access violation, memory could not be read” crash that has been posted here aswell as on the NA forums. Let’s see if they will fix it again soon. Hopefully it wont take as long as it did last time and HOPEFULLY they’ll say something once they do. Blizzard is notoriously bad at posting patch notes that include technical changes to the client and whatnot. Even the patch notes relating to gameplay changes are often lacking. What Creative Assembly is doing with the Total War games should be the industry standard where they release a full documentation on changes made every patch. Like an actual doc that you can deep-dive if you feel like it. Of course they have bullet points similar to other games too.
It’s the happening on this Win10 system running an older CPU (not 13th or 14th gen). But was also happening like 3 months ago on a newer system which some people tried to imply was due to the intel shenanigans*.
It is also happening in BOTH Anniversary Classic and Retail.
Anyway, the memory access violation crash is back. No, it is not this computer. It’s the game.
*Mod edit. If you have to censor yourself, just use another word please. Thanks 
2 Likes