mine continues with the error after the screen bar loads, what are the specifications of your pc and what do you use?
For any one with bootcamp D700 firepro, I finally got past the character selection without an error. The bootcamp drivers from apple update wont work, but i found these drivers from a random reddit post.
run a search for these drivers on the AMD site (at your own risk)
Unified_R5_20.45.40.15 (from around 2020)
install and Turn off the crossfire (called mgpu now). This finally got my wow past character selection. If you leave crossfire on the second gcard will run at 99% ALL the time.
Works so farâŠiâll edit if it fails.
Even if you are paying developers $120 an hour, it would only cost $20 to give some respect to however many hundreds or thousands of players out locked out of the game. For every person posting to this forum, there are probably 100 more locked out that are not posting/reporting at all.
Maybe some people are demanding a fix for everything immediately, but I am not. All I am saying is it costs almost nothing for a simple acknowledgement. It makes all the difference. I realize development is extremely complex, but Blizzard needs to understand that respecting the playerbase with simple acknowledgment and respect of paying customers is extroardinarily easy and has a higher ROI than anything else they are doing. I wonder if the Board of Directors has any concerns with such low level customers like us, that $20 of effort distributed among 1,000 customers is unimportant.
Considering the fact that there is no way for us to connect to suport directly ourselves, and we are that full mercy of an opaque and inscrutable inbox message queue, Blizzard needs to do much much much better at a simple acknowledgement like the blue post here, which should have come within a day or so of the widespread complaints.
You give a reasonable response. Not a solution, not the greatest, but infinitely better than complete disregard, at least its something. I wonder if the bean counters have an entry in their balance sheet reflecting the cost for disenfranchisement of the playerbase.
Long live WotLK.
Not just R9. 
This something that often gets overlooked. People in online communities tend to have a skewed view of how the message board reflects the broader population. I posted on here because this issue is driving me nuts and I wanted to share what was happening on my system in case it was helpful, but posting is not something I normally do. There are unquestionably way more people who are either looking on the forum but not finding a solution or saying anything, or not even getting to the forum in the first place.
2 Likes
So we all still f****ed 
How the hell does adding white and gray items to transmog or trading post a system that has nothing to do with graphics of the game become a graphics card issue
I put together my old ryzen 5 1600 with my old rx 460 with windows 10 pro, directx 12, updated drivers and it works.
1 Like
A friend has the same error since the new patch, so 10 days without able to log in WoW.
The error appears when she is trying to log into the world.
These are the list of the we tried so far but nothing works:
- Change directx 12 to 11
- Update Drivers
- Try to login without drivers (thing we donât recommend, her windows corrupt so we have to reinstall windows)
- Reinstall windows
- Reinstall WoW
- We tried in an old pc from 2010 with 4GB and it worksâŠ
- Wotlk runs good
Her laptop is a hp pavilion 15 notebook, and it runs an Amd high-definition (hd) graphics driver, I know the last time the drivers were updated was in 2015, but that is not the issue. She was able to play without issues before the patch, and how it explains an old pc from 2010 has not the error?
This is an AMD-WoW related issue, something change with the patch implementation.
I was able to fix my Error 132 issue. I am on Windows 10 with an AMD Radeon graphics card. I was getting the error as soon as my characters was entering the world. I had been dealing with âout of dateâ graphics card warning for a long time but everything told me my graphics card was up to date.
I downloaded a program called Driver Easy. It is the only thing that showed me updates for my graphic card. Because I am cheap, I used the free version to download the updates and it took 7 hours. (if you pay itâs faster).
The free program also does not install them for you,. I used this link to manually install myself.
(Canât put link in post- I googled driver easy manual install)
Once this was done, the game loaded no problem and the out of date graphics card warning were gone. I wish you all the best of luck!
Whatever happened at the patch is retail, all the other games work fine, there handshaking from character selection to game world causes amd cards to crash, one would assume blizzard could you know figure out what they changed and add a hot fix but we are over 2 weeks now
What OS version are they on? From what I have read so far, updating the graphics driver manually on a Windows 10 and above fixes the issue.
I was able to finally resolve this by checking AMDâs website and downloading the latest driver for my R5 from them directly. Windows updates donât seem to grab these latest versions so make sure you check the manufacturerâs website and grab the file from there.
1 Like
Iâm already the last updated RMD9 driver. i feel like, we are kinda on the viking ship just waiting for the fire arrow to put us out.
I donât see any hot fix it feels like
After way too many tries, I finally got it to work with my AMD R9. I wound up trying the âlegacy and non-legacyâ version 21.5.2 of the Adrenalin package; the others didnât have much luck, and I was stymied for a bit by the error message that I didnât have a supported graphics card. I had to do a clean uninstall and a couple restarts, but it works!
Also, it works with all my previous addons, including the outdated ones. A couple had to be updated so theyâd display properly (zPerl and SexyMap, in particular), but nothing interfering with the game.
Hey, her OS is windows 10 pro.
As someone mentioned we installed Driver Easy, but after 3 hours of downloading appeared an error.
The driver was trying to download was the âAMD Radeonâą R7 M260â So we download it manually from the AMD website.
It seems that driver was not compatible with the machine, WoW was not able to detect the graphic card so we have to uninstall it and reinstall the drivers directly from HP site.
Same Error #132, so we will wait until blizzard deploy a fix or something
Bumping to the top cause its week 3
I have also been getting a lot of Error 132 crashes, and an occasional crash 138. It was happening consistently Saturday, but I managed to avoid it Sunday/Monday. Thought maybe it went away but it happened again tonight.
Iâll be honest I just spent a ton of money on a brand new computer and set it up less than a week ago. Wow is on a fresh install, no addons right now, I have run updates on everything I could think of. I have removed/moved RAM sticks. I am at my wits end. I need to know if it is my computer or WoW. This thread gives me hope that itâs WoW since i have no issues elsewhere, but I donât know what else to do/try. There doesnât seem to be any specific actions in game that cause it, as it seems random.
Most recent one:
Error #132 (0x85100084) Fatal Exception!
Program D:\World of warcraft_retail_\Wow.exe
ProcessID: 3040
ThreatID: 19688
Exception: ACCESS_VIOLATION
The instruction at â0x00007ffbec8e5716â referenced memory at â0xffffffffffffffffâ
The memory could not be âreadâ
Edit: Everyone here seems to be getting it right on log in. I am able to log in and play, it just happens randomly while playing. So my issue must be different.
Sothe, it appears we have very similar issues.
This error mostly occurs during a loading screen and once in awhile randomly while in game.
I have an Nvidia card.
Windows 11
Nvidia 3080 10g
I9 Raptor Lake
32gb ram
Itâs definitely not a lack of performance hardware and this was fixed after blizzards extended maintenance on 2/1. After their most recent maintenance on 2/6 it started happening again.
This is definitely a blizzard screw up and they just arenât putting enough effort into getting it fixed. Iâve been playing this game since launch and this is by far the worst customer support I have seen.
2 Likes
I just got this error.
Did a nok m+, hearthed, logged out to go to my war and 132 crash
I fixed the issue by swapping what GPU World of Warcraft was using in the settings. This might also help if youâre using a laptop with AMD graphics cards.