For about the past week or so, whenever I try to launch WoW, the launcher will minimize like normal, but then I get the 132 Fatal Exception error window saying ACCESS VIOLATION and the memory could not be “read”. The follow up window behind it lets me submit a comment to Blizz about what I was doing at the time of the error, with a reference code 60BE9BA5-8F39-463E-A16D-C08B27415F05 if that helps. This is all before the client even loads, so its not a character/zone issue like I’ve seen in other threads.
I tried running the Scan & Repair from the launcher and deleting the Cache folder but its still happening every time.
I don’t have a solution, but I’m having the same error. It just started today for me.
This also started for me today. It was the first time I launched the game today and I had just updated an addon called The Undermine Journal before launching the game. After I got this error, I removed the addon and tried launching wow again and it worked fine. I’m not sure if that’s a coincidence or if something in the addon update caused some weird issues. So I’d check any recently updated addons and remove until they update again and see if it helps.
I’ve never had problems like this before, ever, and I’ve used addons for quite some time (including this specific addon) so this error is a weird new thing to me.
Started happening with me too. Makes the game almost unplayable for me.
Im having the same problem for the past week and i literally just installed the game 4 days ago once more. Nothing i seem to do works and every time i might wanna log in i have to fully restart my computer for a small chance it seems to allow me in.
This is happening to me now as well. I uninstalled and reinstalled the game and removed all addons. This happened once before and I had to wait until after maintenance for the game to work .
I got it starting today as well. Have been playing SL on new characters for about three weeks. Cannot figure out whats up ;o(. Error 132 (0x85100084) Fatal Exception! - also says Access_violation.
I’ve got the same thing happening. I have no addons, this started yesterday when. I have uninstalled and reinstalled but still get the error. I am able to drag the error popup to another monitor and play like normal.
OK, so I’ve found an answer on another thread Keep getting 132 crash error - #44 by Azerious-fenris. If you go into the Game Settings on the launcher, click the Additional command line arguments box, and enter -d3d11 in the field that pops up. Make sure you’re in the WoW dropdown (obviously) because it’ll bring up a list of your Blizz games by default and I almost changed the settings for Diablo by accident! 
This completely solved my problem (for now, that I know of) and I hope it can help you guys too! Good luck!
1 Like