Error 132 and BSOD

I’ve been having problems with World of Warcraft for a few months now: non stop 132 crashes (either unable to read from memory, either unable to write to memory, or an illegal instruction at some memory address), or the sporadic BSOD’s genre: KMODE_EXCEPTION_NOT_HANDLED, ATTEMPTED_TO_WRITE_TO_READ_ONLY_MEMORY, ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY… And these really only do happen with the game is running.

Sometimes there’s a week where there’s maybe one or 2 crashes, like 2 weeks ago, but then come next patch day and you’ll feel Blizzard’s wrath full on for having been able to enjoy the game and actually do some instances. And when I say instances I mean dungeons (3 crashes within 5 minutes and then nothing until the next one) and like today 4 wasted Vessels of Horrific Visions, because this problem never seems to happen in raids or bgs. Not even Ashran can trigger this (well, I think it did once, but that was at the end of it).

Anyway, clearly all this is related to memory issues. And I know Blizzard likes to shift the blame, so let me get this out of the way first:
I’ve got plenty of RAM, less than half if used even. My graphics card’s got plenty of RAM and processing power. My processor’s got plenty of processing power. Not overheating (doesn’t affect memory anyway). No overlays (ms game bar’s disabled, afterburner’s not running, discord’s not running), although I did run discord for a group 2 weeks ago (during that blissful week) and hey, look: no issues. Drivers and windows are up to date. I’ve reinstalled World of Warcraft 3 times, I’ve even reinstalled Windows. And yes, it took only 5 minutes after the fresh and clean install to crash again. So please don’t go and blame addons, by now I trust those people’s coding skills a lot more. And oh yeah DirectX 11 Legacy does absolutely nothing either. Neither does reducing the graphics level way beyond recommended.
Anything else I forgot to mention? Most likely have tried it and more…

But given that Google is littered with forum posts about error 132 and memory mismanagement, the fact that Blizzard manages to bug old content with new patches, and there actually seems to be a correlation between those patches and the crashes (given that we’ve already excluded addons), it looks to me as though World of Warcraft is currently under development by people who are still learning C++ and do not know the meaning of Bjarne Stroustrup’s infamous quote yet…
And sadly enough product aren’t a democracy, it’s not good enough to please the majority; if it doesn’t work for 100% of the people, 100% of the time your product’s faulty (unless of course it wasn’t meant to do so).

Now joking, and my best Aubrey Plaza impression, aside, please please please please please can you fix this? :sob:

If you would like someone to look at why you are getting Blue screens please post a DXdiag to start with . note that generally a program can not cause a blue screen unless there is another issue Ie driver issues or hardware issues.

DxDiag
1.Press Windows Key + R.
2.Type DxDiag and press Enter.
3.In the DxDiag window, click Save All Information.
4.Name the file “dxdiag” and click Save
5.Open the txt file above select all, copy and paste to this thread.
You can include the DXDIAG in a reply to the forum post. Place it between rows of ticks (`) for formatting:

Like this.

If it will not allow you to post the whole thing post it on pastebin.com just post the last section of the link see the highlight section below .
https://pastebin.com /y47kBy74