Access Violation Crashes Since Patch 11.1.7 — No Acknowledgement from blizz?

Susana-grim-batol · July 17, 2025, 2:13pm

Hi,

I’ve been experiencing constant Access Violation crashes ever since the recent 11.1.7 update. I have never had any WoW error like this before, and I do not encounter crashes in any other game or application — only in WoW, and only since this patch.

I’ve tried every troubleshooting step I could find here on the forums, on Reddit, and through advice from Game Masters:

Updated Windows fully
Latest GPU drivers
Updated BIOS
Checked system temperatures (everything normal)
Disabled Advanced Work Submission, tried DX11, DX12, all settings combinations possible
Added exceptions to security software
etc…

Nothing works. For context, I’m running a Ryzen 9800X3D, so this has nothing to do with Intel CPUs (which some threads mention).

There are dozens of new posts and users reporting exactly the same issue since this patch — yet so far, Blizzard has not even acknowledged this as a known problem.

It’s really disappointing that we, the players, have to guess and troubleshoot blindly for something that clearly started with the last update.

I believe Blizzard should at least post an official statement confirming they are aware of this and investigating it.

Here are some posts of the users experiencing problems including this very same issue:

EU FORUMS:

US FORUMS:

All the threads I linked are recent and/or have replies from less than 20 days ago (most of them have replies from hours ago) , so this is clearly not an isolated or outdated issue.

If you’re having the same issue, please reply here to keep this thread visible — maybe then we’ll finally get some recognition and a fix.

Thanks for reading and good luck out there.

System Specs:

Win11
CPU - Ryzen 7 9800X3D
Mem - 64GB DDR5 @ 6000Mhz (2x32 dual-channel)
GPU - AMD RX 7900XTX 24GB
Board - Asus Rog Strix B650A-Gaming WiFi
PSU - Corsair RM1000X

Felranys · July 17, 2025, 3:44pm

Hey there Susana

I understand your point for this topic and I honestly appreciate your intentions here, I am afraid though I have to make a quick intervention to clarify a couple of points.

First and foremost

I have to point out that unfortunately having such a topic to “catch all” the technical problems people are reporting is ultimately making things more difficult not only for us, but for all players that decide to post their experience.

This is due to the fact that technical problems have often vastly different causes even in situations where the symptoms are similar or even identical.

For example, an “ACCESS_VIOLATION” error can have hundreds of different causes, ranging from a driver issue (video, audio, chipset etc… etc…) up to something extremely more complex such hardware failure/problems such as the infamous Intel CPUs bug. Of course among all the possible causes there are also client bugs, weird software interactions and a ton of other possibilities.

A second point

I want to clarify is that our engineers are constantly reviewing crash reports, and working on anything that is actually caused by a client bug and not something external.

In other words, if a specific crash is actually caused by a client bug our teams are usually aware within a very short time. That said, not all bugs are made equal and depending on the situation it can tale a bit of time to have a fix deployed especially if a fix requires an actual client patch rather than an hotfix.

I want to take this second point as an opportunity to encourage everyone to make sure crash reports are submitted whenever possible via the crash report window that usually opens up after a client crash.

Third and last point

In reality the vast majority of crashes are not due to client bugs, but due to software/hardware problems or conflicts. More often than not such problems can be self-resolved by players via one of the technical troubleshooting guides we offer on our support site - such as this one:

To also cover a couple of your points:

While the reports may seems the same - mostly due to having the same error message - their root causes are not, as I briefly explained in my first point.

We can not acknowledge “ACCESS_VIOLATION” errors as a known problem, as there are multiple causes for them - and almost entirely they are not due to a client bug or problem.

I honestly appreciate your list of topics, but again putting them together under the same umbrella is not useful in this case, as while some share an error message they are often due to different problems

We would rather not have a single topic collecting a ton of different reports, as it would make things more difficult for both us and other players.
Please keep the discussions in pre-existing topics (or create new ones if you feel none of the existing topics is covering your specific problem), rest assured that they are all read even if there is no blue response.

I am going to close this topic now Susana, please know however that it is not due to something wrong you did but rather to prevent a situation that is likely to create only more confusion in the long run, and an extra layer of difficulty for us to check and collect information.

A short conclusion

Rest assured that reports of crashes or technical problems in general are not ignored, it is however important to remember that more often than not such problems are not something that can be resolved via a client patch/hotfix and should be troubleshoot and fixed locally.

Our support site has plenty of guides that can help with the process, and this community as a whole is also often able to offer a helping hand to troubleshoot and fix more complex situations

Please also rest assured that where a technical issue is due to a client bug/problem we are always doing our best to prep and release a fix timely, even though it may not be always possible to release a statement beforehand.