Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
I've been running into this a lot today.
Did the combo update to OSX. Did the SMC reset. Still getting the black screen with stuttering sound.
Hi, I am experiencing this as well. I am on a 2008 MacBook Pro5,1, 2.53 GHz Core 2 Duo. 4 GB of RAM, and I'm running Snow Leopard 10.6.8.
I assumed the machine was just overheating, but I'm getting the panic reports on restart as well. This just started last night, I had been able to play the game for 1-2 hours at a time prior without any problems. Coincidentally, last night was when I installed the most recent version.
The panic report from my last crash (third one tonight):
Thanks for investigating the issue, Blizzard, I hope we can expect a swift resolution.
Edited by Machkhan on 5/27/2012 10:39 AM PDT
Another kernel panic once again while i played Diablo for about 2 hours (longest i've played without a crash by the way)
Edited by Machkhan on 5/27/2012 10:39 AM PDT
Running the combo update and resetting the SMC resulted in the shortest period of play time yet - maybe 2 minutes? - and a spectacular white flash of the screen before it went black with the sound loop. Crash report included for completeness' sake. I'mma try one more time and then go to bed.
Edited by Machkhan on 5/27/2012 10:40 AM PDT
Could you guys (Blizzard) maybe give us an update on your progress? Are you testing fixes or looking for the problem? If you are already testing your fix can you maybe share if it deals with the issue of kernel panics or FPS or both? Any info will be highly appreciated ^^
Edited by zelka#2357 on 5/27/2012 9:29 AM PDT
85 Human Mage
I can never play this for more than 2 hours before I see one of these bastards.
Edited by Machkhan on 5/27/2012 10:45 AM PDT
This is something that the team is still reviewing. From all these examples here we have 2 MBP in which kernel panics happen.
We suggested the troubleshooting steps to see if we can eliminate any driver issues, but still seems that it happens. When the team gets back in I'll see what more we can find about this.
Edited by Machkhan on 5/27/2012 10:44 AM PDT
Thanks for your efforts on this, I appreciate your responsiveness and your attention to our problem.
Appreciate it. I try to get whatever information I can provide out. I'm not on the dev team for Mac, so updates for me occur when I get my hands on information :)
This looks like same kernel panic wow users are also getting on same hardware since 4.3.4. Related? It's definitely an apple bug, but one thing to notice is wow didn't trigger it until 4.3.4, as for D3, well, it seems to trigger it too. So the question for dev team is, what did wow 4.3.4 changed in graphics front end? and what is it D3 does that's similar? Then, when they find cause, report it to apple for fixing(which of course, even if apple fixes it, it'll only be fixed in 10.7 which means all the 10.6 users are still going to have to update their OS regardless).
This issue is affecting iMacs too, not just the macbook pro models. I've had this problem consistently since launch as I bought the collectors edition. I also tried every "fix" suggested on these message boards. At times I've been able to play for hours before a crash while other times it only takes a few minutes to completely freeze and require a hard reset. Regardless of time, it happens eventually in both menus and gameplay.
iMac 27inch model late 2011
Mac OSX 10.7.4
3.4 GHz Intel Core i7
8GB 1333 MHz DDR3 RAM
Radeon HD 6970M 2GB
Interval Since Last Panic Report: 139849 sec
Panics Since Last Report: 1
Anonymous UUID: 04084447-6B52-44D6-BE60-7C0B94E3B14A
Sun May 27 19:05:15 2012
Machine-check capabilities (cpu 1) 0x0000000000000c09:
family: 6 model: 42 stepping: 7 microcode: 26
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Processor context corrupt
ADDR register valid
MISC register valid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
panic(cpu 2 caller 0xffffff80002c4d65): "Machine Check at 0xffffff7f81c48436, registers:\n" "CR0: 0x000000008001003b, CR2: 0x0000000104b34868, CR3: 0x00000000345f7002, CR4: 0x00000000000606e0\n" "RAX: 0x0000000000000001, RBX: 0x0000000000000000, RCX: 0x0000000000000001, RDX: 0x0000000000000000\n" "RSP: 0xffffff80f1b936e0, RBP: 0xffffff80f1b93710, RSI: 0x0000000000000006, RDI: 0xffffff80126fd800\n" "R8: 0xffffff80125bd800, R9: 0x7fffffffffffffff, R10: 0x80000000345f7002, R11: 0xffffff80002da800\n" "R12: 0x0000000000000148, R13: 0xffffff801248cf40, R14: 0xffffff80125bd800, R15: 0x0000000000000001\n" "RFL: 0x0000000000000046, RIP: 0xffffff7f81c48436, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-1699.26.8/osfmk/i386/trap_native.c:278
Backtrace (CPU 2), Frame : Return Address
0xffffff80e8ce0ec0 : 0xffffff8000220792
0xffffff80e8ce0f40 : 0xffffff80002c4d65
0xffffff80e8ce10a0 : 0xffffff80002daa9f
0xffffff80f1b93710 : 0xffffff7f81c372a5
0xffffff80f1b937e0 : 0xffffff7f81c38d9c
0xffffff80f1b93890 : 0xffffff80002c63b2
0xffffff80f1b938b0 : 0xffffff800022d375
0xffffff80f1b938f0 : 0xffffff800022e060
0xffffff80f1b93950 : 0xffffff800022f413
0xffffff80f1b939b0 : 0xffffff7f815ce826
0xffffff80f1b93a00 : 0xffffff7f8158fa3a
0xffffff80f1b93a30 : 0xffffff7f8157c809
0xffffff80f1b93b00 : 0xffffff7f81578ecb
0xffffff80f1b93b60 : 0xffffff800065501e
0xffffff80f1b93b80 : 0xffffff80006558fa
0xffffff80f1b93be0 : 0xffffff800065609b
0xffffff80f1b93d20 : 0xffffff80002a3f08
0xffffff80f1b93e20 : 0xffffff8000223096
0xffffff80f1b93e50 : 0xffffff80002148a9
0xffffff80f1b93eb0 : 0xffffff800021bbd8
0xffffff80f1b93f10 : 0xffffff80002af150
0xffffff80f1b93fb0 : 0xffffff80002da6ce
Kernel Extensions in backtrace:
BSD process name corresponding to current thread: Diablo III
Boot args: 0x0
Mac OS version:
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: iMac12,2 (Mac-942B59F58194171B)
System uptime in nanoseconds: 17623260321077
last loaded kext at 24450321760: com.apple.driver.AppleBluetoothHIDKeyboard 160.7 (addr 0xffffff7f81c7b000, size 20480)
last unloaded kext at 84648987575: com.apple.driver.AppleUSBUHCI 4.4.5 (addr 0xffffff7f80a34000, size 65536)
Here is the kernel panic log...
Please do! What worries me is that these kernel panics are not really heathy. My computer wasn't designed to be forcibly restarted several times a day, but I can't help myself and not play Diablo. Maybe if I had a clue how close you guys are to solving this, I could stop torturing myself and my machine for a while and just wait till you issue the patch. I'm sure I'm not the only person that will be doing this until the problem is solved or - and I hope it doesn't get to that - at least we know we should give up.
Edited by zelka#2357 on 5/27/2012 4:41 PM PDT
Are all of you playing in windowed mode by chance? or toggling in and out of full screen at any point? I know the panics wow gets are strictly from using windowed mode and not staying in full screen entire time. Curious if related or not.
Just to add to the list...
I am running the dual video card macbook pro. I have been playing since launch. I recently discovered window mode gave me much better performance and graphic quality (without changing any of the settings...) I have no idea why. I have been playing this way for the last four or five days. I hadn't had any of these issues until today. I've had to hard restart three times in the last couple hours...
Please continue to work on this Blizz, cause this is a major issue and we are running machines that fit the specs required. thanks.
MacBook Pro 13 2009ish
Intel Core 2 Duo - 2.26 GHz
8 GB Ram
NVIDIA GeForce 9400M
FS Mac OS Extended (Journaled)
Symptoms: Can't finish more the 5 - 10 min in q1 without d3 crashing back into the OS with the d3 crash reporting engine (entries below with UID's) or a few times with a solid lock (with sound loop) and forced hard reset of system. Two of the crashes resulted in the grey OSX hard crash screen asking you to hold the power down for reset. Crashes every time.
crashUID playTime - nontes
<none> 02min - hard lock with apple grey screen saying forced reboot is needed
C4D8E105-32AF-45FD-9965-5DBEAA823B45 02min - after reboot
79BD3338-3FBA-4FE6-87FE-78828E038E68 05min - reopen option from above crash
<none> 02min - reopen option from above crash - hard lock with forced power cycle
437BDBB0-6B08-41F8-9049-B420C78D423F 10min - started after above reboot
<none> 06min - after smc reboot - full on locked up crash with apple screen dump
I have since moved to boot camp and Windows 7. I get longer playing time with this setup about 30 - 50 minutes tops (beats 5 - 10 minutes).
This makes me think that this is a hardware problem specific to the 9400M.
 the first time I've ever exited d3 without a crash was when I fired it up to get the resolution I was running at.
I am going to echo everyone here. I am running a 2009 Mac Pro, and everytime my machine feezes and I restart, I am never provided with a crash report to paste here. This is getting a bit ridiculous.
2.93 GHz Quad-Core Intel Xeon
16 GB Core 2 Duo RAM
ATI Radeon HD 5780 1GB
4TB 7200 RPM drive space
My machine shoudl whistle while playing this game! There is no rhime or reason as to when the freezes occur.
Are you getting kernel panics as well (where the Mac tells you that you need to restart in 4-5 different languages?
Make sure this is the case, if not getting a kernel panic message, then it may be a different issue, which creating a new thread is the best course of action.
Threats of violence. We take these seriously and will alert the proper authorities.
Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.
Harassing or discriminatory language. This will not be tolerated.