Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

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 have macbook model 2009 that is crashing. I dont' understnad why is this happening

Sun Jul  7 00:28:01 2013
panic(cpu 0 caller 0xffffff80084b8655): Kernel trap at 0xffffff8008462af0, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000011cad0160, CR3: 0x000000006116f000, CR4: 0x0000000000000660
RAX: 0x0000000000000014, RBX: 0xffffff800eabe6c8, RCX: 0xf7ffff801f1abc40, RDX: 0x0000000000000821
RSP: 0xffffff80e8fcbda0, RBP: 0xffffff80e8fcbf20, RSI: 0x00000000030bf000, RDI: 0xffffff801f1abc40
R8:  0xffffff80e8fcbee0, R9:  0xffffff80e8fcbed0, R10: 0x0000000000001002, R11: 0x0000000120254000
R12: 0x0000000040000800, R13: 0xffffff801f1abc40, R14: 0x00000000030bf000, R15: 0xffffff800eabe704
RFL: 0x0000000000010246, RIP: 0xffffff8008462af0, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x000000011cad0160, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff80e8fcba40 : 0xffffff800841d626 
0xffffff80e8fcbab0 : 0xffffff80084b8655 
0xffffff80e8fcbc80 : 0xffffff80084ce17d 
0xffffff80e8fcbca0 : 0xffffff8008462af0 
0xffffff80e8fcbf20 : 0xffffff80084b8aa0 
0xffffff80e8fcbfb0 : 0xffffff80084ce0a1 

BSD process name corresponding to current thread: mdworker

Mac OS version:

Kernel version:
Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
Kernel slide:     0x0000000008200000
Kernel text base: 0xffffff8008400000
System model name: MacBook6,1 (Mac-F22C8AC8)

System uptime in nanoseconds: 505020014105
last loaded kext at 282811440391: 1.8.1 (addr 0xffffff7f8a3ec000, size 65536)
last unloaded kext at 466200391898:   1.8.1 (addr 0xffffff7f8a3ec000, size 57344)
loaded kexts:  1.9.5d0  1.60    4.1.4f2  1.0.0d1    3.5.10   100.12.87    122   8.1.2   2.3.7fc4   7.0.0   2.3.7fc4 170.2.5    2.0.19  4.1.4f2 3.4.5   615.20.17    1.0.0   1.6.0   1.1.11    3.0.3d1    3.0  237.1 237.1 1.0.0d1 1.0.0d1 34  3.5.5 404  2.3.1    5.5.5   161.0.0  2.5.2   5.5.0   5.2.5  1.7   1.5  1.8   1.7    1.9    1.7  1.6 196.0.0   4.0.39   2.1   196.0.0  10.0.6   86.0.4    8.1.2    8.1.2 2.3.7fc4   1.8.9fc11    1.6   4.1.4f2   1.0.4 4.1.4f2 2.3.7fc4 2.3.7fc4   3.4.5   2.3.7   530.4  3.0  2.2.9 1.0.0  1.0.11d0 5.3.0d51   1.0.11d0    2.3.7   3.1.4d2 1.0 237.3  5.2.5   5.5.5  5.2.5  3.5.5   1.7  1.7.1   1.7.1   2.5.1   3.5.5 5.5.5    2.3.1 5.6.0    1.7 1.8.1   1.1  220.3   1.0.0d1  7 345 1.8  28.21  1.7 2.7.3    1.4    1.0

What is going on with this report?

share|improve this question
Is this happening since you updated to 10.8.4 1 Month ago ? – Buscar웃 Jul 7 '13 at 4:44
Run it in Safe mode for a while to see if you have conflicting drivers. – Buscar웃 Jul 7 '13 at 4:53
yes it is happening in 10.8.4 when i updated – Zagham Arshad Bajwa Jul 7 '13 at 5:02
Well you can try the Safe mode to see. I would say it is a driver conflict, but do not know which one. You are not showing all the drivers in the report, specially the non apple ones. – Buscar웃 Jul 7 '13 at 5:36
any of the external software could be the problem like the Air Display, DisplayLink, Logitech Control Center, Sunflower ect. – Buscar웃 Jul 7 '13 at 5:39

The why is quite simple from a high level detail. The kernel is dumping a bunch of diagnostics since one of the hundreds of processes that run all the time had a hiccup and the system couldn't tell you anything more helpful.

It's easy to have a language where you can describe nonsense or illogical ideas. Computers are math based, so if you tell them to divide 5 things by 0 an error arrives. Unless the programmer has considered that this error could happen and writes code to handle those exact errors, the kernel is the last line of defense and it has told you it's giving up and dumping information an engineer might be able to use to debug the problem.

If I was that engineer, I would notice that spotlight's mdworker process might have been the last one in the vicinity where the crash was logged and that the last change to the kernel was unloading MSDOS extension, so I would ask you if you have any PC drives connected or ejecting and if this crash was actually within 8 minutes (505 seconds) from the time the Mac was started.

Another high level analogy is if your car stalls, try starting it up again. Only if it's stalling in a repeated way or you have other needs (like you're driving the president around) would you try to fix it yourself or hire a team of engineers to know what to do. In your case, we would need to know a lot about what you have connected to the Mac, if you can boot from a clean install of the OS, if you have expertise or time to troubleshoot this or if you just want assurance on what to do next.

From a user level perspective, here are tips you can take to know how to handle them:

Feel free to ask a follow on question if you have more context to this one panic dump or have questions how to use the article above to solve your dilemma.

We also have a few threads that might help you narrow down some options:

share|improve this answer

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.