Since the prepatch I’ve been having lots of game crashes caused by error #132. Before the prepatch I never had any sort of problems with World of Warcraft since i built my PC 2 years ago. Now after the prepatch sadly this error keeps happening to such extent that it makes the game unplayable.
Error #132 keeps happening while being idle in city, flying somewhere, being in dungeion or raid, being in my own instance (Garrison).
Steps I tried to do to fix the error:
-
as with any new prepatch I went and tried to play without addons sadly to no avail
-
next I went and updated every drivers/ windows update, closed background applications, tried reinstalling graphic drivers in safe mode and wiping old ones using DDU that didn’t helped either
-
next I uninstalled every blizzard game and battlenet and and deleted all files from my PC and did a fresh install of battlenet and WOW only
-
after the above steps didn’t produce any steps I decided to completely wipe out my main drive and I reinstalled windows 10 and every drivers from scratch, sadly with no results once again
Here’s the example of the errors I keep getting:
Error #132 screenshoots
Here’s the link to MSInfo:
https://pastebin.com/0L1dX3Vb
and here’s the link to DXDiag:
https://pastebin.com/qeQzUrq1
here’s the link to pastebins of Error #132:
https://pastebin.com/W4W61vMR
https://pastebin.com/h9baDrvY
https://pastebin.com/5WQw7JD0
https://pastebin.com/Fi46hmhq
https://pastebin.com/fL13nsW5
https://pastebin.com/dXRtkvXY
https://pastebin.com/scGV58Tk
https://pastebin.com/LR03uev3
https://pastebin.com/SeYBYwZE
https://pastebin.com/65ZuhWsU
I would like to mention that while playing Shadowlands beta (lvling, doing HC and Mythic raid testing) I haven’t had any of problems with crashing even with using addons, while the problem on retail started with Shadowlands prepatch.
I saw from one other thread that there’s a chance to fix this problem via BIOS update, but I’m not keen on trying that due to BIOS updates for AMD chipset could potentially brick hardware as there were many updates to make Ryzen 3000 series compatible with X470 boards.
Thank you for any assistance offered.
1 Like
Heya Monoroth,
Sorry to hear that you’ve been crashing while you’ve been playing after the patch. However, thank you for all the information you included this can very often help us be as specific to your issue as possible.
In your case, it appears as though your graphics drivers may be getting into a bad state. This appears to be causing the crashes however we should be able to resolve this with a clean installation.
These older drivers have proven to be very stable and might be worthwhile trying. You can also try these current drivers. Regardless of your choice, you will want to clean install the drivers:
- Click Accept and Custom Install
- Click Install Radeon Software
- Click Clean Install
note this will require a restart of your PC, please save any open documents or files
Hopefully, this does help you avoid further crashes while playing.
Do you using the AMD Radeon Software program? If so, what version do you use?
1 Like
Hey! If you are using a amd gpu (not sure with cpu’s) roll back your drivers to an older version. I had same exact issue and it works flawlessly after I rolled back. WoW is not compatible with the latest amd drivers. I am assuming it has to do with the raytracing support they added.
1 Like
I went with latest drivers version 20.10.1, before I reinstalled windows I updated to 20.9.1, but decided to switch to 20.10.1 as it said it supports WoW Prepatch. I’ll give a Emelies advice a go and try a roll back.
Can you tell me to which version did you roll back your drivers?
I went for 20.9.1 and that fixed my problem with Error 132
I’ll give that one a go. Cheers
1 Like
I gave a 20.10.1 version a go sadly after 2 days of testing still loads of crashes (errors #132), I’ll give 19.11.2 a go and report back. Hopefully it goes well. Cheers for the links.
1 Like
I’ve been having the same issue since about 2 days after pre-patch. First 2 days and before the patch I had no issues. Now my game crashes with that error at random times, sometimes after 10 minutes and other times after about half an hour.
Did all the usual steps including removing all addons, deleting WTF, Interface and Cache folders, entire reinstall, the Battlenet and Blizzard folders in Programdata. Checking for windows and graphics drivers updates aswell, reinstalled the graphics drivers again in a clean install. Ran Memtest and Diskcheck. Nothing seems to fix it.
Really strange I had no issues before nor do I have any other issues with other games. Also strange is that I can play the Shadowlands Beta without any crashing. But retail I can crash from just standing still … I ran out of ideas now 
Running a setup with Ryzen 5 3600, Geforce 1060 6gb vram, 16 gb DDR4 
1 Like
If the graphics drivers are going into a bad state, may I suggest DDU?
Display Driver Uninstaller will delete every last trace of graphics drivers, allowing you to set it up with a clean slate, and then you can try again.
Strange things are going there. I installed 3 clients(Classic, Retail and Beta) into single folder. All was fine till today morning. After a short beta patch I start experiencing crashes with 132 error code in WoW Classic. After I reinstalled Classic client into different folder crashes dissapeared.
Think the main problem is inside code of CAS storage component(which may be different for different clients of WoW).
Tried installing into a entire, new folder. Still same crash after roughly 15 minutes. No addons or anything.
A quick update: I gave 19.11.2 a go and still had multiple crashes.
I went to BIOS and I disabled XMP profile and during testing today with XMP on and off (GPU drivers 19.11.2) I haven’t had a single crash with XMP off. When I tried playing the game with XMP profile on I instantly had crashes wile playing and while character being idle.
Gonna try updating to newer drivers with XMP profile off and see how’s stability.
For now people that have similar problem go into BIOS and check if you have XMP profile enabled and try playing with XMP profile disabled.
Another update:
After playing for about 5 days and doing random amount of content (lvling/AH/Mythic raiding/dungeon spamming etc) using driver version 20.9.1 with XMP profile off, I haven’t experienced a single WoW crash or error #132. I tried playing with XMP on with above mentioned driver, but sadly still had crashes as reported previously.
Once again it might be worth either checking your RAM via memtest or trying to turn off XMP profile and see if that helps.
Once I get some free time I’ll give a shoot at Driver Version 20.10.1 which specifically mentions support for WoW: Shadowlands pre patch, with XMP off/on.