Access_Violation Error possible fix

Support Bug Report
1

I had the Access_Violation memory could not be read error. I found that utilizing the code “/console cvar_default” fixed it. I spent 50 hours digging and researching, to no avail. I couldn’t find a fix, I couldn’t get it to stop, I finally gave up and went to bed. I got up this morning and one of my guildmates who had been helping me research it found this in a REALLY old battle.net post. Here is what it does, “The /console cvar_default command in World of Warcraft resets all Console Variables (CVars)—which control graphics, sound, interface, and camera settings—back to their default, “factory” state. It is typically used as a troubleshooting step to fix UI bugs, camera issues, or misconfigured settings”.

You can make the decision whether you want to use it or not, BUT it completely fixed the problems I was having and the error has not returned. So, if you are experiencing the Access_Violation error. This may be the best approach to stopping it.

2

This did not work for me. It made things much worse. It reenabled DX12 and increased my graphics settings, so now the game crashes with an access violation after a couple minutes.
On top of that, all nameplates are so small I can’t read them and there doesn’t seem to be any options in the game to increase the text size. So the game has become completely unplayable for me because of this.

3

anyone else having this issue or find a resolution? This started happening to me yesterday and I have put in at least 20 hours trying to fix it so far. No luck.

1 Like