Hi trying to launch wow classic in prep for season of mastery and it is a fresh install on mac - won’t load at all, goes straight to blizzard error. Very frustrating. Anyone else experiencing this issue or aware of a fix?
8 Likes
Experiencing as well for several days now, reinstalling does not help
5 Likes
I am also experiencing this error. I really want to play SOM but it crashes every time I hit the “Play” button.
I have tried allowing full access on the computer, running the executable, and uninstall/reinstall/reboots. I always get the same “WoW has experienced an unknown error”.
Running the game on a 2015 mac book.
I can run TBCC, retail, and was able to run the original classic without any problems.
3 Likes
Experiencing this issue as well. So Frustrating as i havent been able to play the launch of Season of Mastery!!! 
i feel like ive tried everything at this point, nothing seems to help.
1 Like
Im experiencing the same issue, away from home and only able to play on my macbook. Missed SoM launch. Very upset.
I’ve been having the same problem, I can log into retail and burning crusade classic WoW but whenever I try and start the application for World of Warcraft Classic my game doesn’t even reach the login screen, I just get an error that won’t seem to go away.
Join the club. I assume you all have AMD GPUs?
If you have dual cards, you could try changing this line in your Config.wtf
SET gxAdapter “AMD Radeon Pro 5300M”
to
SET gxAdapter “Intel(R) UHD Graphics 630”
Or whatever your non-AMD adapter is. I can at least get into the game now, however slow and ugly it is, lol.
1 Like
I’m having this issue as well. TBC runs fine however if I try to run classic for SOM it totally freezes my mac requiring a hard reset by holding down the power button.
2019 Macbook Pro
Catalina 10.15.7
AMD Radeon Pro 5500M
2 Likes
Hey there,
Thanks for these reports. So far it’s looking like these crashes are all related to interactions with the metal API. For this type of crash I normally recommend resetting the game files and updating the device operating system.
If it’s still crashing after both of those items, and you are getting error 134 on wow classic, please reply with the following:
- OS Version
- Processor
- Graphics device
I do hope the info helps. Let us know how things go!
I only had crashes on classic with AMD gpu if I used regular graphics engine. if I used Prism issues went away. but others haven’t reported success with this so don’t know core cause.
SET GxPrismEnabled "2"
added to config to try it. maybe it’ll work for you maybe it won’t.
So are we supposed to do sudo chmods and data file mods for ever? Is that the plan?
Another Mac user voicing the same issue/frustration/confusion. Tried the uninstal/reinstal, using battle.net’s “scan and repair” feature now. Tried to avoid opening crowds cuz I know my machine isnt the most powerful, its a mac after all, but now it seems im totally locked out. Thought i could just pop in breifly and get started today…now approaching hour 3 of trouble shooting 
Hey y’all,
Just as an update, the issue has been identified by QA/Dev and a fix is on the way. I don’t have an ETA for when it will go live but once I get more info I’ll update this thread.
Cheers!
4 Likes
Hi @Kalydraydis, just wanted to update you on the impacts the inaction is having.
I’ve been trying to get answers from customer support for two weeks on this issue. Blizzard has assigned 7 different tech specialists or game masters to respond in substantially the same way: check this form post for updates, i.e., the one I’m now posting on.
There hasn’t been an update for 10 days. Can you please provide an update? I’ve requested a subscription refund, which was handled near-instantly. That was a far cry from the efforts to handle the problem itself.
Hey Trillville,
This thread has been quiet for about 10 days and the initial issue that was being investigated has since been hotfixed (recently) and should no longer be causing this specific crash.
If you are still experiencing a crash at the time of this response, we recommend submitting a new (or reopening by replying to an existing support case) ticket with fresh system reports and an description of exactly what you are encountering. Codes, messages crash IDs etc… screenshots will also help.
This issue isn’t fixed. Choosing the Radeon Pro 5300M still completely crashes WoW Classic.
1 Like
Confirming Carlthuzad. It is happening with equal frequency as before the ‘hotfix.’ Can someone please look into or find at least a temporary work-around?
I support this thread. The exception is always related to the graphics library, even across versions in the past few months, and MacOS updates. Also seems related to some in-game default dialogue boxes opening or closing at times.
Thread 0x00000103 [Stack Base: 0x00007FFEEF8B9000 Used Space: 2816/67104768 bytes]
0 0x00007FFF6DF54A6B “com.apple.AMDMTLBronzeDriver” -[BronzeMtlBlitCmdEncoder resolveCounters:inRange:destinationBuffer:destinationOffset:] + 2417
<Graphics.VendorID> 0x1002
<Graphics.PCIIdentifier> VID=0x1002,DID=0x679E,REV=0x00,SSID=0x00000125
Graphics.DeviceID 0x679E
Graphics.DeviceName AMD Radeon HD - FirePro D500
<Graphics.VideoMemory> 3072 MB
I have tried several times to submit a ticket on this in the last few days and to no avail. It just. tells me that I cannot submit a ticket. Can Someone please get back to us to let us know if it’s still being worked on please?
You can’t submit this ticket.
An error has occurred. This may be a temporary error, so please try again later.
This is all I get every time I try.