- Hello Since year or more i cant play WoW on my main PC because i get constantly crashed by error#132 memory could not be read.I checked EVERY SOLUTION GIVEN BY BLIZZARD or people in the internet.Moreover i bought used ram,disk,procesor and motherboard.I spend long hours checking forums all for nothing,nothing works beside that I wrote ticket for blizzard asking for help but they linked me blizzard webiste when I indicated in the ticket that I have already checked all the methods.PC has been checked for issues by the IT guy and said my components aren’t broken and data isnt corrupted.I really need help because WoW is the only game that doesn’t work and error constantly appears.Thanks for you help and patient (sorry for bad english).
1 Like
Can you please upload your system files to pastebin.com and reply with the links to the files using the preformatted text option to encapsulate the links.
Also if you can find the game error logs for a couple of the latest 132 errors from there, these can help us to better identify the issue as well.
here are system files
and here error logs:
https://pastebin.com/h44dyiT6
https://pastebin.com/0CtENbSE
https://pastebin.com/WdF1GY3F
Thanks for the logs! It does unfortunately appear the MSINFO file is missing, which would contain most of the interesting data - but a loose picture is forming from the DXDIAG and crash-record data as well.
More specifically:
Best I can tell from the captured data this is a memory conflict, in the sense of WoW being unable to access the memory areas normally assigned to the game. This in turn essentially chokes the game, leading to the crashes you’ve been seeing.
Issues like this would typically be caused by other programs “hooking” into WoW, or incorrectly occupying more memory space than they have been assigned. In some rare cases malware may also lead to such results, as it also occupies memory space (and generally does so covertly). Without the MSINFO log there is no realistic chance to accurately determine which specific program is getting in the way here, so I’d recommend to start with a bit of tabula rasa - let’s clear out as many as possible, and see how things go from there. Instructions on this can be found here: Click me please!
Primary attention would be on any application that spawns an “overlay”, such as Discord, Overwolf, Nahimic, Razer Synapse/Cortex and similar tools. Removing said tools, or at least turning off their overlay-functions, would definitely be worth a shot.
Thank you for the answer. Unfortunately even after turning off overlay programs the error still occurs. I tried to put the MSINFO log on the pastebin but the file is simply just too big for that (almost 3mb) and it’s currently impossible to buy premium there. If you know any alternatives then i will for sure check it and try. Here is the newest error log after turning off programs mentioned above.
Edit:
I reduced the size of the MSINFO file by following the guide on the blizzard site so i can paste it on pastebin.
https://pastebin.com/1f6ASxpV
it has the reduced size as i mentioned above
1 Like
Hello again!
Unfortunately it seems the shortening process of the MSINFO log may have been applied a bit too generously, as the entirety of the Windows error report section and even a fair amount of the standard data is missing. That said, the fact that the file was north of 3MB in size is somewhat telling - the vast majority of the log was apparently composed of the aforementioned error reports (as the default system data is only about 200-300KB), so there must have been a great lot of them for the log to balloon to such dimensions.
Without the report section there is little we could directly suggest at this point. The crash log still points to a type of memory conflict, so checking out the RAM sticks and banks they’re seated in would be worth a shot though - removing the sticks one by one (and possibly seating them in different banks) is an option here.