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

We’re going on nearly four weeks now, Blizzard working on it is a bit of a stretch at this point.

7 Likes

Didn’t realize some folks Macs are getting permanently damaged from this, that freaks me out. There is no way I will be playing WoW again until it’s 100% confirmed to be fixed.

7 Likes

With one left on game time and the game removed, I just wanted to say something. Those who say you will be back when fixed are crazy. This company has shown that they just don’t care about anything any more. A pay to win game for phones, Warcraft 3 is a mess, and then 8.3 issues they knew about before hand. They don’t clearly don’t care about the gamers. To say you will come back no matter how long it takes allows them to get away with this kind of stuff. It is not worth the issues or the money. heck, we pay for this and they suspend players for complaining. I just don’t see a point anymore. It is all for nothing. It is just yelling into a void. Iowa is doing and better job than Blizzard. For seven years I left then came back in Nov of 19 just to have this happen. They have even said, they will not refund or doing anything to make up for the issues because we were able to log in and play. Play, to them means walk around in the world, not matter how well or long. I have emails from them to prove that they even said that. They don’t care. The CS team will tell you they care, but do not buy it. Be smart move on people. Its four weeks and still you each sit here hoping. Join those of us who are officially done. I know, all pointless, but if I can save on person the time it took to write all this was worth it. Good bye blizzard, and the rest of you. I wish you all the best.

10 Likes

I’m basically having an issue anytime there are too many things going on.

Pretty frustrating. Will probably not renew my subscription unless this is promptly fixed. There’s lots of options out there for MMORPG and WoW definitely has the best community. Right now they don’t have a functional game though… Sad…

3 Likes

Class action law-suit for false advertising that it’s Mac compatible? Anyone willing to start up a Go-Fund me to pay for a lawyers retainer?

6 Likes

Guess what?! Game crashed and forced a restart of my iMac, something neither new nor different…! Oh yeah, another error report to add to the pile! Blizzard are you even looking at these any more, or just hoping we will go away so you can focus on glitchy AH and mail…

What: Soulbinder (never did work right, horrendous lagfest pre 8.3)
Where: Naz
who: holy pal
when: about 4:30 realm/CST

panic(cpu 1 caller 0xffffff7f8dcf0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (15190 seconds ago): 1520, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (15190 seconds ago): 1508, last successful checkin: 120 seconds ago

Backtrace (CPU 1), Frame : Return Address
0xffffff91300b3820 : 0xffffff800d13bb2b
0xffffff91300b3870 : 0xffffff800d2734d5
0xffffff91300b38b0 : 0xffffff800d264f4e
0xffffff91300b3900 : 0xffffff800d0e2a40
0xffffff91300b3920 : 0xffffff800d13b217
0xffffff91300b3a20 : 0xffffff800d13b5fb
0xffffff91300b3a70 : 0xffffff800d8d2b25
0xffffff91300b3ae0 : 0xffffff7f8dcf0ad5
0xffffff91300b3af0 : 0xffffff7f8dcf07e6
0xffffff91300b3b10 : 0xffffff800d86739b
0xffffff91300b3b60 : 0xffffff800d870443
0xffffff91300b3ca0 : 0xffffff800d222d12
0xffffff91300b3db0 : 0xffffff800d1419d8
0xffffff91300b3e10 : 0xffffff800d118635
0xffffff91300b3e70 : 0xffffff800d12f0e5
0xffffff91300b3f00 : 0xffffff800d24b575
0xffffff91300b3fa0 : 0xffffff800d0e3226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[053A5D15-51D4-3E61-978B-EB435FA4BD0A]@0xffffff7f8dcef000->0xffffff7f8dcf7fff

BSD process name corresponding to current thread: watchdogd

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
Kernel slide: 0x000000000ce00000
Kernel text base: 0xffffff800d000000
__HIB text base: 0xffffff800cf00000
System model name: iMac16,2 (Mac-FFE5EF870D7BA81A)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 77024191904601
last loaded kext at 60212582582717: >!UTopCaseDriver 3430.1 (addr 0xffffff7f8ed72000, size 16384)
last unloaded kext at 76958317790656: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f8e1db000, size 24576)
loaded kexts:

