I’m not sure where you’re getting that idea from, since people with new rigs are having this happen.
So what I’m getting is I need a new PC? Is that what I’m being told? Yet I can load into everything else, hell run around on the PTR but this right here, no, I have to have a new PC to play wow at retail. I don’t want to believe that but since blizzard isn’t saying anything, whatever. Just made canceling my subscription easier. Waste of money right now
By stealth addon i meant the additional damage from stealth, not an actual addon. should have been clearer there.
because the requirements changing will still probably effect us low ram or old window users even if this issue is fixed.
Yes, i can use stealth on my rogue just fine. switched to combat, can use ambush, etc. switch back to sub and try to use shadow strike, instant crash. Every single time. Very repeatable. Not an issue with my system at all. Only started after patch. I played all night before the patch leveling this rogue and no issues with shadowstrike at that point in time.
2 Likes
Martuuk, the additional damage from shadowstrike is 25%
A bunch of people with various rigs/os are all having the 132 error happen at launch. The requirements change you’re referring to has nothing to do w/ the error 132 at launch problem. I think this important to mention since this is a mattter that technical support needs to address.
3 Likes
For me, leveling my low level rogue, I would stealth then sinister strike. That crashed my game twice. Since then, I’ve tried stealth + ambush but so far no crashes
I can get to the character select screen. I can choose a toon, and the screen get to 100% and it crashes with this error. I don’t know what to do. If this really is my PC sucks, then with my current state of injury and such. I just wasted time and money on something that actually kept my sanity from the pain of my torn tendon. So if that’s the case, thanks blizzard for that
1 Like
< martuuk. had my old toon as my avatar.
This problem (the stealth attack crash) has definitely come in since the most recent big patch on tuesday. prior to then I don’t think I’d ever crashed, now I can reliably drop to desktop every time. I haven’t tested it on my balance druid to see if THAT guy has the same problem, but I’m wondering if Shred and Shadowstrike were two of the talents that got “updated” last patch
I don’t think the issue is with your PC.
I spent half the day troubleshooting this error, I have done everything I could on my end and it’s still not fixed.
I’m done with this game. GGWP, goodnight.
I’m going to wait to see if blizzard will respond
They need to respond…
For documentation purposes, this is the error I’m getting right when it tries to open the character selection screen.
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
ProcessID: 5812
ThreadID: 4312
Exception: ACCESS_VIOLATION
The instruction at “0x000007f98587bac2” referenced memory at “0x0000000000000000”.
The memory could not be “read”.
1 Like
+1 for this issue. I have submitted a ticket with my MSInfo and my DxDiag.
This issue is reproduceable for me by using incarnation and then attempting to use rake from stealth, this will trigger error #132 Fatal Exception without fail.
I have tried reinstallation of the game, removing all addons, running the game as administrator and even rolling back the most recent windows (11) patch, as well as the other troubleshooting steps listed on the KB article for this error, nothing appears to be working.
I am also getting this error across two different computers.
1 Like
My brother is having the same issue on his brand new PC.
It is NOT a PC or specs thing. People should really stop suggesting that.
1 Like
Then it looks like we can narrow out specs being the issue. There are a number of posts talking about graphical issues since patch, and Mac users have their own thread going about this same crash error under similar circumstances.
"Please report this ID below when communicating with Blizzard about this issue.
52181246-806B-44B1-8521-B11D59E6D5B3"
Ok now what? hahaha