Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just got a Retina MacBook Pro and this is my second day of using it.

I was just browsing the internet and a message popped up saying

Your computer was restarted because of a problem

… along with some other text. Here is the output from the panic log:

Fri Jul 20 22:11:00 2012
panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f823e8b9c, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff81a1a9b990, CR3: 0x000000002d616039, CR4: 0x00000000001606e0
RAX: 0x0000000000004242, RBX: 0x0000000000000077, RCX: 0xffffff81a1a8b000, RDX: 0x0000000000795bf2
RSP: 0xffffff81e71cb9b0, RBP: 0xffffff81e71cb9c0, RSI: 0xffffff8028114000, RDI: 0xffffff802aa22000
R8:  0x0000000000000075, R9:  0xffffff7f82442360, R10: 0xffffff81e71cb92c, R11: 0xffffff81e71cb930
R12: 0xffffff8024e67488, R13: 0xffffff802aa22000, R14: 0xffffff81a1a8b000, R15: 0xffffff802aa22000
RFL: 0x0000000000010206, RIP: 0xffffff7f823e8b9c, CS:  0x0000000000000008, SS:  0x0000000000000010
CR2: 0xffffff81a1a9b990, Error code: 0x0000000000000000, Faulting CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff81e71cb660 : 0xffffff8000220792 
0xffffff81e71cb6e0 : 0xffffff80002c4794 
0xffffff81e71cb890 : 0xffffff80002da55d 
0xffffff81e71cb8b0 : 0xffffff7f823e8b9c 
0xffffff81e71cb9c0 : 0xffffff7f823ed0a5 
0xffffff81e71cbb00 : 0xffffff7f823ea010 
0xffffff81e71cbb60 : 0xffffff800065551e 
0xffffff81e71cbb80 : 0xffffff8000655dfa 
0xffffff81e71cbbe0 : 0xffffff800065659b 
0xffffff81e71cbd20 : 0xffffff80002a3f08 
0xffffff81e71cbe20 : 0xffffff8000223096 
0xffffff81e71cbe50 : 0xffffff80002148a9 
0xffffff81e71cbeb0 : 0xffffff800021bbd8 
0xffffff81e71cbf10 : 0xffffff80002af140 
0xffffff81e71cbfb0 : 0xffffff80002dab5e 
      Kernel Extensions in backtrace:[097ADF6F-75A9-30B9-99DA-BC8368951241]@0xffffff7f823e0000->0xffffff7f82446fff

BSD process name corresponding to current thread: Google Chrome He

Mac OS version:

Kernel version:
Darwin Kernel Version 11.4.1: Wed May  2 19:34:43 PDT 2012; root:xnu-1699.28.13~1/RELEASE_X86_64
Kernel UUID: My Magical UUID
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)

System uptime in nanoseconds: 23730041049309
last loaded kext at 300487456992:  4.1.19 (addr 0xffffff7f8176c000, size 16384)
loaded kexts:    4.1.19 9.8.1   6.0.1  1.9.5d0    3.0  1.59   100.12.69   2.0.5d3    5.0.0d8    122   2.2.3fc5   2.2.3fc5   2.2.3fc5    3.5.9   5.0.0d8  1.0.0d1    2.0.1d2    4.0.6f7   7.0.0 1.2.3 3.1.32    5.0.0d8    3.1.32   1.6.0 170.2.2   1.0.33   7.2.4   7.2.4 7.2.4  227.6  4.0.6f7   227.6 227.6 1.0.0d1 1.0.0d1 33 404  2.0.4   551.7.16  1.2.1    3.2.3b7    5.0.5  1.6.1  2.3.0   5.0.5   1.0.5   161.0.0   1.5   1.5  1.7    1.9    1.5  1.6 195.0.0   3.2.30   1.3  8   195.0.0 1.0 1.0   3.2.1 2.2.3fc5   80.0.2  10.0.5   1.8.6fc17    1.3 2.2.3fc5 2.2.3fc5  1.0.10d0 5.0.0d8   3.1.32  5.1.1d6   3.1.3d10 5.1.1d6   1.0.4    1.1.8  1.1.8   1.8.4   1.0.10d0    7.2.4 7.2.4 7.2.4    7.2.4   2.3.4    2.3.4 4.0.6f7   4.0.6f7  13    1.8.4    1.8.4 1.2.5 230.5  5.0.0   5.0.5  5.0.0    1.5.9 2.0.3   420.3 1.0.1b1  2.1 5.0.0    2.0.8 5.0.5    1.6.1 1.7.1   1.1  177.5   1.0.0d1 331.7 1.7.2  28.18  1.5 2.7    1.4
share|improve this question
up vote 6 down vote accepted

Your crash is related to the AppleIntelHD4000Graphics kernel extensions. It wouldn't be the first time Chrome caused troubles with that particular chipset: Google confirms Chrome bug is causing crashes on latest MacBook Air:

The problem seems to have first been discovered early last week, according to reports in Apple's support discussion forums. The common thread among users experiencing crashes was the use of Chrome, which seemed to cause a kernel panic related to the drivers for Intel's HD4000 integrated graphics.

Google says it has filed a bug report with Apple concerning the driver issue, "since it should not be possible for an application to trigger such behavior," the company told Gizmodo. Chrome developers continue to work on a fix for the resource leak, but in the interim, Google has pushed out an update to Chrome that disables GPU acceleration on Macs with HD4000 graphics until the issue is resolved.

So, unless you haven't done so yet, update Chrome to the newest version. Try using another browser in the meantime and see if the problem persists.

share|improve this answer
I have a retina macbook pro so in order to use a browser at the correct resolution I have to use chrome canary, apparently that doesn't have GPU acceleration disabled – DontTurnAround Jul 21 '12 at 2:27
I would probably get involved in the Chrome canary bug tracker discussions regarding that subject! – slhck Jul 21 '12 at 2:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.