Error #132

[Blickness-illidan]

The current fix is to throw out your computer and build a 10th gen intel gaming tower, none of those users have been affected

[Otís-emerald-dream]

I am also receiving the same error. Immediate crash upon character loading in game. Both w/ and w/out addons. Have tried repair tool as well with no luck.

[Vódkalol-bigglesworth]

@Bleu-skeram

Okay, so, that’s Blizzard CS just following a general order to tell people to make sure their own stuff is working. That’s perfectly reasonable in most cases. And, if you want to check your stuff, that’s a good idea at any time.

However, this is a stack overflow which should never, ever, ever, ever happen regardless of how messed up your video card driver or operating system is. Error #132 is a Blizzard problem and it requires a Blizzard solution. So, if you don’t feel like tearing Device Manager a new one at this time, just wait patiently. They will find it and fix it. They’re getting mountains of useful debugging information every time your game crashes.

I love you. Most level headed person here.

[Røxx-illidan]

It’s a stack overflow for a lot of users. repairs on our end won’t work. Something in the blizzard launcher OR in WoW classic is causing your PC to run more resources than it can handle, thus causing a stack overflow. Just gotta wait for Blizz to patch it lads.

[Brewbawlz-emerald-dream]

Small indie company. Cut them some slack.

[Tothh-grobbulus]

I am having this same exact issue, I even tried nuking everything, addons wtf/cache, repair, fresh install, I still am getting immediate crashing on any character I log into

[Jofawizard-whitemane]

Ouf. Samezies.

[Mithrandir-faerlina]

same issue here. not sure what to do. other people are online is the weird thing

[Cramptron-grobbulus]

Yes, same here. Lets see how long it takes them to fix it.

[Perkle-herod]

I wonder if it has anything to do with battlenet. I’m still offline on that for some reason and can’t connect.

[Røxx-illidan]

See my previous response, you personally cannot fix it. It’s either WoW classic or Bnet launcher that’s consuming too many of your PC’s resources and causing it to crash. You can’t do anything on your end to stop a stack overflow unless you go into the game files and fix the problem and compile it before they send it out.

[Pwrwrdstfu-atiesh]

Same issue as everyone else:

Error #132 (0x851000084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft_classic_\Wow.exe
Process ID: 14244
Exception: 0xC00000FD (STACK_OVERFLOW) at 00007ff7c1a96c46

I have tried updating graphics drivers (up to date), deleting WTF folder, disabling all addons, rebooting and only opening battle net and Wow, and disable antivirus. Considering we’re all having this issue after the maintenance, now to kick our feet up and… sob.

[Kolonel-lightbringer]

I turned my graphics settings all the way UP and it works now. I have no clue why

[Starchaser-atiesh]

Same here

All I did, was log in to my character, and take one step in the auction house, before getting a
"Error #132 (0x85100084) Fatal exception!
Program: C:\Program Files(x86)\World of Warcraft_classic_\Wow.exe
ProcessID: 12508
Exception: 0xC00000FD (STACK_OVERFLOW) at 00007ff63d78572a

Time go to play some Teamfight Tactics until it’s fixed, I guess?

Update: There was a NVIDIA driver update available, I’m going to install that and see if it fixes anything.

Update #2: Updating the NVIDIA driver did not fix the issue.

Update #3: Restarting the Bnet client also did not fix the issue.

Update #4: Setting myself to “Appear Offline” also did not fix the issue. I also noticed I have not a single friend online in my friends list. Seems like we’re going to have to wait it out unless anyone has some other suggestion?

[Rocktoe-herod]

Having that issue as well.

I can give a bit of a unique perspective. I was one of the lucky few that got in the game 10 mins after the servers went down. Everything was smooth (about an hour) until the Blizzard services were re-enabled. It took about 5 minutes after people start logging back in for it to crash. When I relogged, the error has been happening.

When the services were re-enabled, I got the message in game, but I didn’t see the friends list spam I have seen before. Just the message and then people started logging in. No friends messages though, hopefully that can help narrow it.

So something after Blizz services were re-enabled caused it.

[Diinsam-whitemane]

I’m having the same issue. I’ve tried all steps in https://us.battle.net/support/en/article/8288 (yes, including uninstalling and reinstalling) and it did not help.

EDIT - All of a sudden the issue stopped and I am able to access the game.

[Uriaah-bleeding-hollow]

I’m getting the same issue. I was able to play when the servers first came up. I changed characters and tried to log into a fresh toon. I kept getting the error. I turned off all my addons and deleted my wtf file. I tried the character that worked but I get the same error. I hope this helps in aiding to help remedy the problem.

[Orichqt-zuljin]

Same here … Blizzard batting a thousand

[Nephex-burning-legion]

Every crash log file has a gamer id of a friend in my friends list… I’m guessing there is some horrible code that is buffering all of the pending friends list status on the stack (which is loading horribly slowly in the battle.net launcher).

[Momjams-atiesh]

Same, updated all my drivers and everything, still getting the error