Exception: ACCESS_VIOLATION - The instruction at referenced memory could not be read

Support Technical Support
1

I am getting an “ACCESS_VIOLATION” error every time I load the warband login screen assets. If I mash enter I can bypass it before the assets load and not crash, but if I try to let the assets on the login screen load it crashes.

This has only been happening recently, I’ve never had any issues up until some recent patch, I’m not sure when the date was for it.

I have done the following:

  1. Update all drivers on my system, graphics, chipset, bios, etc - anything I could find to update I did.
  2. Re-installed WoW completely, to include bnet. I’m also running no addons at all, stock configuration (no modifications to any compatibility settings, etc)
  3. My temps are not an issue at all, everything is completely fine, CPU is downclocked to 52x (I’ve had this for months, even prior to this issue)

I’m running a 14900k w/ a 3080 TI graphics card, I’ve already gone through all the rigmarole of underclocking this CPU, disabling all boost profiles, etc. Everything runs completely stable on my system except WoW right now, and this error was only introduced recently.

===================================

Update: I was able to completely stop the error from happening (I tested logging in multiple times now, no crashes, whereas prior I would crash about 80% of the time)

This has been successful for me, so far, to eliminate the issue:

  1. Drag all characters out of your warband
  2. Log into a character, then log back out - if you don’t do this and just close the game the warband will be populated again when you come back in after closing the game.
  3. Close WoW
  4. Log back in and see if the error happens for you again

It hasn’t happened for me yet, and nothing is in my warband right now. Seems to be something with rendering the 4 characters in the same location (maybe some odd transmog related issues or something? Maybe loading transmogs one class can’t use? I don’t know)

Let me know if this works for anyone else!

===================================

Further edit, this might just be tied to paladin flail transmog version of Truthguard. Still troubleshooting, but I’m able to consistently reproduce it with that mog on.

===================================

Final edit, issue is caused by having the Legion Mage Tower Artifact Flail transmogged, and the character is in your warband, and your initial load of character is on the warband login.

Change your paladin transmog, issue goes away.

1 Like
2

Having this same exact issue, I know a lot of other people are too. Hoping we can get replies ASAP as launch is imminent.

3

Mash your enter button, brother. That’s the best we can hope for, for now.

4

I am thankful I came across your post, I didn’t know about mashing enter and it did get me into the game. Hopefully that can continue to work until they get this fixed. Insanely frustrating to troubleshoot.

5

Good thing many of us got that early access with our purchases, eh? A masterful troll.

To be clear, i’ve bought the epic/collectors editions of nearly every wow expansion since vanilla… so i was just happy to get early access this time. But the feeling of having that rug ripped out from under me is exquisite. And the added bonus is my wife isn’t having this issue… so she’s going to be chomping at the bit to go on friday and if they don’t get this squared away by then… man… not a good day.

6

Yes, it’s definitely a real kick in the pants having paid to get in early and having this issue. Use the mashing enter method the OP posted before the warband assets fully load and you should be able to bypass this issue for now. Once you’re in you can log back out and it doesn’t crash and I’m able to swap between characters. However, if the game ever crashes while playing we’re gonna have to go back to the mashing enter method. Very disappointing and it makes me regret having paid for EA.

7

Have you tried teleporting or doing anything else that gets you a loading screen while playing? For me, if the exception happens, it happens while the game is loading. So i’m afraid if i have to take a portal somewhere or load into an instance that my game is gonna crash.

8

I am not crashing while on loading screens so far, I’m clicking around places and changing continents and not having any issues right now. I’m also not running any addons at all right now, so take what I say with a grain of salt there. Normally I would have addons going, but I’m waiting for the new release of Atrocity UI before I do any addons today.

===================================

Update: I was able to completely stop the error from happening (I tested logging in multiple times now, no crashes, whereas prior I would crash about 80% of the time)

This has been successful for me, so far, to eliminate the issue:

1. Drag all characters out of your warband
2. Log into a character, then log back out - if you don’t do this and just close the game the warband will be populated again when you come back in after closing the game.
3. Close WoW
4. Log back in and see if the error happens for you again

It hasn’t happened for me yet, and nothing is in my warband right now. Seems to be something with rendering the 4 characters in the same location (maybe some odd transmog related issues or something? Maybe loading transmogs one class can’t use? I don’t know)

Let me know if this works for anyone else!

1 Like
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.