Firestorm wow error 132
- #Firestorm wow error 132 install#
- #Firestorm wow error 132 drivers#
- #Firestorm wow error 132 software#
Retail WoW had been crashing to desktop seemingly at random.
#Firestorm wow error 132 software#
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. All voltage, speed, and temperature readings in HWiNFO64 during games looked fine. My new power supply was actually mentioned in a thread as being one that stopped someone’s Error # 132 when swapped to.
#Firestorm wow error 132 install#
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.ĭefault 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.
#Firestorm wow error 132 drivers#
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. 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. I had tried dozens of fixes without success, which I’ll list below…Ĭlean 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. When the issue began (Sept / Oct 2019) is important, because that definitely aligns with BIOS version / specific AMD AGESA microcode as being the culprit. MSI motherboard BIOS currently installed: E7B89AMS.A90 GPU: Nvidia / Gigabyte RTX 2060 Gaming OC ProĪM4, B450 chipset drivers currently installed: 2.04.28.626 I flashed that older BIOS this past week (released Sept 2 but dated August 29), after which the crashes to desktop stopped! The fix I tried that finally worked: BIOS for my B450 motherboard that has version 1.0.0.3ab of AGESA. It was only after reading so many Error # 132 threads that I finally saw input from Crosswinds on Ryzen 3000 processors in AMD motherboards. I’d tried dozens of fixes during the past 8 to 9 months but none of them had worked! It was always Error # 132: memory could not be “read” or could not be “executed” etc. Thanks to Crosswinds suggestion/fix of using a prior BIOS, World of Warcraft doesn’t crash to the desktop anymore! I’ve had the issue of retail WoW randomly crashing to desktop since at least as far back as October 2019.