This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: F:\Games\World of Warcraft\_retail_\Wow.exe
ProcessID: 16560
ThreadID: 23348
Exception: ACCESS_VIOLATION
The instruction at "0x00007ff79ae11ab7" referenced memory at "0x00000000000000f0".
The memory could not be "read".
<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff79ae11ab7>("Wow.exe") <- DBG-ADDR<00007ff79ae0e0ff>("Wow.exe") <- DBG-ADDR<00007ff79adbdd4f>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff79ae11ab7" referenced memory at "0x00000000000000f0".
The memory could not be "read".
I’ve not played the game for 1.5 years and came back to the game on brand new hardware. At first I used my original install but I’ve since reinstalled the game. It occurs about every hour or so, sometimes longer (I guess it depends on what it is I am doing).
The things I have tried to remedy the problem, in the order I’ve tried them:
Updated drivers
Knocked down the graphics settings from 10 down to 7
Removed every non essential addon
Removed all addons and reinstalled the ones I actively still use
Shift-delete nuked the game files and reinstalled the entire game
Uninstalled the game via the battle net launcher and reinstalled the game
Updated windows 10 to windows 11
Ran sfc /scannow
Disabled FidelityFX things
Removed a hard drive that was at the end of its life in case Windows tried to do anything with it
It’d be really interesting to see the entire crash-log here, but from what is available in the files - this looks a lot like the crash is being caused by either an addon or the “WoWUP” addon handler.
I’d recommend to fully remove (disabling won’t do) all addons and their cached data following these steps, and to uninstall any addon handler program as well. With any luck things may work a lot more smoothly afterwards.
I hope that wowup is the cause rather than some addon data, some of the data stored is pretty valueable to me so I would really rather not have to reset my UI
I’d love to say otherwise, but from the full logs addons remain the #1 entry on the list of potential “culprits”.
Best I can tell, based on the data available, the #132 condition occurs because WoW is trying to access a memory section that should be reserved for the game, but instead of finding the expected data that should be stored there something else occupies the space (which is a very commonly addon-induced problem). This in turn causes the game to fail on processing the instructions it was working on, and ultimately the crash occurs.
In terms of preserving your custom UI it should be called out that the instructions I linked above allow for it to be fairly easily restored, should the problem persist after the removal has been tested (basically, all you’d need to do is rename the folders again). As such the test can be performed without risk of unnecessary losses.
Oh yes I know that the data is not “gone” gone, just that the crash doesn’t occur until hour(s) into the game. As such testing it requires actively playing the game without any addons. Something I’ve not done since… patch 1.5 I think
I’ll give it a shot playing with the default UI and some absolutely essential stuff for running dungeons like weak auras and only adding what I need and dbm.
Oh and not having wowup running in the background ofc
Both of the mentioned addons unfortunately very much have the potential to cause exactly these issues. For a reliable test this would have to be “pure” WoW UI, without any kind of modification to it.
That is fair, however if those addons (as a fresh install, with no prior WTF data) are causing my game to crash the game becomes relatively unplayable on a higher level of game play in higher keys and raids. So I might as well just not play the game at all then sadly
idk if it helps but i have 132 crashes when my dram is at 1.2-1.25v, if i set it to 1.35 it stops crashing and never occurs anymore, however it can only be my personal issue
