Crashing, freezing, and stuttering after 8.3 [Intel GPUs]

It’s MLK Jr. day here in California, so it’s a holiday. I expect only critical support staff will be in at Blizzard this morning. It appears the fix for you folks is still on track for Tuesday at the earliest.

For what it’s worth, I know what it feels like to not have access to the game. You’ve only been without it for a few days. I’ve been unable to play for 1.5 years because the devs removed critical features many disabled players rely on (exclusive fullscreen mode to prevent app focus from being stolen and the original user interface layout as a built in option so we don’t have to deal with taint due to having to move literally everything around with addons). I’ve missed out on the entire expansion. I was told I wouldn’t even get the six months of game time I had remaining when 8.0 hit given back to me if and when Blizzard ever reversed their decision on the removal of those features. Hell, I’m only still able to play Diablo 3 because it still has exclusive fullscreen mode so the mouse acceleration curve I set up for my deformed arm doesn’t get screwed up due to the game client losing app focus.

Hope you guys get your fix soon. At least, sooner than the fix for me will ever come. :slight_smile:

6 Likes

I love how they said a patch was ready a day ago but they don’t know when it will be pushed.

8 Likes

It isn’t just Mac OS. This is occurring on PC as well. Every few minutes, my PC is freezing as well. The screen flashes black, the entire PC locks up, then comes back a few seconds later. It comes back after about 10 seconds, then does it again. Could be anywhere from 10 minutes to 30 seconds. This only occurs in WoW, no other games affected.

Windows 10
NVIDIA GeForce GTX 760

4 Likes

Damn that sucks. I hope they bring back those features. I wasn’t even aware they removed them. The devs are incompetent morons. We deserve better.

6 Likes

At this point I’m not sure what to say…with so many not able to play effectively…loosing out on resources from the new content, cloak upgrades, etc…even giving free game time wont fix that week (or more as we don’t have an eta for fix)…It’s beyond frustrating for allot of people.
Add to this the two 6 month sub pushes they’ve done in the last three months…to me this just pushes they idea that they do not / will not care. So many have already paid for 6-12 of game time in the last three months, people leaving wont effect their profit margins. Then add on the fact that they know the vast majority of people that have paid for something (with no option of refund) are more likely to suffer through the problems and attempt to play/use the service…Activision/Blizzard really have NO incentive to actually provide a quality product IMHO. Sorry for the bluntness…just the facts.

3 Likes

When just going to the mailbox causes a forced restart… Quality of life is in the toilet in 8.3
panic(cpu 1 caller 0xffffff7f81e3fad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (3120 seconds ago): 313, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (3120 seconds ago): 301, last successful checkin: 120 seconds ago

Backtrace (CPU 1), Frame : Return Address
0xffffff9125473820 : 0xffffff8000d3bb1b
0xffffff9125473870 : 0xffffff8000e733e5
0xffffff91254738b0 : 0xffffff8000e64e5e
0xffffff9125473900 : 0xffffff8000ce2a40
0xffffff9125473920 : 0xffffff8000d3b207
0xffffff9125473a20 : 0xffffff8000d3b5eb
0xffffff9125473a70 : 0xffffff80014d2575
0xffffff9125473ae0 : 0xffffff7f81e3fad5
0xffffff9125473af0 : 0xffffff7f81e3f7e6
0xffffff9125473b10 : 0xffffff8001466fcb
0xffffff9125473b60 : 0xffffff8001470083
0xffffff9125473ca0 : 0xffffff8000e22c22
0xffffff9125473db0 : 0xffffff8000d41998
0xffffff9125473e10 : 0xffffff8000d18625
0xffffff9125473e70 : 0xffffff8000d2f0d5
0xffffff9125473f00 : 0xffffff8000e4b485
0xffffff9125473fa0 : 0xffffff8000ce3226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[EFAA17B9-A62C-30B7-9602-0BB5282EDDD6]@0xffffff7f81e3e000->0xffffff7f81e46fff

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: 0x0000000000a00000
Kernel text base: 0xffffff8000c00000
__HIB text base: 0xffffff8000b00000
System model name: iMac16,2 (Mac-FFE5EF870D7BA81A)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 125542631126660
last loaded kext at 30613999749: >!ATopCaseHIDEventDriver 3420.1 (addr 0xffffff7f840de000, size 61440)
last unloaded kext at 125475005481859: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f8233d000, size 24576)
loaded kexts:

