Intel Mac Wow Crashes on launch after dragonflight pre-patch

When I launch World of Warcraft from battle.net launcher, it crashes, and doesn’t even get to the start screen. This has only started happening after yesterday’s dragonflight pre-patch.

5 Likes

Same problem. I tried reinstalling the entire game, I tried scanning the installation, I tried restarting my computer. Nothing. Pre-patch really broke everything.

2 Likes

The same error occurred to me after the Dragonflight pre-patch om both my Macbook Pro and iMac. I am getting this Report ID: 975A0D94-2A18-4EA7-BCB0-9BBA7843FA97

1 Like

I did the wow repair, reinstalled wow, and all the OS updates. Still nothing

I had the same experience on my macbook pro with intel chip, (os 10.15.7) everything was working fine, then when prepatch loaded and i pressed the play button dragonflight crashed.

i then ran the scan and repair on the launcher, then ran first aid on my mac, then i removed all the addon files, then tried again.

it crashed again

1 Like

I have the same issue, pls blizzard dont make me go back to overwatch

Same issue here, european side

Same here since Dragonflight pre-patch on Mac Pro OS 11.7.1

Report ID : 378495DB-BDEC-4BD1-BEFB-BF9EA5E0B8A0

Just can’t believe i have wait so long for such a result… Am i having fun?

Having the same issue as well :(…

2 complete uninstalls (deleted from disc too) and reinstalls later and still…
072B5CE6-A72F-4BE0-8117-B66E9AFB35A0
MacOS 12.6 on Mac Pro 2013 6 core Xeon 64 GB ram AMD AMD FirePro D500 3 GB GPU
Worked just fine before the pre-patch…

I am also receiving this issue. Exactly as described above, installed the pre-patch and then my previously working client crashes to desktop. I have tried deleting all files, WTF and doing a full re-install.

Report ID:
1B62CD73-0AC0-401D-863F-8ACB98D01422

MacOS 10.15 on Intel Mac Pro 2012

Looking at the error file, it’s definitely something to do with Intel processing:

Exception: EXC_BAD_INSTRUCTION
Description: EXC_I386_INVOP

/26 20:57:11.710 LogOpen
10/26 20:57:11.710 World of Warcraft Retail x86_64 10.0.0.46313
10/26 20:57:11.710 macOS 12.6.1 (21G217) x86_64
10/26 20:57:11.710
10/26 20:57:11.710 Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz | Sockets:1 Cores:6 Threads:12
10/26 20:57:11.710 64.0 GB System Memory
10/26 20:57:11.710 On AC Power - Battery Not Present
10/26 20:57:11.734 Adapter 0: “AMD Radeon HD - FirePro D500” family:GCN1 type:Discrete vendor:0x1002 device:0x679e driver(0x0) location:2
10/26 20:57:11.734 Monitor 0 “C32F391” Size(1920x1080) Pos(0, 0)
10/26 20:57:11.734 Monitor 1 “(null)” Size(1920x1080) Pos(0, -1080)
10/26 20:57:11.734 Adapter 1: “AMD Radeon HD - FirePro D500” family:GCN1 type:Discrete vendor:0x1002 device:0x679e driver(0x0) location:1
10/26 20:57:11.734 Monitor 0 “C32F391” Size(1920x1080) Pos(0, 0)
10/26 20:57:11.734 Monitor 1 “(null)” Size(1920x1080) Pos(0, -1080)
10/26 20:57:11.734 AutoDetect: hwDetect = 1
10/26 20:57:11.835 Choosing gpu with monitor attached: “AMD Radeon HD - FirePro D500 [2]”
10/26 20:57:13.681 Error Loading Shader: 3186452
10/26 20:57:13.682 NotifyOnDeviceCreate
10/26 20:57:13.684 Metal Legacy Device Create Successful
10/26 20:57:13.684 Using shader family mtl_1_1
10/26 20:57:13.684 No
10/26 20:57:13.684 Detected Graphics Defaults: 2 (CPU = 3, GPU = 2, MEM = 7) WindowSize: 1920x1080
10/26 20:57:13.684 GxLowLatencyMode: None
10/26 20:57:13.813 Render Settings Changed. New Render Size: 1920x1080
10/26 20:57:14.830 Render Settings Changed
10/26 20:57:15.130 Crash Summary: ERROR #134 (0x85100086)

Possible workaround:

This worked for me. Thanks!

same issue on my imac since the pre patch. i get this error 4786E060-0713-45E6-A805-E856E26D4E33. ive uninstalled the blizzard app, ran wow repair, deleted cache folders and still nothing.

Try the workaround Blizzard posted in the thread I linked above

Tried the workaround but it still didn’t work…

1 Like

im having this error everytime i try to get on to the pre-launch it gives a number and i dont know what to do im Dkweasel of WindRunner battle tag# 1648 please help email or something rdianasic@aol.com

tried the work around and it worked, thanks !