Pandaria Memory could not be read.

[Korpen]

Hi,

I have trouble entering the game now and then. Seems like its in SW since i can start a new character.
I get error message, memory could not be read. It also says access violation!

My brother gets the same message on a diffrent computer also beeing in the Inn in SW.
He started a new character and could enter the game in gnome starting area.

I have tried runing the game on low grafic settings, runing the game as admin and also removing "read only" attribute on folders and files.
It has worked a few days now since last time i/we got this problem.

Thanks for any reply or solutions.

After using unstuck feature on the website i now can play since i had my HS in a diffrent location.
My brother still cant use his character since his HS is in SW inn.
Seems to be a problem with the area.

Would appriciate an solution if possible, thanks in advance.

[skullatbash]

try to log-in with "MoP minimal"

[Korpen]

Thanks for the tip, ill try that next time, just now my brother could enter as well, we removed "read only" from all folders, the .exe file and ran the exe file as an admin. This btw didnt work for me, very strange problem. Thanks again for taking the time to answer.

[munk]

hi, i have been having this same problem, have done all of the possible fixes given to both my laptop and desktop, they both still crash regularly. Today it is so bad, i moved my character with the unstuck feature, didnt work. Cleared cache , over and over. It seems to sort of work in small increments. But keeps crashing regularly. Very upsetting. Am using minimal client on both computers, any ideas?

[Korpen]

It feels like its a bit random Munk, on my desktop which im playing on, unstucked worked. On the laptop my brother is playing on, removing the "read only" or "write protected" attribute on the folder and subfolders and also the *.exe file you are using to start the program with solved the problem. He was starting the game as admin as well. I tried this solution first on my desktop but that didnt solve the problem for me.