Greetings fellow adventurers. Over the last few weeks I’ve had maddening crashing issues with both WoW and another non-Blizzard game, and I couldn’t figure out why it was happening for the life of me. So after much back and forth and troubleshooting with Blizzard tech support, they have concluded that there is a BIOS bug affecting AMD Ryzen 3rd Gen (3xxx) processors. My CPU (Ryzen 7 3700X) and motherboard (ASUS TUF X-470 Plus Gaming) with the latest BIOS fit the criteria.
Thanks to the player known as Crosswinds on another thread, he managed to figure out how to solve the crashing issues, at least temporarily. Every BIOS version later than AGESA 1.0.0.3ABBA seems to have issues with the aforementioned CPU’s. Flashing your motherboard’s BIOS to that version seems to fix the crashing issues, at least for me. I recommend anyone who experiences the same problem to try that and hopefully it will work for you until AMD solves this problem.
1 Like
I found something interesting today in my WoW folder.
Apparently, yesterday I did get an error 132 (while on 1.0.0.3abb), but it never crashed my client. I think there is definitely some underlying issue with the microcode, and I hope they all find a solution for it. This is the first I’ve seen of an error 132 on 1.0.0.3abb. But again… I found it today, and it didn’t crash the client. Heck, the error never bothered to show up.
So even that BIOS version isn’t enough to stop the crashes? That’s disappointing. It’s worked for me so far, but I suppose now it could be only a matter of time before it crashes again for me.
Well, it didn’t crash. It just produced an error log. I don’t know how that even happened. Normally a 132 crashes your client. This one didn’t.
Edit: I am thinking it happened when I exited the game. It’s odd, because this 132 specifies that the memory could not be “executed,” whereas it’s typically either “cannot be read” or “cannot be written.”
Hey @Lasthus and @Crosswinds (Not sure you’ll get this since this is an oooold thread),
I was wondering if your BIOS issues ever got resolved? I am having maddening error 132 crashes and haven’t been able to find a cuplrit (I’ve done all sorts of things like play with a fresh install of wow, reformat windows, switch our hardware, etc). This all started at Shadowlands launch, but specifically a week before that I upgraded from a Ryzen 2700x (and probably fairly old MOBO firmware) to a Ryzen 5600x (and a new mobo, with new firmware, currently Asus Tuf Gaming x570-Pro (Wifi). I didn’t actually think the CPU and/or Firmware could be the issue, as that seemed a bit too out there, but this thread makes me wonder otherwise.
My current bios/firmware version has AMD AGESA V2 P1 1.1.0.0 Patch C. If there really is a bug (or bugs) between WoW and newer AMD firmware, it seems like I might be SoL? I don’t even have the old MOBO + CPU anymore, nor would I really want to downgrade to it anyway… I guess it’s possible this stuff has just been a bug in AMD’s firmware for ages now, and was inherited into the next gen? It feels like my only way to A B test something like this would be to obtain an Intel Mobo + CPU, which seems like a bit of a stretch lol.
1 Like
It turned out to be a faulty CPU – in my case, the Ryzen 5 3600.
I should change my class to death knight since I’m raising this thread from the dead.
Unfortunately I’m still experiencing crashes MANY months later with no fix in sight. It appears that it is not related to hardware or anything with AMD specifically. It is entirely beyond the scope of Blizzard’s support and as such I will not be receiving any assistance from them from here on out. I’ve even gone so far as to install a fresh copy of Windows 10 Home on an entirely new NVMe drive and yet it still didn’t resolve my issue.
Reading the dmp files created every time WoW crashes, it labels it as memmory_corruption. Yet I’ve run MemTest86 plenty of times with no errors. I will also have BSOD’s that all point to some kind of driver issue, but I cannot for the life of me figure out which one it is or where it is located. I’ll probably make a new thread with more details.
I would just like to chime in to say that I’ve been having this issue for months now. I have contacted Blizzard and tried every fix they suggested. I’ve done fresh installs of WoW AND Windows 10. I’ve updated all my drivers. I’ve run memtest with no errors. EVERY OTHER GAME RUNS FINE. WoW is the only one that crashes. I’m seriously about to drop hundreds of $ on new hardware just so I can play WoW. This is ridiculous.