I recently installed the Windows 10 Anniversary Update. After doing so however, my World of Warcraft installation started crashing during launch with a message stating Error 132 memory something or other referenced such and such.
I searched online for a solution and tried a bunch of things listed on this helpful Youtube link - the DX9 fix worked, but I found a better fix. I happened across a post listing what's new in the update and found that they "added support" for World of Warcraft in the Game DVR. On a hunch, I turned it off (in the settings of the X-Box app). Voila, WoW started working again with DX11.
Edit: After posting I found that Blizzard has an official post with the same resolution: http://us.battle.net/forums/en/wow/topic/20748004624#post-1.
great
ReplyDeleteThis was an interesting read, especially the part about how a Windows update can unexpectedly affect something as specific as World of Warcraft. It also made me think about how easily font rendering and other UI elements can get overlooked when troubleshooting crashes. Sometimes a change that seems unrelated, such as Game DVR or graphics settings, can affect the way the game handles its interface and text. I’ve had similar moments where I initially blamed a font or display issue, only to find that the real cause was somewhere completely different. Posts like this are a good reminder to check the less obvious Windows settings before assuming the game files or fonts themselves are broken. I also like seeing practical troubleshooting discussions like this because they help put issues such as https://ffbetadl.com/ into a broader technical context.
ReplyDelete