Is there some way we can get a refund for our wasted subscription before we eject ourselves from this travesty?
4 Likes
Id doubt that, but agree that Blizz should do something. Particularly with how crippling the bug is. The game is literally unplayable.
2 Likes
I just contacted Blizzard and asked to have this rectified by at least giving us a refund for the subscription we wasted over the past weeks. If you attach a photo of the bug happening and your system details, then there’s no reason why they can’t
3 Likes
2 freeze/forced restarts within 5 minutes of each other this afternoon in the Vale, so the first of the bug reports was wiped out… Also lost 2 vessels trying to do Horrific Visions when the game froze, both times on the Cathedral steps… A low level (27) toon in my guild also having a rough time with his Mac crashing, so this mess permeates the game with misery…
panic(cpu 1 caller 0xffffff7f91a3fad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (690 seconds ago): 70, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (630 seconds ago): 51, last successful checkin: 120 seconds ago
Backtrace (CPU 1), Frame : Return Address
0xffffff912130b820 : 0xffffff801093bb1b
0xffffff912130b870 : 0xffffff8010a733e5
0xffffff912130b8b0 : 0xffffff8010a64e5e
0xffffff912130b900 : 0xffffff80108e2a40
0xffffff912130b920 : 0xffffff801093b207
0xffffff912130ba20 : 0xffffff801093b5eb
0xffffff912130ba70 : 0xffffff80110d2575
0xffffff912130bae0 : 0xffffff7f91a3fad5
0xffffff912130baf0 : 0xffffff7f91a3f7e6
0xffffff912130bb10 : 0xffffff8011066fcb
0xffffff912130bb60 : 0xffffff8011070083
0xffffff912130bca0 : 0xffffff8010a22c22
0xffffff912130bdb0 : 0xffffff8010941998
0xffffff912130be10 : 0xffffff8010918625
0xffffff912130be70 : 0xffffff801092f0d5
0xffffff912130bf00 : 0xffffff8010a4b485
0xffffff912130bfa0 : 0xffffff80108e3226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[EFAA17B9-A62C-30B7-9602-0BB5282EDDD6]@0xffffff7f91a3e000->0xffffff7f91a46fff
BSD process name corresponding to current thread: watchdogd
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: 0x0000000010600000
Kernel text base: 0xffffff8010800000
__HIB text base: 0xffffff8010700000
System model name: iMac16,2 (Mac-FFE5EF870D7BA81A)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 695835268709
last loaded kext at 40318540710: >!ATopCaseHIDEventDriver 3420.1 (addr 0xffffff7f93cde000, size 61440)
last unloaded kext at 635384712162: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f91f3d000, size 24576)
loaded kexts:
!ATopCaseHIDEventDriver 3420.1
@fileutil 20.036.15
AudioAUUC 1.70
!APlatformEnabler 2.7.0d0
X86PlatformShim 1.0.0
AGPM 111.4.1
@filesystems.autofs 3.0
!AUpstreamUserClient 3.6.8
!AHDA 283.15
|Broadcom!B20703USBTransport 7.0.2f4
!AThunderboltIP 3.1.3
!AGraphicsDevicePolicy 4.5.21
!A!IBDWGraphics 14.0.3
@AGDCPluginDisplayMetrics 4.5.21
eficheck 1
!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
!ASMCLMU 212
!A!IBDWGraphicsFramebuffer 14.0.3
!AMCCSControl 1.13
!A!ISlowAdaptiveClocking 4.0.0
!ALPC 3.1
!AVirtIO 1.0
@filesystems.hfs.kext 522.0.9
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
!ASDXC 1.7.7
|!ABCM5701Ethernet 10.3.5
AirPort.BrcmNIC 1400.1.1
!AAHCIPort 341.0.2
@filesystems.apfs 1412.61.1
@private.KextAudit 1.0
!ARTC 2.0
!AACPIButtons 6.1
!AHPET 1.8
!ASMBIOS 2.1
!AACPIEC 6.1
!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
!AMultitouchDriver 3420.2
!AInputDeviceSupport 3420.4
!AHS!BDriver 3420.1
IO!BHIDDriver 7.0.2f4
!AHIDKeyboard 209
@kext.triggers 1.0
DspFuncLib 283.15
@kext.OSvKernDSPLib 529
!AHDA!C 283.15
|IOHDA!F 283.15
|Broadcom!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
!AThunderboltEDMSink 4.2.2
!AGraphicsControl 4.5.21
|IOAVB!F 800.17
!ASSE 1.0
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
X86PlatformPlugin 1.0.0
@!AGPUWrangler 4.5.21
|IONDRVSupport 569.3
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
!ASMBus!C 1.0.18d1
|IOGraphics!F 569.3
|IOSlowAdaptiveClocking!F 1.0.0
IOPlatformPlugin!F 6.0.0d8
!ASMBusPCI 1.0.14d1
@plugin.IOgPTPPlugin 800.14
usb.!UHub 1.2
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
|IOAHCIBlock!S 316.40.3
|IOEthernetAVB!C 1.1.0
|IO80211!F 1200.12.2b1
mDNSOffloadUserClient 1.0.1b8
corecapture 1.0.4
|IOSkywalk!F 1
|IOAHCI!F 290.0.1
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
!AThunderboltDPOutAdapter 6.2.4
!AThunderboltDPInAdapter 6.2.4
!AThunderboltDPAdapter!F 6.2.4
!AThunderboltPCIDownAdapter 2.5.2
!AThunderboltNHI 5.8.1
|IOThunderbolt!F 7.4.7
|IONVMe!F 2.1.0
|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
|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
|IOTimeSync!F 800.14
|IONetworking!F 3.4
|IOReport!F 47
!AACPIPlatform 6.1
!ASMC 3.1.9
watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
I cancelled my account because the game is not playable. I also asked for and received a refund, citing this issue/post. The issue is well documented, and is referenced in the official “known issues” for the expansion.
Can you show me where it is listed in the known issues? Because I cannot find anything citing what you just said.
Whether or not it’s on there let’s just hope blizzard didn’t didn’t quit on working on the fix.
3 Likes
Are most of you playing on the iGPU or a DGPU? Playing on the iGPU even on the Core-i9 MacBooks is not a terrific idea, even in Windows.
A lot of people are on machines that have no discrete GPU and are stuck with the IGP. That’s one of the bigger problems. Apple laptops with discrete GPUs cost a lot more than the lower tier models with only IGPs. The Mac Tax is quite real and makes a difference in which models people can afford a lot of the time. 
1 Like
This is true of Windows laptops too. An ASUS ROG “gaming” laptop with anything above an iGPU will cost you upwards of $2200.
1 Like
Downloaded new patch. Login screen background error in a grey/blue box
Storm_error_wow_name_string
Error #137 (0x85100089)
We really are their QA dept now and they are just pushing out trash. Blizzard used to stand for quality and it wouldn’t ship until it was polished and perfect. I already won’t but Activision games with their ship now fix whenever they get to it. Lumping Blizzard I’m with that model now. Sad to know such a great company no longer cares. Time to find a game that actually works.
Tfw no blue post for 3 days kekw
6 Likes
Agreed, There should be Blue updating us every couple of days. I have 2 accounts active and am really on the verge of cancelling.
5 Likes
During testing of 8.3 the issues was reported, Still they pushed it out because they had a set date to do so and figured it would not matter.
Jan 14th. 8.3 drops Tuesday, reported issues. Blizzard started take information but did not look at it in their systems in hopes few had issues.
Jan. 15th. Wed, tons more report issue and Blizzard gets to work in late afternoon.
Jan. 16th. Thursday, they are able to see the issue and create a fix.
Jan 18th. Saturday, issue is reported fixed by team and was tested. They report they have a fix, just do not know when to apply the fix.
Jan 21th. Tuesday, one week later. After other work in the late day they drop fix. After users complain it is taking too long. The fix does not work.
Jan. 22nd. They report they understand then stop speaking because it is better to blow it off and move on.
Jan. 26th. Not one word from Blizzard on a fix, since the 22nd. More players reporting issues.
8 Likes
I have at this point deemed the freezings to be a feature of 8.3. To test wows users to see if they are insane enough to play because my god this is bad. The freezing is so bad my windowed “work around” now just [blacks out the game screen and again freezes my MacBook
Lookup markmetlerjr on imgur since I can’t post a link here…
2 Likes
I got a new error message while I was completely frozen in an island.
1C9BEEA8-8EF8-4AF0-B98F-5EF400D54953
Please fix and communicate with us about the issue with the intel graphics cards on Mac.
I can’t even be in vale or this happens today imgur link /0GMVNZu.jpg
Yeah, I just checked out. Lucky, since my sub is up tomorrow. Gameplay is debilitating and paying $15/mo to do nothing makes no sense
I am going insane. I crashed on a horrific vision. 8.3 is going to drive me crazy. They promoted this patch correctly.
6 Likes
Battle for Azeroth 8.3 - Info & Known Issues This page, search for ‘mac’.