I’ve been crashing to the access violation error as well.
On all characters, with or without addons disabled, even on Remix characters.
1 Like
Same issue, played fine yesterday. Some small update downloaded today and constantly crashing. Sometimes I don’t even make it past the loading screen.
1 Like
I got this crash error today. I stopped having issues after I switched to Skyriding? That might not be the case for everyone, but it helped me. thunk
Probably too soon to post, but I logged on a char that didn’t have skyriding enabled. That char is not crashing.
My druid who crashes seconds after logging in DOES have skyriding active and is midflight. If he ever stayed on long enough to change the option, I might be able to confirm something.
For those who are crashing to addons or whatever, it may be how they interact with data tied to the coding with skyriding.
OR
not at all and this is all crappy coincidence.
Update: So it worked until I got to Theramore* then it freaked out, froze, and crashed again. However my other char who was in Searing Gorge has been totally fine even with all the peeps around.
1 Like
I found this advice on reddit. I’ve so far not experienced another crash since I implemented their solution.
For folks on this thread, a potential stopgap includes the following:
- Go to Game Menu, then Options
- Under System click on Graphics
- Scroll to the bottom and uncheck Optional GPU Features and Advanced Work Submit
17 Likes
I just found this and it is so far working for me. I was going to post but wanted to make sure first. Good share!
that fix seems to work for me as well!
This worked for me! thank you for sharing.
1 Like
Works, thanks!
1 Like
This fixed it for me! Thanks
1 Like
Same here. Completely unplayable.
Same here, and Blizzard Support was no help. Gave me a generic copy paste response and told me to come here. This is what I have been getting. I notice it crash when I open my character menu or a quest with a character model in the dialog.
Exception: ACCESS_VIOLATION - The instruction at “0x00007ff62813dfa6” referenced memory at “0x0000000000000228”.
The memory could not be “read”.
ProcessID: 18296
ThreadID: 13168
My specs are:
Intel i9 13900k
Nvidia 4070ti
16GB of Gskill Ram DDR5 5600
WD NVME SSD
MSI z 970-a Motherboard
It works for me, awesome find! (AMD chip btw)
1 Like
This worked. Hopefully it gets fixed in a patch as the graphics quality is rather noticeable, but I can deal with that over crashing. Thank you.
same issue, tried all the fixes, disabling addons, disabling advance work submit and that worked for about 30 minutes and now constant crashing again.
Also wanted to link this post, seems like this may work as well as disabling. Haven’t crashed on this either.
2 Likes
Thanks for bringing this to our attention! I went ahead and did as they suggested while re-enabling Advanced Work Submit and Optional GPU Features. I’ll update y’all on my performance as I continue playing.
Also getting consistent crashing, though for me it seems to be triggered primarily by opening the transmog vendor. Oddly, it happens almost immediately on one of my priests, but other characters it takes a little time before it crashes. As long as I don’t open the transmog window, I can play without any crashing problems (though my first two crashes were earlier today when doing the prepatch event, but nothing like that since.
I doubt system specs have an impact, given the wide array of specs in this thread, but just for completeness;
Ryzen 7 7800X3D
64GB DDR6000 ram
Installed on M.2 SSD
RTX 4080 GPU
Graphics settings on max
5120x1440 resolution
There is a fix, see above the linked post from the devs. Crashing non-stop for me, since the fix i havnt crashed in hours.
It’s less of a “fix” and more of a band-aid. I’m really hoping Blizzard will look into whatever part of yesterday’s patch started causing this issue for so many people so that we can return to using the graphical settings our PCs are actually capable of to enjoy the game.