What gets me is that I have an AMD system that was running perfectly before the patch, and all of a sudden is crashing with error #132 after the patch. It still runs fine for everything other than WoW. So while I understand that it’s an older system, clearly something changed on Wow’s end that took my system from fine to unplayable.
7 Likes
I guess Their update screwing everything it’s our fault— because we are either non-gamer(won’t waste money to play a videogame for 30days lol) and others poor/hard economic situation… 
As I said a Du Soleil version of a company…
hope you use the 15 you’re about to steel from me to pay a decent support, and devs that are not liars… not liars and clowns, because you could get better people for 7, yeah…that cheap is your circus.
Hope yall have a good one, and for the people that have been playing this for years, maybe this happened so you can move on to better and bigger things…not other videogame 
2 Likes
My brothers graphic card is AMD , two gens older than mine, his game has been fine since patch , mine not. it is a joke that blizz wants to blame this on us and not take any accountability , or actively help the little fanbase it has left. One step forward with a good xpac finally , two steps back with counterproductive measures to retain player base.
1 Like
DD6A87F5-C79B-40FD-9EFB-8C26FD510E8D - day 7 no resolve, get to end of handshaking end of blue bar then crash. fatal error.
please resolve
Good luck guys and gals, I’m out. They are still blaming customers. Looking at support forum seems to me like some severe coding issues going on over at blizz hq. Its not just these people who cannont connect, you have massive amounts of people complaining about being randomly disconnected and horrible fps issues and many more similar issues…and heaven forbid you use one of the disconnect bugged abilities. All of these issues were practically non existant before patch. But its definitely something wrong with all of these customers setups…not blizzards kindergarten level developers…
4 Likes
DF has been crap from a performance perspective- I know because I run 8 clients at once…
1 Like
The most I’ve run is 69 clients, but this was like a 420 months ago.
Alright. After a last ditch effort to fix my game, I finally got it to work. I had to manually install the driver update like 3 times, but I finally got it to work. Now I’m feeling sick because I’m not used to the graphics driver and I just came back from my graveyard shift so goodnight.
DF is quite a bit more resource intensive.
Yes but the point is that it was working perfectly fine until the Jan.24th patch and then it wasn’t.
Personally, I barely had any lag at all except occasionally in SW, let alone all the other problems that other customers have been complaining about and now I can’t get past the character screen to even check it out. I had expected major lag issues in DF but nope, so basically the programmers changed some command that locked out a lot of the “outdated” graphics systems so they could provide some extra sparkles…
1 Like
Same here. No consistent lag or graphics slowdowns; I had some stuttering during Winter Veil when a million people were all trying to kill the Greench at once, and sometimes in the early days of the expansion when certain Valdrakken spots were really crowded, but that was it. Then, immediately after the January 24 patch, I was unable to even get past the loading screen. And as others have noted, it happens precisely at the end of the loading bar filling up, which indicates (at least to my amateur mind) some sort of problem with the handshake, not strictly an insufficient graphics card.
1 Like
Everytime I play now, I get vertigo due to the supposed graphic “upgrade” I took on with switching out laptops & updating drivers. Played yesterday but I do not want to play today. Error 132 now happens randomly and dragonriding causes DCs. I’m done.
I don’t understand how they can’t know what the problem is, if this happened due to that patch, how can they not know what they put in and what they didn’t, I get a fatal error on my ryzen 7 and gtx 1070, and changing to my rx 460 too, when before that patch it worked very well in both, even in the minimum requirements it puts windows 7, so how is it possible that they mention incompatibilities? Or that they buy the game and pay a subscription to later realize that it is not compatible? this is sad.
1 Like
It’s a bit misleading.
They did something to the game which caused an incompatibility with some of the older graphics drivers.
Yes, the minimum OS requirement is Windows 7. But only if you have a graphics driver that is compatible with whatever they changed in patch 10.0.5.
Logged in for like 15 mins (the patch deleted all my WeakAuras so I logged cause I felt a headache coming on). No issues yet. Fingers crossed.
For example, an rx 460 with windows 8.1 has its last update in 2017, in theory according to the minimum requirements, it would be compatible, As a question, what are the specifications of your pc and so?
Mine is Windows 10, but my AMD R9 360 driver is no longer being updated since June 2022. So if something like this happens again, I’m completely out of luck unless I get a new PC.
I think Blizzard nuked AMD R9 series for good
1 Like
I fixed my issue by installing the last update (June 2022) for my AMD R9 360 driver.
May have something to do with how recently the manufacturer updated the specific drivers.
1 Like
I want to rub a little salt into the wound. I am running a 15+ year old Dell with 15+ year old cards and Win 7 and it works slow but fine—However—
New computer 1 having the 132 issue with nothing that can fix it and
New computer 2 having the new graphics issue with nothing to fix, either.
Both new crashes happened at the exact same time on two different computers on two different accounts after a random update outside the usual Tuesday updates. The unannounced update came through on Monday night. My daughter and I have lost 2 days now attempting every fix the internet can think of. We have headaches now. Maybe we should try asking a Ouija board next.
3 Likes
So, my gf was able to log in and LOAD a character finally with getting error 132! Updated my gf’s old AMD R7 driver and it worked–but also as I logged on there was another WoW update, so who knows which one made it work. Hope this might help someone else.