!ATopCaseHIDEventDriver 3430.1
!AGraphicsDevicePolicy 4.7.2
AudioAUUC 1.70
@AGDCPluginDisplayMetrics 4.7.2
@fileutil 20.036.15
!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.3f5
!AUpstreamUserClient 3.6.8
AGPM 111.4.2
!APlatformEnabler 2.7.0d0
X86PlatformShim 1.0.0
pmtelemetry 1
!A!IBDWGraphics 14.0.4
@Dont_Steal_Mac_OS_X 7.0.0
!AHDA 283.15
eficheck 1
!AThunderboltIP 3.1.3
|Broadcom!B20703USBTransport 7.0.3f5
|!ABCM5701Ethernet 10.3.5
!ASMCLMU 212
!ALPC 3.1
AirPort.BrcmNIC 1400.1.1
!A!IBDWGraphicsFramebuffer 14.0.4
!A!ISlowAdaptiveClocking 4.0.0
!AMCCSControl 1.13
@filesystems.autofs 3.0
!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
!AAHCIPort 341.0.2
@filesystems.apfs 1412.81.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 3430.1
!AInputDeviceSupport 3430.1
!AHS!BDriver 3430.1
IO!BHIDDriver 7.0.3f5
!AGraphicsControl 4.7.2
|IOAVB!F 800.17
!ASSE 1.0
DspFuncLib 283.15
@kext.OSvKernDSPLib 529
@plugin.IOgPTPPlugin 810.1
@!AGPUWrangler 4.7.2
|IONDRVSupport 569.4
!AHDA!C 283.15
|IOHDA!F 283.15
|Broadcom!BHost!CUSBTransport 7.0.3f5
|IO!BHost!CUSBTransport 7.0.3f5
|IO!BHost!CTransport 7.0.3f5
|IO!B!F 7.0.3f5
|IO!BPacketLogger 7.0.3f5
|IOEthernetAVB!C 1.1.0
!AHIDKeyboard 209
!ASMBusPCI 1.0.14d1
|IO80211!F 1200.12.2b1
mDNSOffloadUserClient 1.0.1b8
corecapture 1.0.4
|IOSkywalk!F 1
@!AGraphicsDeviceControl 4.7.2
|IOAccelerator!F2 438.3.1
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
!ASMBus!C 1.0.18d1
|IOGraphics!F 569.4
!AThunderboltEDMSink 4.2.2
@kext.triggers 1.0
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.80.1
|IOAHCI!F 290.0.1
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
!AThunderboltDPOutAdapter 6.2.5
!AThunderboltDPInAdapter 6.2.5
!AThunderboltDPAdapter!F 6.2.5
!AThunderboltPCIDownAdapter 2.5.4
!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.0
|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.80.2
|IOSCSIBlockCommandsDevice 422.0.2
!ACredentialManager 1.0
KernelRelayHost 1
!ASEPManager 1.0.1
IOSlaveProcessor 1
|IOTimeSync!F 810.1
|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

Ironically I use boot camp on my Mac to play SWTOR, EA/Bioware at least are clear and honest there game doesn’t support Macs. I can respect that, this deception on Blizzard’s part is absurd and unacceptable. Maybe a little more honesty and a little less BS.

7 Likes

Without too much extraneous detail:

Where: PvP Island expedition, two different times (both losses, obviously)
Who: Void Elf Frost Mage on Feathermoon US
What:1) During big mob pull, and 2) after dying in PvP, System froze, I manually restarted
When: around 3:00-4:30 Eastern, 12:00-1:30 realm time, exact timing is hazy.

Also getting some horrendous lag spikes starting a few days back.

2 Likes

I’m having issues with my MacBook too now. This is beyond ridiculous

2 Likes

