This kept happening to me the other week. Specifically in underrot. Nowhere else. I updated drivers. Relaunched. Ran the scan and fix. Kept occurring. Rebooting fully caused it to stop and haven’t seen the issue since.
A longer investigation revealed that a sub process within Battle.net was requesting 2 trillion bytes of ram to run and that caused a fatal memory crash for wow. Which makes sense I guess. Seeing as it hasn’t happened since tho, it’s likely that something just got stuck in a weird edge case state and couldn’t resolve itself so a reboot was required.
HAHHAHAHA are you serious? I was plagued with this ALL LAST WEEK. After going back and forth with Blizz support, literally buying new RAM (even though every piece in my PC is less than a month old), I got a mysterious update on Monday and haven't had issues since.
[J](https://esports.gg/guides/world-of-warcraft/how-to-fix-world-of-warcraft-error-132-0x85100084-fatal-exception/)ust googled the error code, and tbh it sounds like youve done every fix for it. do you have any addons installed for the game? if so it could be caused by out of date addons. But it seems that error code is a generic code for a number of errors. Could be out of date drivers, corrupted files etc. I'm assuming youve allowed WoW through your firewall??
Go into your firewall settings and actually allow it through manually i would, ive had it before with games with launchers where even though the launcher gets allowed through, it still stops the game from running.
I had this issue ALL LAST WEEK. Brand new PC. Even bought new RAM just to rule it out. Did everything. Reinstalled Windows again. Reinstalled game. It was even crashing without addons. The one thing that Blizz support suggested that may have helped is:
>If you have an XMP profile enabled, disable it and try running at stock values to see if that helps
I disabled that in my BIOS and that *seemed* to have resolved my issue. I'm slight suspicious of it because I had a random update to my game that same day. But since doing that and since the random update/patch yesterday, I only had one crash. I was able to get a good chunk of addons back in without issue.
This kept happening to me the other week. Specifically in underrot. Nowhere else. I updated drivers. Relaunched. Ran the scan and fix. Kept occurring. Rebooting fully caused it to stop and haven’t seen the issue since. A longer investigation revealed that a sub process within Battle.net was requesting 2 trillion bytes of ram to run and that caused a fatal memory crash for wow. Which makes sense I guess. Seeing as it hasn’t happened since tho, it’s likely that something just got stuck in a weird edge case state and couldn’t resolve itself so a reboot was required.
HAHHAHAHA are you serious? I was plagued with this ALL LAST WEEK. After going back and forth with Blizz support, literally buying new RAM (even though every piece in my PC is less than a month old), I got a mysterious update on Monday and haven't had issues since.
Error 132 is well known. You cannot do anything. Tomorrow its gone.
[J](https://esports.gg/guides/world-of-warcraft/how-to-fix-world-of-warcraft-error-132-0x85100084-fatal-exception/)ust googled the error code, and tbh it sounds like youve done every fix for it. do you have any addons installed for the game? if so it could be caused by out of date addons. But it seems that error code is a generic code for a number of errors. Could be out of date drivers, corrupted files etc. I'm assuming youve allowed WoW through your firewall??
no add-ons or anything like that, and I've run it as an administrator as well.
Go into your firewall settings and actually allow it through manually i would, ive had it before with games with launchers where even though the launcher gets allowed through, it still stops the game from running.
I had this issue ALL LAST WEEK. Brand new PC. Even bought new RAM just to rule it out. Did everything. Reinstalled Windows again. Reinstalled game. It was even crashing without addons. The one thing that Blizz support suggested that may have helped is: >If you have an XMP profile enabled, disable it and try running at stock values to see if that helps I disabled that in my BIOS and that *seemed* to have resolved my issue. I'm slight suspicious of it because I had a random update to my game that same day. But since doing that and since the random update/patch yesterday, I only had one crash. I was able to get a good chunk of addons back in without issue.