Opened up a ticket to talk about it with a dev will update if it goes anywhere
3 Likes
Activision stock on a downward trend because WoW losing tons of subscriptions. PANIC AT THE ACTIVISION
1 Like
Dear Blizzard, Please fix game… ty.
2 Likes
Just had another kernel panic.
MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)
Processor 2.9 GHz Dual-Core Intel Core i5
Memory 8 GB 2133 MHz LPDDR3
Graphics Intel Iris Graphics 550 1536 MB
MacOS Catalina 10.15.2 (19C57)
Was doing the Uldum invasion and had the client froze while fighting the final boss. I waited 30-60 seconds and it came back up. I was able to turn in all of my quests and in town looking through my loot when I had a kernel panic and had to hard restart. Here’s the error:
panic(cpu 0 caller 0xffffff7f85133a76): “Graphics firmware encountered an exception (eip: 0xf179, fault #: 0xd)\n”@skl/sched3/IGGuC.cpp:864
Backtrace (CPU 0), Frame : Return Address
0xffffff912544bb70 : 0xffffff8001b3bb1b
0xffffff912544bbc0 : 0xffffff8001c733e5
0xffffff912544bc00 : 0xffffff8001c64e5e
0xffffff912544bc50 : 0xffffff8001ae2a40
0xffffff912544bc70 : 0xffffff8001b3b207
0xffffff912544bd70 : 0xffffff8001b3b5eb
0xffffff912544bdc0 : 0xffffff80022d24f9
0xffffff912544be30 : 0xffffff7f85133a76
0xffffff912544be80 : 0xffffff7f850ac464
0xffffff912544bee0 : 0xffffff8002240ccd
0xffffff912544bf30 : 0xffffff800223f612
0xffffff912544bf70 : 0xffffff800223eb9c
0xffffff912544bfa0 : 0xffffff8001ae213e
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelSKLGraphics(14.0.3)[72E6B358-5743-3374-8E58-9F7B4CD011B7]@0xffffff7f850aa000->0xffffff7f8519cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f826f7000
dependency: com.apple.iokit.IOSurface(269.6)[640503DC-6033-3EF6-85F4-F48282EF48DD]@0xffffff7f83853000
dependency: com.apple.iokit.IOGraphicsFamily(569.3)[7B5CA52B-0BD1-34AB-BFC9-7D5C3A0DBE7C]@0xffffff7f84137000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.2.8)[9176E894-E24A-36BA-AFDA-0DB11F3F512A]@0xffffff7f841ca000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
19C57
Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide: 0x0000000001800000
Kernel text base: 0xffffff8001a00000
__HIB text base: 0xffffff8001900000
System model name: MacBookPro13,2 (Mac-66E35819EE2D0D05)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 138294176763269
last loaded kext at 80181214961775: >usb.cdc.acm 5.0.0 (addr 0xffffff7f84e87000, size 32768)
last unloaded kext at 80399021006114: >!UAudio 320.49 (addr 0xffffff7f85273000, size 434176)
loaded kexts:
com.sophos.kext.oas 9.9.4
com.sophos.nke.swi 9.9.4
AudioAUUC 1.70
!AGraphicsDevicePolicy 4.5.21
@fileutil 20.036.15
@AGDCPluginDisplayMetrics 4.5.21
!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
!AUpstreamUserClient 3.6.8
!APlatformEnabler 2.7.0d0
AGPM 111.4.1
X86PlatformShim 1.0.0
pmtelemetry 1
!A!ISKLGraphics 14.0.3
@Dont_Steal_Mac_OS_X 7.0.0
!AHDA 283.15
!ABacklight 180.1
!AThunderboltIP 3.1.3
!AHIDALSService 1
eficheck 1
!AEmbeddedOSSupportHost 1
!A!IPCHPMC 2.0.1
AirPort.BrcmNIC 1400.1.1
!A!ISKLGraphicsFramebuffer 14.0.3
!A!ISlowAdaptiveClocking 4.0.0
!AMCCSControl 1.13
@filesystems.autofs 3.0
@filesystems.apfs 1412.61.1
!AVirtIO 1.0
@filesystems.hfs.kext 522.0.9
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
!ATopCaseHIDEventDriver 3420.1
@private.KextAudit 1.0
!ASmartBatteryManager 161.0.0
!AACPIButtons 6.1
!ARTC 2.0
!ASMBIOS 2.1
!AACPIEC 6.1
!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
!AGraphicsControl 4.5.21
|IOAVB!F 800.17
!ASSE 1.0
DspFuncLib 283.15
@kext.OSvKernDSPLib 529
@!AGPUWrangler 4.5.21
!ABacklightExpert 1.1.0
|IONDRVSupport 569.3
!AHDA!C 283.15
|IOHDA!F 283.15
|IO!BHost!CUARTTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
!A!ILpssUARTv1 3.0.60
!A!ILpssUARTCommon 3.0.60
!AOnboardSerial 1.0
|IO80211!F 1200.12.2b1
mDNSOffloadUserClient 1.0.1b8
corecapture 1.0.4
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
!ASMBus!C 1.0.18d1
|IOGraphics!F 569.3
@plugin.IOgPTPPlugin 800.14
|IOEthernetAVB!C 1.1.0
|IOSkywalk!F 1
@kext.triggers 1.0
usb.cdc.ncm 5.0.0
usb.!UiBridge 1.0
usb.cdc 5.0.0
usb.networking 5.0.0
usb.!UHostCompositeDevice 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.6
@filesystems.hfs.encodings.kext 1
!AActuatorDriver 3420.2
!AHIDKeyboard 209
!AHS!BDriver 3420.1
IO!BHIDDriver 7.0.2f4
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
!AMultitouchDriver 3420.2
!AInputDeviceSupport 3420.4
!AHSSPIHIDDriver 58
!AThunderboltDPInAdapter 6.2.4
!AThunderboltDPAdapter!F 6.2.4
!AThunderboltPCIDownAdapter 2.5.2
!AHPM 3.4.4
!A!ILpssI2C!C 3.0.60
!AHSSPISupport 58
!AThunderboltNHI 5.8.1
|IOThunderbolt!F 7.4.7
!A!ILpssSpi!C 3.0.60
!A!ILpssDmac 3.0.60
|IONVMe!F 2.1.0
!A!ILpssGspi 3.0.60
!A!ILpssI2C 3.0.60
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
|IOUSB!F 900.4.2
!AEFINVRAM 2.1
!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
DiskImages 493.0.0
!AFDEKeyStore 28.30
!AEffaceable!S 1.0
!AKeyStore 2
!UTDM 489.60.3
|IOSCSIBlockCommandsDevice 422.0.2
!ACredentialManager 1.0
KernelRelayHost 1
!ASEPManager 1.0.1
IOSlaveProcessor 1
|IOTimeSync!F 800.14
|IONetworking!F 3.4
|IOUSBMass!SDriver 157.40.7
|IOSCSIArchitectureModel!F 422.0.2
|IO!S!F 2.1
|IOUSBHost!F 1.2
!UHostMergeProperties 1.2
usb.!UCommon 1.0
!ABusPower!C 1.0
|CoreAnalytics!F 1
!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|IOReport!F 47
!AACPIPlatform 6.1
!ASMC 3.1.9
watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 1.0
Devs do not respond to tickets. You’ll get a GM at best, but not a dev. This would be the same across any of Blizzard’s games.
1 Like
Any updates from social media, tickets, other forums, anything?
Just to make sure that we’re hitting multiple channels with our complaints (squeaky wheel and all that), I submitted a ticket yesterday and got this response back today:
Ticket:
“I am one of the many Mac users who have found that the 8.3 update has caused many lockups and crashes while playing the game. Please ask the tech team to make this a priority.”
Response:
“Lorrothir
Hey there Brian,
Reading over the request I can totally understand where you’re coming from. Having the game freeze up or crash is totally scary!! Especially with so many other folks having the same issue.
We are currently tracking this issue and are working on a fix. When one is available we should post on this thread [the link was back to this thread].”
Don’t know if this will make anyone happy, but they’re definitely aware of it.
6 Likes
They were aware of it during PTR testing of 8.3 and still pushed out the broken patch.
And yet nobody here has managed to provide evidence of this. Will you prove any different?
1 Like
Looking up the PTR reports but here is one from 24 days ago showing that they have been getting reports on this crash wow issue since before the patch.
120 Pandaren Shaman 10000
Hey, Anomander! We’ve seen some reports over WoWClassic and Catalina freezing/crashing on the 10.15.2 build recently. The following may help, but it seems that this may be tied to some graphic driver issues on Catalina, some situations resulting in kernel panics on Catalina.
Hehe, no Intel/integrated graphics card on a desktop “Mac Pro” so this wouldn’t help as that option isn’t on that computer.
120 Pandaren Shaman 10000
Hey, Anomander! We’ve seen some reports over WoWClassic and Catalina freezing/crashing on the 10.15.2 build recently. The following may help, but it seems that this may be tied to some graphic driver issues on Catalina, some situations resulting in kernel panics on Catalina.
While VMs are not supported nor is rolling back an OS, it may be worth trying to an earlier build of MacOS like Mojave.
I’ll try to update if we have any new workarounds or information available here!
My Mac Pro Specs
- OS: macOS 10.15.2 Catalina - All updated
- CPU: 3.3Ghz 12-Core Xeon
- Video Card: Radeon Pro Vega II - 32GB
- Ram: 32GB
- HD: 2TB SSD
- Monitors: Dual 27" UltraFine LG’s
- Hardwired internet, 1000/40 speeds.
- Settings: Everything is set to 10/Ultra.
- When playing retail, not Classic.
So after finally playing some more after the holidays on my new Mac Pro I am also noticing this behavior. I can play fine for hours, then out of no where the machine seems to lock up. I can tab out of the game, and move my mouse around, move it to the other monitor, but everything seems stuck. All my other apps are frozen, Discord, Twitch, etc. After about 10-30 seconds, the game goes into some type of hyper mode, everything goes super fast, like 10x speed, it seems like it is trying to catch up for a few seconds, then its back to normal, and everything is unfrozen.
I do have a few add-ons installed, but this happens sometimes when doing nothing just chatting with some friends in a city, it also has happened when being in a raid or doing world quests. So I don’t think it is an add-on.
Interesting that two Mac Pros are having the same issue with live and classic. macOS bug? or WoW bug? hmm…
2 Likes
That was from a comment on the forums 24 days ago
1 Like
If you’re a SWTOR player you will understand the scary similarities Activision is having with EA now. Used to this kind of behavior with EA, seems like it will become the norm with Activision/Blizzard now as well. Unfortunate.
1 Like
Ok zoomer we get it your 12
I am currently talking with a game master and he is going to give me an update to where they are at with the fix, I’ll update y’all when I get the answer
7 Likes
At work, so I haven’t been able to post the PTR Mac issues, but this is another forum post where a blue post acknowledges they knew of the issue previous to the patch, stated they had a fix, and then pushed 8.3 on Mac leading to it being unplayable by a hell of a lot of players.
Hey, Chinbo! The crashes are tied to one of our known issues. Our team already has a fix ready, so hopefully this will be resolved soon! There have been some driver issues with AMD cards and Catalina recently though that may contribute to some of the issues like the black screen, which we’ve seen some issues with in our other games. This may require a driver update, but we are tracking these reports and issues on our end. - Hopefully this isn’t the situation and the update will be resolved soon!
1 Like
How long ago was that blue post posted? I just talked to a game master and he said there is no available work around other than installing windows thru bootcamp and the dev team is still researching the bug
December 17, 2019
this is ridiculous…
5 Likes
I’m guessing that was the fix they dropped Tuesday that didn’t work at all
I reported that it stopped after changing directx to 11, but it started happening again after 2 days. Now steadily happening again every few minutes. This is obviously a problem related only to WoW, and only recently started happening on both Mac OS and Windows.