WoW: "Memory could not be written" error

Same problem for me on my pally loading into Krokuun.

1 Like

Ok. My character is also on Krokuun. It does appear to be legion based.

1 Like

Same issue here, Launched after the servers came back up, decided to run the Nighthold and then the crash keeps happening anytime I load into that character. My other characters are fine, luckily.

1 Like

Got two characters crashing in Krokuun, decided to give that up, and now have a third character crashing in Nighthold…

Brunhammer-Wyrmrest Accord
Coya-Wyrmrest Accord
Madcap-Wyrmrest Accord

Attempted use the unstuck feature, but continue to crash when attempting to login to these characters. All addons disabled.

AMD processor, not Intel.

2 Likes

same here. i can’t log onto that character either without getting the error.

1 Like

Had one char go there(Night Elf Priest Lunanna) and the game crashed. Its definitely legit, very curious to what is going on.

1 Like

Just posting on the proper character on the off chance some one comes here to fix. This is the character that is stuck on emerald dream. Please save me!

1 Like

Pls Blizzard the Legion stole my wife :[

1 Like

Same issue here. Trying to access Legion raid content via the Looking for Raid NPC. Got the error and crash on two separate characters. After the first crash, I logged still in a LFR group, still in Dalaran. Tried going to the raid entrance itself rather than being ported in. Upon entering the raid instance portal I crashed again with the same error, and now that character is stuck there. If I try to log into that character, the game crashes with the same error.

As a note, all my addons were disabled at the time these errors / crashes happened.

Exception: ACCESS_VIOLATION - The instruction at "0x00007ff72ab78a9d" referenced memory at "0x0000000000000088". The memory could not be "written". ProcessID: 2044 ThreadID: 2040

<Exception.IssueType> Exception <ExceptionType> Crash <Exception.Summary:> ACCESS_VIOLATION - The instruction at "0x00007ff72ab78a9d" referenced memory at "0x0000000000000088". The memory could not be "written". (DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff72ab78a9d>("Wow.exe") <- DBG-ADDR<00007ff72ab79486>("Wow.exe") <- DBG-ADDR<00007ff72ab7cd6c>("Wow.exe") DBG-OPTIONS<>) <:Exception.Summary> <Exception.Assertion:>

1 Like

Stuck in this character as well

1 Like

I posted this in another thread that was started about the same issue, but ya, me too. Ported to Krokuun from Legion Dalaran. Game crashed, got message below, and get same message every time I try to log in

ACCESS_VIOLATION
ACCESS_VIOLATION - The instruction at 0x00007ff3d9a8a9d" referenced memory at “0x0000000000000008”.
The memory could not be “written”

1 Like

ive got 8 toons parked over argus and they all give me this crash. 1 toon in legion dalaran does the same thing. no issues with any other toons until i hearth to legion dalaran. bad day to be an egg farmer

1 Like

Same Problem here…Stucked at Krokuun…

2 Likes

Same problem here. Logged on and was able to enter Halls of Valor (for a quest) and complete it with no problems. Then went on to do some quests in the Nighthold Raid and crashed upon entry. Then whenever I launched the game it would give me the same access violation crash.
I have a second character that I logged off in the Karazhan Dungeon, which is affected by the same issue.

I was able to gain access back to the first character after using the Stuck Character Service, but the second one got sent to Krokuun and is still broken.

Things I tried:
Updated nVidia app and drivers
Disabled all addons
Set graphics to potato
restarted PC
Disabled any special graphics features (the bottom options)

1 Like

Thinking the same thing!! This is my main that is stuck and I am terrified that if and when they will fix it!

1 Like

Krokuun is where I also got sent by using the Stuck Character Service. I still am not able to log onto her.

1 Like

same with me. i have 5 characters stuck in argus now this really sucks. all my mains are unusable.

1 Like

Guys, the solution is simple: Go to this link https://us.battle.net/support/en/article/10581 and use the service to move yourself to the nearest location. This will get you out of Argus and other places.

I did that but all of argus is affected so will not work there

1 Like

I used this, one of my characters was sent to Krokuun and is still affected. So it doesn’t fix it for every toon. Also, it’s very clearly an issue with the latest patch.

1 Like