Error 132 - referenced memory could not be read

Thanks for the logfile - from a review we can pretty much definitely rule out a game/code bug, this problem very much looks like it has it roots somewhere beyond WoW itself.

Addons would be a possible explanation - there are a lot showing up in the log and some of the captured data indicates faulty LUA-code (which is what addons are made of). With that in mind as a first step I’d definitely recommend to fully delete all addons and their cached data following this guide. Please note that just disabling addons will not suffice here, as their cached data would still be potentially bogging down the game.

If that doesn’t do the trick the next step here would be to take a look at the full diagnostic logs of the computer and also run a test with tool like HWMonitor - it is unfortunately possible that these crashes are just the tip of a potentially rather nasty iceberg of deep-level systemic issues. Please feel free to post links to the gathered data here if you’d like us to take a look at it too. :slight_smile: