Before the latest update I was getting an access violation that cause my PC to shut itself off every 2-3 days. It was annoying but I lived with it. Today I have had SEVENTEEN access violations since the servers came back up. You people need to properly test this game before releasing and update. This is just plain incompetence.
9 Likes
Same here, I recently re-installed Windows + WoW on a new SSD, everything was running fine until the 12.05 patch, now I’m getting ACCESS_VIOLATION errors every 5 minutes. Tried updating my NVidia drivers to the 595.97 release with no luck 
3 Likes
I got access violation error once after heavy transmog viewing for 1 hour straight.
1 Like
Ive had several of these this morning
1 Like
Had one of these last night while seeing what a quest reward item looked like and logged off. None today, knock on wood, but I haven’t really gotten started with my routine.
Its insane how much they managed to break with this patch.
1 Like
Same as OP. Every few days, now 13 today. Getting pretty frustrated.
1 Like
Access violations may be due to corrupted files and/or improper configuration (usually due to setting up some non-standard config in an earlier version of the game and keeping updating the game on the same folder for a long time).
I’d try the diagnostic tool (“Verify and repair” in Battle.net app, on the “cog” button to the right of the “Play” button).
I’d also delete the COnfig.wtf file on the World of Warcraft_retail_\WTF folder, or maybe even delete the whole WTF folder. After that, start the game and adjust configurations as needed in the standard menu.
If those don’t help, it may be a hardware problem, maybe due to outdated drivers or faulty memory.
1 Like
Two different machines, one of which was a fresh install of the game.
Both crashing at the Character Select load.
Get on a starter account I haven’t used since Panda Remix, characters load just fine.
3 Likes
In my 47 years experience as a programmer, every access violation that happened in software I was working on was due to one of our programmers forgetting to initialize a pointer. It’s never been another piece of software or hardware. In this case, windows always says it is wow.exe causing the violation, so unless something is tricking Windows into thinking it is wow.exe I believe it is wow.exe causing the problems.
4 Likes
I crashed with the same error twice today tied to Dialogue UI’s (an addon) text-to-speech toggle while on quest screens. I reported it but I suspect that this is something not playing nice with Blizzard’s recent “lets make everything a secret value” obsession. Could be wrong, though.
3 Likes
I’m also having this problem, some players think it might be due to the Legion transmog on the shaman when they set it to hide when sheathing. I don’t know if this applies to you.
3 Likes
same is happening to me. Tried cache and wtf folder, even removing add ons… still crashing at game start , when I try to login. Before the error, I ve got add on error in game. closed the game an then this started.
1 Like
Try to log in to the game and get to the warband screen to be met with a access violation error every time since the maintenance yesterday. I have a shaman who is transmogged with double lightning axes from Legion artifact appearance (Option Hidden when sheathed) as others in a different post all had the same issues and had shamans transmogged similarly.
My 2nd account that I do not have a shaman on is completely playable with no issues running on the exact same computer.
Fatal Error - Wow.exe
ACCESS_VIOLATION - The instruction at “0x00007ff65c4a5468 referenced memory at “0x00000000000000a0”. The memory could not be “read”.
2 Likes
since today Im getting this error when I try to log in on my rogue:
B3C20FC1-6B2C-48ED-8E81-44DEFB2BA7BF
0x00007ff7a35c5468 at 0x00000000000000a0 memory could not be read
tried everything, but reinstall the entire game. deleted cache, wtf folders, reseted configs…
nothing seens to work.
1 Like
Same.
Cant get to the character loading screen without this happening.
Can you guys like….fix the game maybe?
very same error message here
Echoing sentiment here, and from the technical forum: After transmogging shaman with double legion artifacts, hidden when sheathed, I have had constant, consistent access violations and crashes on the character select screen on 2 separate devices, one PC and one Macbook. I am genuinely locked out of the game.
1 Like
Something that might solve this is the “Stuck Character Service.” I selected the problematic shaman, and his transmog resets, and the game restarts. Just don’t do what I did, which was to change my shaman’s transmog, close the game, and come back to see if it works without first changing characters, because now I can’t even log in. I’ll have to wait another 4 hours to use the service again before I can play.
edit: in doubt, place your shaman as far down as possible so that he doesn’t appear on the screen when loading the warband for the first time.
This worked for me to at least get back in game and try to change my mog.
Hoping it sticks…..
Throw your shaman down there and most importantly, don’t leave the game before logging out another character that isn’t the shaman last. Because if the last one is called, the game will remember and load it first on the screen, then the problem returns.
1 Like