I have attempted from another computer and it gives the same error (a computer with 2 other accounts and no issues…literally just my one toon)
+1. lol yikes xd meme character limit cringe.
Yes, tried from my fiances pc, with a fresh bnet install and fresh bcc install, 0 addons. still same issue. its not local, its on blizz’s end somehow.
I am experiencing the same issue. I have 2 sub accounts with multiple lvl 70s, only the first character of the 1st subaccount is having this issue (my main).
I have:
- Disabled all addons
- Updated the video drivers
- Used the “unstuck service” from Blizzard website (moved to Durotar), thinking it was a zone issue
- Deleted cache folders
- Reinstalled completely Wow
I am still having the issue.
I also can’t login into my level 70 shamans and warriors, but I can log into my sub 70 characters.
I am also experiencing the same issue on my rogue and have tried many of the troubleshooting steps outlined here and elsewhere. No luck!
Same thing…
Level 70 warlock and priest both have the issue
My other level 70’s and lower level toons are fine.
Hey everyone,
I looked up some of the crashes going on with the players in this thread and they’re all similar. I also see a few tickets came in recently for this exact symptom. Looks like something is going on and I’m going to poke the developers to make sure this is on their radar to fix up. Thanks for the reports everyone. Will post an update should I hear something further.
Please help
Thanks for looking in to it!
+1 I’m having the same issue on my paladin, It’s raid night and I want to raid
Having the exact same issue as well on my rogue.
Thank you!
Since the servers went live with the ZA patch I am getting ERROR 132 and the game crashes.
This is only happening when logging in with all existing characters of any level across multiple realms.
Creating a new character allows me to play normally and with all my addons active with said new character.
Update: I completely uninstalled all versions of wow and then renamed and moved my wow folder to the desktop. I followed that up with uninstalling and reinstalling the Battle.net launcher which when completed found no versions of wow on my PC. Next I reinstalled TBCC and attempted to log in to find the same ERROR 132 that everyone else here is getting.
I am having the same error as well. Only one of my toons on my account is affected (my main of course). I submitted a ticket, so hopefully others have too
i just posted about this 6 or so minutes ago. it is happening to only ONE of my toons as well… and its my crafter that has all of my consumables tonight xD
Ugh oh nooo. At least mine isn’t needed until tomorrow for raid, we were thinking it was maybe a server issue, but maybe it’s more widespread. Worse case I guess my guild gets a super undergeared hunter or boomie instead of a healer.
thank god other people are having this issue… I’m having it aswell. I can login any character aside from my 2 main ones which are both on different accounts…
Sometimes its giving me the
ProcessID: 9156
ThreatID: 10820
Exception: ACCESS_VIOLATION
The instructions at “0x00007ff71378b516” referenced memory at “0x0000010065e756f.”
The memory could not be “read.”
and sometimes it’s giving me
ERROR#123 (0x8510007B) This memory block has been corrupted by an out-of-bounds memory write.
ProcessID: 11196
ThreadID: 2712
“Memory Corrupted – unknown 0”
BLIZZARD CS HELP
Same issue on my rogue
Same here it’s ONLY on the characters I logged in Shattrath and ONLY my account because I was able to log onto my other account and was fine.