132 Memory Cannot Be Read - Blizzard stop auto replying and address the issue! **SOLVED!**

Constant crashing due to this.

Reports sent last one was D565723A-1373-4D06-AE59-BE7DF8C20D77

Any assistance on this would be greatly appreciated.

I have done as the other forum posts suggest inc full wow install, this is a brand new PC so wow was my first game installed, have removed my fav mounts, have run tests on the machine still nothing.

This is becoming a very frustrating issue and would like some assistance please.

The most common cause of error #132 is bad ram. As it is a new PC that is something you need to check.

Download a Memtest95 usb stick, boot from the USB stick, and let Memtest95 run for a while to check your ram for errors.

I too am getting Error 132 frequently, since dragonflight update - I have followed all the guidance, reinstalled PC from scratch, reinstalled WOW from scratch, run memtests and GPU memory tests with no errors reported.

Everything was fine until the update and now random crashing all over the place when playing WOW - having a look at the crash logs that get dumped it’s WoW.exe that is exiting - I obviously can’t read the dmp files - I’m on latest nvidia drivers, happens on those and on rollback version too - have tried running in compatability mode - you name it I’ve tried it but this seems so unstable on my machine!

Happy to upload any logs or dmp files needed and have been sending the reports when the game crashes out - it’s getting totally unplayable :frowning: hopefully a blue picks this up!

1 Like

Also hoping a blue reads this as im sure some changes that were made have now begun to cause these issues. Surely with all the data we send about this they can come up with some patch.

If you want to report it as a bug, that has to be done in game. Bug reports are not collected via the forums in the EU regions. Nor will the Blues forward any bugs reported to the Developers.

Just… For the love of all thats holy…

Use the BIG BUTTON in the top left marked “Submit Feedback or Bug Report”, and not any of the little buttons in the bottom right. There is a reason its big and the others are little… But the amount of people who still gravitate to the little buttons in the bottom right, then say the bug reporter doesn’t work, is… Frustrating.

1 Like

Bug Report submitted - hope waning

Received the usual BS auto reply from Blizzard asking me to try everything I had already detailed in my ticket.

Its a wonder anyone pays for this game anymore considering the after care or lack of!

Make sure you test your memory meanwhile just to rule out the posibility of it being ram, i personally tho suspect there is a memory leak in wow or a bug that causes bugs like yours or other problems.

Error 132 is a very general error that encompasses many causes. Looking at the ones you sent in, they all seem to be caused by Addons. Do a full UI reset and do not reinstall either Addonmanagers or Addons.

Mem test completed no errors. Running with 0 add ons still the same.

Cannot copy the error log as the post says I cannot add links (no idea what its referring too)

Can technically still get errors in some memtest while not having them in others depending on what you use hci memtest karhu testmem5 classic memtest86+ and new memtest86 etc some aren’t free tho, but likely you have no problems especially if you ran over night for like couple of hours

Hope you figuring this out soon, if been trying to figure out why my system freezes or game crashes my gpu, and i think i finally found it compute effects are broken atleast with MPO disabled.

Is there something specific you are doing when it crashes ? maybe you seeing a trend like always being in same situation when it crashes cos consistency always is a clear give away of a software related issue.

Do you use AMD or Nvidia GPU with MPO disabled?

Guessing you asking me since i mentioned MPO, i have 6900 XT

Sadly no trend - sometimes it can go hours with nothing then occasionally the graphics reset - screen either freezes or minimises and the graphics reload.
Last time I got the wow error I was flying - time before that was sitting still in SW. No pattern nothing stressfull

Is Prime95 stable ? Is Furmark stable ? Is Prime95+Furmark stable ?

Yep all stable - its got 64gb ram 6000mhz speed. GPU is MSI 4090 NVIDIA have done all the fresh installs. All I have left to try is disabling the XMP in BIOS.
Fingers crossed :frowning:

Your gpu driver crashes ? cos for me system freezes and every time it does not it crashed gpu driver after it freezes, does your system freeze and then crash gpu driver as well ?

edit: can you do proces analyzer from details tab on wow.exe in task manager does it report deadlock state of some sort ?

Solved!! XMP profile in the BIOS was causing the crashing. Now its disabled no more crashes.

And now your 500 Euro ram run at 4800mhz instead.

Watch him get issue again in couple of days, i am in that position right now

This would have been detected by the Prime95 torture test.

So much for