As the title suggests, I am writing here to report 2 strange mishaps that are frequently occurring to me during 8.2.5, causing me to disconnect from the game.
The first error I’d like to report is “Error 132” - which I am getting A LOT (sometimes up to 4-5 times per day). By searching at the game’s root folder and then opening the “_ retail _” and “Errors” subfolders, I can see that the error logs are stored there everytime this happens. The .txt files read;
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe ProcessID: 12848 Exception: ACCESS_VIOLATION
The instruction at “0x00007ff6839ca189” referenced memory at “0x0000000000000190”. The memory could not be “read”.
<Exception.IssueType> Exception Crash Exception.Summary: ACCESS_VIOLATION (DBG-OPTIONS DBG-ADDR<00007ff6839ca189>(“Wow.exe”) DBG-OPTIONS<>) The instruction at “0x00007ff6839ca189” referenced memory at “0x0000000000000190”. The memory could not be “read”. <:Exception.Summary>**
The second error I would like to report is a really bizarre one because it happens completely randomly and out of the blue, without leaving any traces as to what exactly is causing it. So far, I have only encountered it Inside arenas, with the last time being approximately 10 minutes ago. What basically happens is;
I log into the game. I don’t have latency, or fps drops. Everything seems to be working just fine.
I queue up for Arenas. Before the gates open, everything keeps working 100% fine.
During the matches, usually when I strafe left, BOOM. The WoW application completely shuts down without any error messages shown. As if something is forcing the task to end.
Stuff that I have tried as solutions;
Updated my Windows + Graphics drivers.
Updated all of my addons (I try to do this daily each time before I log in).
Scanned + Repaired WoW through the Bnet Client 2 times.
Addons I am using are;
BigDebuffs
Details! Damage Meter
Enhanced Raid Frames
flyPlateBuffs
Gladius
Leatrix Plus
OmniBar
Quartz
SafeQueue (Out-of-date at the time of writing this)
sArena (Out-of-date at the time of writing this)
Simulationcraft
SpellNotifications (Out-of-date at the time of writing this)
Tomtom
Deadly Boss Mods (with only “The Eternal Palace” activated)
Total AddOn Memory while in game is equal to 23.50 MBs.
Now Blizzard, see, this is very annoying from a player’s perspective. It feels really disgusting to lose Rating, MMR, and “force” my teammates to go through these losses as well. Please, do something.
Any help is greatly appreciated. Thank you in advance.
Provide the code from the pastebin link in your next post - the bold portion of this example: https://pastebin.com/2Qk28Ed1P )
You might also want to copy the entire 132 Error log file for this error. What you posted seems only like a small part of that log.
Additionally can you please try changing the DirectX settings.
If moving to DirectX 11 does not resolve the issue, please switch back to DirectX 12 by reverting the changes.
Instructions for enabling DirectX11 in World of Warcraft:
in Game Settings, activate the option “Additional command line argument.” Type in one of the following commands:
-d3d11
-d3d11legacy (for legacy DirectX11)
Try running the game.
You might also want to close all other applications to resolve any potential software conflicts. And then run the game.
If you are using any extra displays - unplugging extra display may resolve the issue as well.
Hey there Yenredyn. Thank you for getting back to me. Ok, so.
MSInfo was created successfully (and it is less than 15 MBs as well), but Pastebin will not let me save that much info unless I pay for an account upgrade. Is there no other way I could send the needed files to you Yenredyn?
Yes, you are right about that error log regarding Error #132. However, I cannot post it on the forums I think since it includes links or phrases that the system thinks are links. Blockquoting doesn’t seem to work this time, but I’d rather send that stuff to you personally, if such thing can be done.
I used the command “-d3d11”.
Regarding apps, the only ones running while I am playing are WoW, Bnet, and Discord.
I am not using any extra displays currently.
EDIT: Since we are speaking of fixes, could you guys also please fix this broken forum system as well? It’s impossible to reply to your quotes Yenredyn, because they include links in them and I get the “You cannot post links” error. Lol.
If MSinfo file was that large you probably have lots of different application or other crashes logged in it. You can try uploading the file to Google Drive, OneDrive etc. service and linking it here.
edit: You can add links by inserting them inside preformatted text. Click the toolbar button (6th button from the left) or insert the link in between two ` characters. Stupid workaround, but forum restrictions are pretty weird.
Unfortunately we aren’t able to check the MSInfo file since it’s set to Private, however from the Crash log, it looks like the game’s not able to properly access your system’s memory
Generally we do see this if some other software is interfering, so I’m going to recommend performing the step to close other programs, since you didn’t mention doing that in your followup. The specific method outlined there is more effective than just manually closing programs, too, as it totally stops other software from loading up. Security software is normally the culprit when it comes to errors accessing memory, and that rarely fully shuts down if closed manually, which is why it’s vital that those specific steps are followed
I am so, so sorry about that - I have very limited experience with using Google Drive. I updated the links in my original post - they are now set to “anyone with the link can see”.
EDIT: One more thing which I forgot to add up previously, I actually followed your advice and disabled literally EVERYTHING on the startup tab. Here’s a screenshot of that too;
Sorry to see that you’ve been crashing in wow and thanks for gathering all the information you have been.
I had a look into this and this is occurring as a result of using an old bios. The first generation of Ryzen CPU’s do require their Bios and Chipset updates to run stably.
While we cannot assist with an update of your Bios. However, you can grab updates from your motherboard manufacturer’s website. The bios update you would be looking for must at least have AGESA 1.0.0.6 . Have a local tech savvy friend or local technician help you with this if you aren’t familiar with how to update your bios.
Once updated, you should also consider downloading and updating your chipset drivers.
