I’ve had the issue of retail WoW randomly crashing to desktop since at least as far back as October 2019. Thanks to Crosswinds suggestion/fix of using a prior BIOS, World of Warcraft doesn’t crash to the desktop anymore!
It was always Error # 132: memory could not be “read” or could not be “executed” etc. I’d tried dozens of fixes during the past 8 to 9 months but none of them had worked!
It was only after reading so many Error # 132 threads that I finally saw input from Crosswinds on Ryzen 3000 processors in AMD motherboards. The fix I tried that finally worked: BIOS for my B450 motherboard that has version 1.0.0.3ab of AGESA. I flashed that older BIOS this past week (released Sept 2 but dated August 29), after which the crashes to desktop stopped!
CPU: Ryzen 5 - 3600
Mobo: MSI B450M Mortar Titanium
GPU: Nvidia / Gigabyte RTX 2060 Gaming OC Pro
RAM: XPG Gammix D10 3000 - 2 x 8GB
M.2 NVME: Samsung 970 Evo Plus - 500GB
PSU: Seasonic Focus SGX 650w (SFX-L)
OS: Windows 10 Pro, version 1909
AM4, B450 chipset drivers currently installed: 2.04.28.626
MSI motherboard BIOS currently installed: E7B89AMS.A90
—> AGESA 1.0.0.3ab
When the issue began (Sept / Oct 2019) is important, because that definitely aligns with BIOS version / specific AMD AGESA microcode as being the culprit. I had tried dozens of fixes without success, which I’ll list below…
Clean slate installs of World of Warcraft, no addons, Win 7 compatibility modes, run as Admin, exit BNet launcher while playing, game scan & repair, renamed Cache & Interface & WTF folders, lowered the graphics settings, tried every setting for different versions of DirectX… WoW crashing to desktop continued.
Reseated the graphics card, changed which slot the power cable plugs into PSU, installed software to ensure that fans on card are always on and it isn’t overheating, stress tested the graphics card and it passed, DDU driver removal and Nvidia GPU driver install with each new game ready release, clean install with no GeForce Experience, default Nvidia settings… WoW crashing to desktop continued.
Updated AMD chipset drivers, and motherboard drivers every time that new ones were released, tried chipset releases from motherboard vendor, then uninstalled those and installed chipset driver direct from AMD, tried different Ryzen power plans… WoW crashing to desktop continued.
SFC scan and repair of Windows 10, reset Restore points, increased the Page File virtual memory, cleared space on OS drive and there’s plenty of space on game install drive, Game Bar has always been turned off, no capture/recording ever, no processor overclocking, no processor overheating, passing stress tests, reset IP, flushed DNS, restarted modem and router… WoW crashing to desktop continued.
Default BIOS settings, flashing new BIOS versions, cranking my RAM’s speed down, disabling/enabling XMP, running only 1 8GB stick of RAM, then swapping that 1 RAM stick with the 2nd, sticks pass MemTest86 with no errors… WoW crashing to desktop continued.
My new power supply was actually mentioned in a thread as being one that stopped someone’s Error # 132 when swapped to. All voltage, speed, and temperature readings in HWiNFO64 during games looked fine. Nothing that I had done in software nor in hardware swaps had fixed the issue, and it continued to crash to desktop mid-game, sporadically.
Retail WoW had been crashing to desktop seemingly at random. It was unpredictable. Sometimes the game would last an hour, 2 hours, even 4, but other times it would crash to desktop after 3 minutes or just 20 minutes. Sometimes, I was in a Legion 5-man when it happened. I’d get back into the game just to find that my character had been vote kicked from the dungeon. Most often my character was just standing there before a crash, for example in the WoD garrison doing nothing.
There was no way to reproduce it, but it seemed that experiments bumping up the in-game graphics setting by 1 increment beyond the otherwise “recommended” setting at the start of each test run would saturate the memory faster and the crash seemed to occur sooner. Increasing the Page File did not prevent the crashes. There were no consistent variables for when the game would crash when testing each stick of RAM on its own, or together, and then swapped between slots on the motherboard.
Given that this is an issue with Ryzen 3000 / Zen 2 in AMD motherboards with different chipsets and made by different vendors, if it’s not a Blizzard game code issue and not a CPU flaw (I’ll throw Prime95 at my Ryzen 3600, though I expect to find nothing amiss), it’s something that I’d hope AMD is willing to acknowledge.
This is especially concerning because it’s been happening for the past 9+ months for some of us, creating a lot of frustration. At least 1 player has reported that AGESA 1.0.0.6 in recent BIOS releases for AMD boards hasn’t prevented the issue of WoW crashing to desktop in their B450 board: