[Main Thread] Crashes on launch after maintenance Jan 24th

[Errowen-whitemane]

Aetherni - have you tried restarting your computer since downloading the new patch? Omegal said some people may have a corrupt cache that needs to be cleared by a restart.

You are also on Big Sur though which is not 100% fixed.

[Deflector-benediction]

It cries out in pain! CRASH

[Tiapriestess-whisperwind (Tiapriestess)]

@Mineva-bloodsail-buccaneers

This isn’t to take a jab at all of the Mac users, but you’re not the only ones with this issue. I’m running Windows 10 with everything updated (automatically) that I can, and I still can’t log in to the game past the loading screen. I was, however, able to create a new character and test if I could load in that way but it crashed at the crossover between load screen and cinematic.

This error is a catchall one, and it’s been triggered for numerous people for a lot of reasons. If you look back on the forums, you’ll see that there are a lot of posts with this exact error that started with Dragonflight.

The error in this thread is not part of the catch-all. It’s literally triggered by a specific API crash with specific GPUs when using a specific API between the two available (Metal and Metal-Legacy). It is not a Windows crash and is most assuredly specific to the macOS client.

[Baigimbor-blackhand]

Version 10.0.5.47871 - No joy here on iMac Ventura 13.1 or MacBook Pro Ventura 13.2. Now gets to the connecting screen, stalls for a bit, and goes black then a crash. E03C8DDF-832E-486D-B1F4-E305802F55DD.
Oddly the laptop and iMac are on different versions. Rebooted also per previous thoughts but that had no affect.

iMac:
Chipset Model: NVIDIA GeForce GTX 780M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 4 GB
Vendor: NVIDIA (0x10de)
Device ID: 0x119e
Revision ID: 0x00a2
ROM Revision: 3782
Metal Support: Metal 2

[Eemerald-blackhand]

Hello all, Updated to 10.0.5.47871 saw opening Cinematic, connecting, crash.
Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro11,3
Processor Name: Quad-Core Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Hyper-Threading Technology: Enabled
Memory: 16 GB
System Firmware Version: 474.0.0.0.0
SMC Version (system): 2.19f12
Hardware UUID: 7EF3BF05-171D-5380-8FD1-982FBA477038
Provisioning UDID: 7EF3BF05-171D-5380-8FD1-982FBA477038

Crash code from Blizzard: A37201DB-77A0-4539-A1FF-6196ED4FBEA8

Thank you Omegal and Rommax, you guys are my heroes.

[Tiapriestess-whisperwind (Tiapriestess)]

@Baigimbor-blackhand

Version 10.0.5.47871 - No joy here on iMac Ventura 13.1 or MacBook Pro Ventura 13.2. Now gets to the connecting screen, stalls for a bit, and goes black then a crash. E03C8DDF-832E-486D-B1F4-E305802F55DD.
Oddly the laptop and iMac are on different versions. Rebooted also per previous thoughts but that had no affect.

iMac:
Chipset Model: NVIDIA GeForce GTX 780M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 4 GB
Vendor: NVIDIA (0x10de)
Device ID: 0x119e
Revision ID: 0x00a2
ROM Revision: 3782
Metal Support: Metal 2

You were warned against hacking the OS onto a system that it wasn’t intended to run on. None of the nVidia GPU machines are able to update to Ventura natively as there are no nVidia GPU drivers past Big Sur, and running Metal-Legacy under Ventura also produces a wicked memory leak.

[Baigimbor-blackhand]

I know about the memory leak. A simple reboot every week or two is not a difficult compromise. These systems worked perfectly on Wow prior to 10.0.5 PLUS the problem is so widespread that using the OpenCore legacy patcher is clearly not related at all to the WoW bug.

[Matmotard-area-52]

just restarted my mac and game is working. I have mac os catalina hope this works for you all

[Tiapriestess-whisperwind (Tiapriestess)]

@Baigimbor-blackhand

I know about the memory leak. A simple reboot every week or two is not a difficult compromise. These systems worked perfectly on Wow prior to 10.0.5 PLUS the problem is so widespread that using the OpenCore legacy patcher is clearly not related at all to the WoW bug.

You’re using the Metal-Legacy API in Ventura. You might find the reboots “workable”, but the fact is due to the use of the OpenCore legacy patcher, they can’t use your crash data for anything useful given that those drivers have to use both drivers that aren’t present in the OS you are on and because you’re using a render path from an already currently problematic OS version (Big Sur).

You might have thought you were being smart, but the reality is, you weren’t. I’m trying to find a nicer way of saying it, but in the interest of preventing anyone from following in your footsteps I’m afraid I’m going to have to be to the point on this one.

Had you remained on Big Sur yesterday’s fix would likely have allowed you to play once more. At this point all you can do is hope that the next patch lets you play again.

[Kirppy-sulfuras]

Alas, Still broken…

[Alastaer-lothar]

How did they not realize non intel GPUs running 11.x.x were affected? I can see a bunch including myself that posted this information last Tuesday.

[Alastaer-lothar]

Same results as Groz

Model: Imac (Late 2014)
Processor: 4GHz Quad-Core Intel Core i7
Memory: 32 GB 1600 MHz DDR3
GPU: AMD Radoen R9 M295X 4 GB
OS: 11.7.3 (can’t upgrade further)

Error Code:
FECDCFFD-9353-4B6D-BF98-CEF6CB45AA63

[Tiapriestess-whisperwind (Tiapriestess)]

@Alastaer-lothar

How did they not realize non intel GPUs running 11.x.x were affected? I can see a bunch including myself that posted this information last Tuesday.

Omegal explained how:

@Omegal-whisperwind

Thanks for all info, based on info, the updated fix (that will go out tuesday and no sooner unfortunately) will fix all remaining crashing users. In meanwhile, below is state of crash vs no crash

Again, It’s fixed for following users
ANYONE (regardless of hardware) on macOS 13, macOS 10.14, macOS 10.15.
Anyone with an intel GPU on macOS 11

People still crashing and need to wait for new fix:
amd GPUs on macOS 11.
intel and amd gpus on macOS 12

For anyone curious why who the fix was applied to was cherry picked and not just applied to everyone. Because the fix is disabling some features/graphics visuals. It’s reverting to an old code path that doesn’t work with new stuff in 10.0.5. As such, they tried to scope the fix to just affected users, but missed some configurations. That scope will be increased but again they want to avoid running old path on machines that don’t need to.

The gist is they thought they had all affected users covered by the first bugfix patch. Based on your (the players’) reports, they quickly realized that was an error/oversight and began the process of putting forth a more broadly applied fix. Unfortunately due to the way Blizzard’s client push schedules work (typically Tuesday and Friday), it is unlikely the second, more encompassing fix gets pushed live until…Tuesday.

I know it’s not what those still affected want to hear but at least Rommax himself was honest about it:

@Rommax-1333

The fix that went out today put clients running on macOS 10.14, 10.15 and Intel GPUs on macOS 11 onto a fallback/legacy code path to solve the crash issues. Based on the feedback here, there’s another hotfix queued up to expand the fallback path to include macOS 12 and all Intel GPUs regardless of macOS version. Unfortunately, for technical reasons, it won’t be possible to get this new hotfix build deployed before Tuesday.

[Andrei-korialstrasz]

I’m just hoping they recognize that all of the categories they said were included in the fix last night but weren’t will need to be added to the Tuesday update. Otherwise, there will still be a subset like mine (Big Sur, Intel, 11.x) that still crashes even after Tuesday.

[Valente-atiesh]

What is ABK doing in the way of compensation, especially the loss of knowledge points we could ave gained through weeklies, let alone through grinding?

[Tiapriestess-whisperwind (Tiapriestess)]

@Valente-atiesh

What is ABK doing in the way of compensation

[Katly-old-blanchy]

Agree - thank you for saying this…I am on Big Sur 11.7.3, Intel GPU so from my (admittedly non-technical) read of the thread, it seems WoW should be working again for me. Alas, I still get this error after a momentary black screen: E1F66998-47C3-4F1D-ADF6-5F43CA115A54

I am still showing Ver: 10.0.5.47849 - no push to 47871 is happening (even after rebooting). Crossing my fingers for Tuesday!

Additional specs, if useful. MacBook Pro Late 2013, 2.4GHz Dual Intel Core i5, Intel Iris 1536MB.

Thank you!

[Mamakazi-anvilmar]

An update is requested in battlenet for my now working setup (47871) - i’m a little afraid of updating now - at least over the weekend

[Tiapriestess-whisperwind (Tiapriestess)]

As long as you can launch the game manually from its install location (i.e. not via the Battle.net app), you’re fine. It only requires updating via the Battle.net app if you encounter the Incompatible realms upon logging in.

[Dysnomia-emerald-dream]

Anybody else unable to log in after the latest patch - On a Mac, crashes before login screen pops up.

Going through reinstall process now.