!ATopCaseHIDEventDriver 3420.1
@fileutil 20.036.15
AudioAUUC 1.70
!APlatformEnabler 2.7.0d0
AGPM 111.4.1
X86PlatformShim 1.0.0
@filesystems.autofs 3.0
!AHDA 283.15
!AUpstreamUserClient 3.6.8
!AGraphicsDevicePolicy 4.5.21
@AGDCPluginDisplayMetrics 4.5.21
!AHV 1
|IOUserEthernet 1.0.1
!AMCCSControl 1.13
|IO!BSerialManager 7.0.2f4
pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
!A!ISlowAdaptiveClocking 4.0.0
eficheck 1
|Broadcom!B20703USBTransport 7.0.2f4
!A!IBDWGraphics 14.0.3
!ALPC 3.1
!AThunderboltIP 3.1.3
!A!IBDWGraphicsFramebuffer 14.0.3
!ASMCLMU 212
!AVirtIO 1.0
@filesystems.hfs.kext 522.0.9
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
AirPort.BrcmNIC 1400.1.1
!ASDXC 1.7.7
|!ABCM5701Ethernet 10.3.5
!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
!AGraphicsControl 4.5.21
|IOAVB!F 800.17
!ASSE 1.0
!ASMBus!C 1.0.18d1
@!AGPUWrangler 4.5.21
|IOSlowAdaptiveClocking!F 1.0.0
|Broadcom!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
|IONDRVSupport 569.3
@plugin.IOgPTPPlugin 800.14
!ASMBusPCI 1.0.14d1
!AThunderboltEDMSink 4.2.2
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
!AHDA!C 283.15
|IOGraphics!F 569.3
|IOHDA!F 283.15
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
|IO80211!F 1200.12.2b1
corecapture 1.0.4
|IOSkywalk!F 1
|IOEthernetAVB!C 1.1.0
mDNSOffloadUserClient 1.0.1b8
|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

While it’s definitely possible WoW is a catalyst for your issue, the behaviour described indicates something (in WoW or otherwise) is causing the GPU to reset. Usually that’s a sign of overheating, so double check your system fans are running and that the front/exhaust areas haven’t accumulated dust on the filters and fan blades.

The issue here is different than yours though - this issue causes the machines to either flat out panic or overheat (or overheat leading to a panic as a result).

Since it seems blizzard has failed to act with a sense of urgency in this issue and has allowed the entire first week of the patch to pass by without a care, leaving countless users handicapped in gear and azerite progression, putting us at a severe disadvantage for progress in the new raid, I am unsubbing until shadowlands, if I even come back at all. Take better care of your customers blizzard, this was truly pathetic, no two ways about it.

7 Likes

+1 here for the mac crashing issue. Entering any instance causes immediate freeze and crash. And in before all the “clean your filters, check your graphic card” stuff, brand new 2019 Macbook pro running WoW perfectly before the update. Game time compensation would be nice.

3 Likes

For PC it is just a Directx thing. Easy fix.

2 Likes

can you guys have the courtesy of giving free game time extension till you fix this? cause we met the requirement for running the game, no reasonable expectation to suspect that the game will NOT WORK on Mac OS

No affected player can freaking play. FORGET any dungeon, visions or raid content… all the while when others work on the visions, etc.

Also if you crash in a boss fight before right clicking (not necessarily picking the item in to bag) you get NOTHING

6 Likes

That probably wont happen. Heck, do not be shocked if it isn’t fix tomorrow. They have a lot of fixes to do and have not even spoken about the fact that Macs can’t fully play. To make thing even worse, Shadowlands could very well be just as bad for Mac users. But we will see.

1 Like

I’m a Windows 10 user and I’m having the same issues since the last update (not patch, but update). It freezes all the time since yesterday.

1 Like

They’re probably not even working today since its a holiday. Just left us high and dry for an entire week, possibly more.

1 Like

Ridiculous we all haven’t even heard any kind of update about these issues. Who knows if it’ll even get fixed tomorrow.

This is extremely unprofessional. I expected better, Blizzard.

1 Like

I’m having this same issue here. Jan 20th.
Running a Macbook pro with Catalina.
macOS Catalina 10.15.2
2,7 GHz Intel Core i5 Dual-Core
8 GB 1867 MHz LPDDR3
Intel Iris Plus Graphics 6100 1536 MB

Was fine and well Thursday (Jan 16th)
And I do see there has been Blizz support in this thread so I can only hope it’s figured out soon.
I seem to be getting the Kernel panic (far too long to post) but every time it shuts down it’s about the same.
panic(cpu 2 caller 0xffffff7f9363fad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

service: com.apple.logd, total successful checkins since load (10700 seconds ago): 1071, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since load (10670 seconds ago): 1055, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address

0xffffff8120833820 : 0xffffff801253bb1b

Seems I can stand around Stormwind and use the AH but that’s about it any quest line I begin just give me the swirling rainbow of death then shuts me down.

1 Like

I’m having the same problem which made me lost the quest “Servant of N’zoth” TWICE. I’m playing on a macbook pro late 2016 with touchbar.

1 Like

They are clearly at home today and Sunday. No reason to work when you can go home and let it all wait until next week. It is sad. If it was a pay system thing it would have been done that day.

2 Likes

The swirling rainbow of death strikes again

1 Like

Yeah I’ve just stopped attempting to play…

2 Likes