I got this, too, in the last week. Couple others as well. I personally have gone through exhaustive troubleshooting with mine. It crashes about as short as 10 minutes in the game to as long as an hour. Even checked temps, and those were fine. Just letting you know you’re not alone!
I have an nVidia 1060 6GB. When I did the actual full UI reset (removed installers, removed the folders), I didn’t crash at all with bare bones. I started a fresh installation of addons, boom, two minutes in and I get a crash. So now what I’m doing is testing to see what addon it could be.
Friends are telling me it’s my GPU, but if it were a hardware problem, I’d be experiencing much more than just WoW crashing. Other games would be throwing fits, and I’d probably be riddled with BSODs. But I’m not, so…
I’m batting zero like you, Fairway. Isn’t it odd this has only started, though, within the last two weeks?
Same here. I even did a full-blown clean install of Win 10 1909 Update. Thought it was maybe a driver or something lingering. Nope. Wasn’t that. One post on here mentioned closing the Bnet app while in-game. That didn’t do it, either.
You know, it’s weird, Fairway, but a combination of doing that (again clean installing nVidia’s drivers) and – for whatever reason – having it so that Wow.exe is marked to run as admin, I haven’t had a crash yet. I wonder what could have gone wrong in my previous clean installs of 441.66, and what does running Wow.exe as admin accomplish?
Maybe a blue could fill me in? xD
Spoke too soon. I mean… I took off run as admin, but I still don’t understand why it’s doing this.
Hey Crosswinds,
Based on what you described and the errors you are getting, there may be something else on the computer causing a problem. Try closing all other programs to test WoW by itself. You could also try creating a new Windows user account to see if there’s any difference.
If none of that helps, then you may want to contact support and include a MSinfo so this can be investigated further.
I appreciate the reply, Zen, though I’ve already been through extensive troubleshooting with tech support. Though I believe I have… figured out the problem? Seems I was using DDU before it was made fully compatible with 1909. When I switched back to 1903 with a clean Windows install and full UI reset, I got a crash, but after I ran SFC /scannow and switched to DX11, I’m so far fine.
I’m just hanging out in-game now to see if it will randomly crash again with error 132. At that point, I am just going to RMA my graphics card, as I know it is not a problem with my memory (extensive MemTest86 tests showed no problems). Then I am going to try with my addons and test from there.
But I think I did solve the mystery: a not-fully-compatible DDU trying to clean drivers on 1909. Well, they’ve since released a compatible one. Mea culpa on that one. If I have further issues, in the event I RMA my GPU, I will make another thread. Thank you!
Okay, it did crash, but when I did a full UI reset, it wouldn’t. Out of curiosity, I deleted the Cache before I logged back in – this time with my addons. No crash. Log out, log back in, same Cache from before… and crash. Delete Cache, log in, no crash.
Why is this? o.o
Crosswinds,
I have swapped out my 3600x for my friends 3700x. Been playing for two days now and NO Crashes so far.
I have the 3700x for a week, so I will keep you posted with my testing.
Zjocura, you were correct about the 3600. But it is not exactly the processor itself, insomuch as it is AMD having messed up something in the memory management of the chipset for that series of Ryzen.
It occurred to me because, as I said before, this has only happened to me within the last month, and the last update for AMD’s chipset for x570 boards 11/25. This lines up almost perfectly with when I started having the issue. So I believe it’s a matter of the hardware not having the correct information to process whatever for stability on the WoW client.
I just had to roll back on stuff. Latest stuff doesn’t always necessarily mean stable, I have come to learn. 
Crosswinds, how are you going with you error #132?
As for myself, after using a borrowed 3700x for over a week now. I can 100% conclude that its a faulty CPU and consistently reproduce the crashing on one CPU and not the other.
After I swapped my 3600x for my friends 3700x, all my crashes in WoW, Diablo 3 and PoE have gone away. I changed nothing else in the system, same drivers, RAM, video card, etc. After CPU swap, the system booted like normal without any differences, even kept my RAM settings and stock timings.
Used the 3700x for a week, not one crash or a hiccup in anything. Swapped the CPU back to my 3600x and within 5 minutes it crash in PoE and WoW crashes within hours. Once again, nothing else changed, but the CPU. Same BIOS settings and system settings, in every way.
This is a very odd situation and I don’t know how you go about trouble tooting it, as my 3600x is 100% stable in Prime95, AIDA64 and MemTest64. Which I have ran for one week straight without any errors! It’s very odd that this error gets picked up in 3D applications only.
Hopefully this helps someone out there to troubleshoot their error #132 Memory could not be Read/Written on a Ryzen system.
My fix was going back to a BIOS version with 1.0.0.3abb, as opposed to anything higher (A4 through A6, I’m on A3 now). Apparently it’s a rather low-key issue with 3600s and BIOS versions from 1.0.0.3abba to 1.0.0.4b for at least MSI boards. So it was technically my hardware – just bad implementations of BIOS for my particular processor. Crazy, right?
Interesting, its definitely a big issue that should be looked at.
As I don’t think its limited to your MSI board only, as I experienced similar crashing on my Asus board.
Unfortunately I could not go back to the 1.0.0.3abb BIOS on my board, as some of the features did not function properly in the BIOS. So all my testing was done on the 1.0.0.3abba code with a couple of BIOS revisions that had some bug fixes from Asus.
Ether way, you should not have to go back to old BIOS’s to have a stable system. Generally its the other way around.
I just know that it works, and I am thankful that, for now, I don’t have to contend with error 132. And yes, it affects more than just MSI motherboards. The critical factor, though, is the 3600 CPUs. The BIOS releases have been just awful for that line. No idea why, personally, and AMD hasn’t said anything.
EDIT:
Here’s the thread I found that gave me my information:
https:// community. amd. com/ thread/ 244029
Sorry, can’t post links, so just C/P and bring the link together. xD
Crosswinds,
Thanks for reaching back out and letting us know how you fixed your issue. That’s definitely a pretty niche issue which isn’t a common fix for this, but we’ll keep an eye out for it. Do you mind marking your post as the solution using the check box to help others find it in the future?
Sorry, Drak, I’m not seeing how to mark my post. Don’t I have to be the OP to do so?
… yes. x.x I missed that you weren’t Op of the last thread. I’ve split you into a separate thread since your issue ended up being wildly different from the previous poster’s.
Marked. And yeah, I know it’s an odd fix, but apparently it’s a thing with people who have the first batches of 3600s? I did post the link (broken, since I can’t actually link anything) to where I got my information. Sadly, that’s ALL I could find on the matter.
1 Like
I ended up replacing my motherboard and that fixed the error 132.
Hi Crosswinds,
I am really happy to find your thread, i think i am having the same problem. I am playing WOW on my new computer (MSI mortar B450, 3600) and i have tried everything including change my RAMs, but nothing works.
I created a thread and waiting for reponse.
what bios should i get for my motherboard?
I have been tortured by this problem since i got my new computer, my old one with intel works fine.
if this is true, I can’t believe AMD let this happen, and did nothing to fix it!