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 keep getting this kernel panic once a week and a half roughly. It freezes the computer (2010ish 17" MBP), showing this error:

(i'll upload the photo soon)

And giving this error dump on reboot:

Interval Since Last Panic Report:  888565 sec
Panics Since Last Report:          1
Anonymous UUID:                    08D63BEE-8C75-4526-B019-3656DE3F605C

Fri Mar  2 15:38:12 2012
panic(cpu 1 caller 0x226ec0): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1504.15.3/osfmk/kern/sched_prim.c:1471
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x4c5fbe18 : 0x21b837 (0x5dd7fc 0x4c5fbe4c 0x223ce1 0x0) 
0x4c5fbe68 : 0x226ec0 (0x593ab8 0xffffffff 0x593a50 0x226790) 
0x4c5fbee8 : 0x2275c6 (0x14cb87c4 0x0 0x44a00000 0x1) 
0x4c5fbf58 : 0x227631 (0x23014c 0x863ea0 0x0 0x2a45c9) 
0x4c5fbf78 : 0x2302e6 (0x23014c 0x863ea0 0x0 0x0) 
0x4c5fbfc8 : 0x2a179c (0x863ea0 0x0 0x10 0x9416164) 

BSD process name corresponding to current thread: kernel_task

Mac OS version:

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro5,2 (Mac-F2268EC8)

System uptime in nanoseconds: 910038174880710
unloaded kexts:  7.1 (addr 0x1ac2000, size 0x40960) - last unloaded 839800501350443
loaded kexts:  7.1 - last loaded 841989895086801 7.1   7.1  7.1
com.vmware.kext.vmnet   3.1.2
com.vmware.kext.vmioplug    3.1.2
com.vmware.kext.vmci    3.1.2
com.vmware.kext.vmx86   3.1.2 9.7.1   5.0  1.9.3d0    2.1.0    3.5.7   1.0.20   2.0.5f14   100.12.31    1.2.0  1.57   2.0.5f14  1.5.2d10    3.0.1d2  3.4   7.0.0 1.1.6   1.5.1    76    4.7.0a1   6.3.6   2.10.6  201.6 201.6  303.8  2.6.8  1.6.4 31.1 1.0.0d1  2.1.7    4.7.3   428.42.4   160.0.0    2.0.17    4.2.4   4.2.4   4.2.0  1.4.0   1.3.1  1.5   1.3.6    1.7    1.3.6  1.4 142.6.0  1   0   2.1.14   142.6.0 2.0.5f14  76   1.0.10d0    6.3.6    2.0.3    76   76    76   76    76   74.2    2.4.5f3  10.0.3   1.8.3fc2    1.3 2.0.5f14 2.0.5f14  76   3.1.0d5 4.7.0a1    6.3.6  1.0.10d0   1.0.1   2.2.1    2.2.1  2.4.5f3 2.4.5f3   2.4.5f3 207.7  4.2.0  2.6.8   1.6  1.6   1.6.1   1.2.6   2.6.8   4.2.4  3.9.0 402.1    2.0.6    4.2.6   320.1  1.10 4.2.4 4.2.4  2.2.7    1.4.0 1.6.6   1.1   1.0.0d1  6 289 1.6.3  1.3.6 2.6.5    1.3.0
Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.42f4
Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: APPLE SSD TS256A, 233.76 GB
Serial ATA Device: HL-DT-ST DVDRW  GS21N
USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24400000 / 2
USB Device: Microsoft® 2.4GHz Transceiver V1.0, 0x045e  (Microsoft Corporation), 0x071d, 0x06200000 / 3
USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8217, 0x06110000 / 4
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0236, 0x04600000 / 3
USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x04500000 / 2

Any ideas?

share|improve this question
Think it could be caused by my MS keyboard, like these guys? – Chris Mar 2 '12 at 5:07
Had the same kernel panic with my 2010 17" MBP. Had to have the motherboard replaced. Another similar case here… – Global nomad Mar 2 '12 at 7:35
I'd highly recommend running the Apple included Hardware Test Tool to see if it finds anything. – Nicholas Smith Mar 2 '12 at 14:35
up vote 3 down vote accepted

You need to find out, if the kernel panic is caused by hardware failure or software/driver related conflicts!

The best way is always to get an idea of what might causing the problem in the first place, therefore you need to gather information and closely observe your system, processes, behavior etc.. in order to pinpoint back to the problem. Secondly, try to recreate the problem, just to make sure your suspicion is correct. The last step is finding the solution to your problem.

This line of information suggest, that MicrosoftKeyboard kext (kernel extension) is causing the panic!!  7.1 (addr 0x1ac2000, size 0x40960) - last unloaded 839800501350443

You can try the following:
Download a linux live cd and boot into it, with no external devices attached, like keyboard, mouse, hdd etc.. if you don't encounter any problems when trying to recreate your problem / or in due time, boot back in your os x partition (with no external devices attached). - (This step only makes sense, if you have no idea of what might be the problem whatsoever!)

Kill all system processes related to "MicrosoftKeyboard" and relocate the which can be found here System/Library/Extensions to another dir, so it will not be loaded when you reboot your OS.

That is my best guess!! Please report back for results.

Edit: You are welcome Chris and hopefully it resolves the kernel panic issue!!

share|improve this answer
I think you're right about the keyboard. I've done some googling and it looks like it's a common problem that MS's lousy intellipoint drivers cause kernel panics. I'll refund the keyboard. Thanks! – Chris Mar 4 '12 at 23:47

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.