Error 132 - referenced memory could not be read

Rumae-kul-tiras · March 28, 2021, 7:14am

What eventually fixed this error for me was to turn off the Discord overlay option in the Windows Discord app. So you might want to try that.

Malekir-mazrigos · November 6, 2021, 7:39am

This worked for me. Thank you

Chonkycheeks-azjolnerub · June 17, 2022, 1:51pm

I forced wow to run in Direct X 11 mode by adding -d3d11 in the game options and it stopped crashing. So it seems to be related to something in Direct X 12?

Jethz-defias-brotherhood · June 17, 2022, 2:00pm

oh and it started after my upgrade to Windows 11.

Mosinathus · June 18, 2022, 4:49pm

The 132 Crash error is a catch all error and can be caused by many different things. This thread is also rather old so I’m going to lock it out. If you are seeing crashing, please create your own thread on the issue after checking if these steps.