This won’t work. I tried to do the UI reset method of renaming my Interface, WTF and Cache folders but the game’s still crashing on me.
1 Like
Cant get past character screen so it doesnt even matter ):
All addons are disabled?
Yup. They’re doing another 1 hour maintenance on Wed which is today or tomorrow depending on where you are.
1 Like
My girlfriend is experiencing the same thing. Can’t log into any of her characters. Crashes once the load bar is full after choosing a character. BUT WoW Classic loads no problem. Tried reinstalling, didn’t help, tried doing the cache thing, didn’t help.
2 Likes
Sounds like stealth is involved in some way. Also so many people are having this problem I doubt it’s an issue on our side.
I’ll add myself to this list. Logged in on patch day, disabled all my add-ons, cleared the addon and WTF folders, did two repair scans. Attempting to log into any retail character causes error 132 after the load bar completes.
Reset didn’t fix it 
2 Likes
I’m just about ready to unsub tbh. This has been an ongoing issue for about 14 hours, and we still have no fix and no update on the situation at the very least.
Keep in mind, this was just a minor content patch. Who knows what else they will break with a major content patch?
Same here. Reset didnt fix this issue
I now have this on my launcher:
“Network conditions stopped us from loading your personalized content; here’s a look at what’s happening across Battle.net”
No idea what that even means. there isnt anything for me to click on that explains it, ot shows me whats happening.
Getting this error as well.
Seems to be something around stealth or coming out of stealth? I try to stealth Sinister strike (new rogue toon) and boom. Crash.
Edit: Also noticed, that when I log back into the game after these crashes, my auto loot (and auto loot only) option is unchecked?
I cant even get in the game though and Im a hunter
Same here with rogue. Casting shadowstrike
I could be wrong but it seems like the most common issue is centered around stealth.
I don’t play Rogue and I am having this issue still and it’s happening at character select. Some of us aren’t even able to log in.
Rogues so strong that cause others to have this issue. #NERFROGUES! hahaha j/k
Not just rogues. I saw a few feral druids posting the same thing, which is why I think it’s centered around stealth. However, it seems to be affecting logging in as well.
Still getting the error just trying to log on. Blizzard, this is a issue. We’ve had no blue post or any acknowledgement what’s so ever, people are still having issues and I’ve done everything the articles requires including reinstall the game. We need someone to actually look into this because this isn’t anything but depressing not being heard. We are having issues and we would like to have fun in the content we paid for
1 Like
I am having this same issue on sub rogue. Anytime i use shadowstrike from stealth it is instant crash to desktop with error #132. I have restarted my modem, router, reinstalled wow to a separate SSD, ran memtest overnight for 4 passes, which it passed without issue. This has to be on blizzard’s end. Did not have this issue before the patch. My other rogue on another server can use shadowstrike just fine, so its an issue with this specific rogue.
ERROR #132 (0x85100084) Fatal exception!
Program: G:\World of Warcraft_retail_\Wow.exe
ProcessID: 9660
ThreadID: 32
Exception: ACCESS_VIOLATIONThe instruction at “0x000001d77e1785c8” referenced memory at “0x000001d77e1785c8”.
The memory could not be “executed”.<Exception.IssueType> Exception
Crash
Exception.Summary:
ACCESS_VIOLATION
(DBG-OPTIONS DBG-ADDR<000001d77e1785c8>("") ← DBG-ADDR<00007ff6d055a01a>(“Wow.exe”) ← DBG-ADDR<00007ff6d054fb08>(“Wow.exe”) DBG-OPTIONS<>)
The instruction at “0x000001d77e1785c8” referenced memory at “0x000001d77e1785c8”.
The memory could not be “executed”.
<:Exception.Summary>
Exception.Assertion:
DBG-ADDR<000001d77e1785c8>("")
DBG-ADDR<00007ff6d055a01a>(“Wow.exe”)
DBG-ADDR<00007ff6d054fb08>(“Wow.exe”)
DBG-ADDR<00007ff6d051507b>(“Wow.exe”)
DBG-ADDR<00007ff6d1623f83>(“Wow.exe”)
DBG-ADDR<00007ff6cf161233>(“Wow.exe”)
DBG-ADDR<00007ff6d0075d93>(“Wow.exe”)
DBG-ADDR<00007ff6d0077ded>(“Wow.exe”)
DBG-ADDR<00007ff6d0076685>(“Wow.exe”)
DBG-ADDR<00007ff6d033301c>(“Wow.exe”)
DBG-ADDR<00007ff6cebb4e02>(“Wow.exe”)
DBG-ADDR<00007ff6cebb529e>(“Wow.exe”)
DBG-ADDR<00007ff6cebab25a>(“Wow.exe”)
DBG-ADDR<00007ff6ceb998c5>(“Wow.exe”)
DBG-ADDR<00007ff6ceb99899>(“Wow.exe”)
DBG-ADDR<00007ff6cebe6238>(“Wow.exe”)
DBG-ADDR<00007ff6cebefa3a>(“Wow.exe”)
<:Exception.Assertion>
1 Like