I’m having issues with my Mac now as well. It freezes randomly and won’t turn on sometimes after WoW shut down my computer one time (and many after) I’ve NEVER had an issue with my Mac before this: it’s new and barely used (I was playing on a different computer before this patch) . This is awfully disgusting

1 Like

Add my name to users of macs with intel graphic drivers that have unsubbed their accounts.

I got excited when I saw a new update for my mac. I thought to myself “yay blizzard talked to apple and apple put out an update!” not true.

My disc priest crashed while killing thoughtstealer vos
(well didn’t crash, because I didn’t allow it to wait that long; I forced shut down)

I was willing to be patient and wait for a fix until I saw this comment:

World of warcraft might be designed specifically for window computers. Even if that is true, I still payed more for my mac than any of my window computers that I’ve ever owned.
As much I enjoy playing this game I’m not going to let this game break my computer.
With that said I have placed WoW into storage on my external drive.
I may be back or I may not

1 Like

Anyone successfully make switch to wow private servers? Let me know…

1 Like

Well, weirdly enough, I’m a lawyer. I putting the paperwork together now for a class action lawsuit. I will need at least 12 to 20 class representatives to be certified under FRCP 23. I’m looking for long time players with significant /played time who have been using Mac for most of the time. As I get closer, I will look for representatives. BTW, my gamer tag is FNLawyer#1402.

21 Likes

Has anyone contacted Intel at all? It’s most definitely a bug in their driver, as people have seen success downgrading to High Sierra. I would think Blizzard would be in contact with both Apple and Intel at this point, but I’m really getting the feeling like they’re going to kill WoW support for Mac after this. Not the first MMO I’ve played where they killed Mac support.

There’s never been a game breaking bug like this for Mac users. And they’ve supported Mac since before Burning Crusade. Four weeks on and the game is unplayable. I have boot camp but, that’s major real estate on a SSD that’s 250gb. Sadly any attempt to build awareness would bring out the lolmac trolls.

3 Likes

Not just that. Blizzard’s games have had been playable on iMacs ever since Warcraft 1. That’s in 1996 (when the iMac client launched).

I would be very shocked if they drop the support now after a quarter-century.

1 Like

Don’t misunderstand, I don’t want them to drop Mac support. I would take faith in the fact that they supported Mac since 1996 as a sign of continued support, if not for the fact that Blizzard is more Activision now and I don’t have a lot of faith in Activision.

Hey, uh, can someone explain to me why “run through old test builds to see which iteration starts the problems, so you can pinpoint the specific 8.3 updated code that breaks intel graphics cards” isn’t a solution here?

In an ideal world, sure, the drivers would be beefed up and WoW wouldn’t need to twist itself to fit them, but the above feels like a very obvious route to take, and only really requires a susceptible mac to test. Unless Blizzard has been rampantly lazy and not kept old PTR builds, mind you, that would also explain why that hasn’t happened.

2 Likes

Approaching 10 years playing WoW (and D3) on an iMac. I started playing WoW specifically because it supported Mac. If they want to stop supporting Mac, they need to say so, take it off the box and stop taking our money! I have had some weird effects after the WoW forced restarts on my Mac (aside from in-game) such as inability to connect my wireless mouse and it seems slower to load other things. And my activity monitor is messed up now. It won’t show actual usage or other data, just the list of processes.

Is anyone technically-minded in a position to set out the real world risks to our computers due to the impact that the WoW crashes are causing?

I’d like to know personally, but actually having it here in writing for Blizzard to see would be useful.

And with the best will in the world, I don’t mean people giving anecdotes of “it slowed my computer down” or “my computer is now dead because of WoW”. I mean a genuine, technically sound explanation of the impact or potential impact that the specific type of crash caused by WoW poses to our machines?

9 Likes

So, did they tweak the graphics too low? Today, tried DMF Firebird’s Challenge on two different chars…No rings appear. They’re there, and I can fly through the first four using the Force…and get credit…but …actually…Now that I look…there aren’t aren’t really any fireworks, much less rings.