You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MBP kernel panic when connecting to external monitor

Hi,

I'm having a recurring problem with my MBP 13" (early 2015; Mojave) restarting because of a kernel panic. This happens several times a day, and one time, sometimes several times in an hour.


I'm quite sure the problem is related to how I connect it to an external monitor (Dell U2413; 1920x1200). Because I don't seem to have problems when I use my laptop with nothing connected. I connect to the monitor using mini-DP to mini-Dp (thunderbolt). The restarts may also be more common when I also connect my thunderbolt-to-ethernet adaptor (official apple adaptor) at the same time so that both thunderbolt ports are occupied. But I can't be sure of the last part about whether the ethernet adpator is part of the problem. When I connect just the ethernet adaptor without the external monitor, I didn't get these kernel panics (but need to test more). But I know the monitor connection is definitely problematic.


I don't have any other issues with the video output and have never had problems with this monitor when it's connected to my desktop (via DVI to DVI).


These thunderbolt ports on my MBp aren't too good anyway because sometimes I have to fiddle around with the ethernet one to get a good connection.


I've gone through the generic advice of diagnosing the problem, but since I'm sure it's the external monitor, my question is: what can I do about this?


This is report (I can post the whole thing if it is helpful):

*** Panic Report ***

panic(cpu 0 caller 0xffffff800c7cbc5f): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.278.65/osfmk/kern/sched_prim.c:2420

Backtrace (CPU 0), Frame : Return Address

0xffffff911c5b2db0 : 0xffffff800c7ad5cd

0xffffff911c5b2e00 : 0xffffff800c8e9245

0xffffff911c5b2e40 : 0xffffff800c8da97a

0xffffff911c5b2eb0 : 0xffffff800c75a9d0

0xffffff911c5b2ed0 : 0xffffff800c7acfe7

0xffffff911c5b2ff0 : 0xffffff800c7ace33

0xffffff911c5b3060 : 0xffffff800c7cbc5f

0xffffff911c5b30e0 : 0xffffff800c7ca1df

0xffffff911c5b3130 : 0xffffff800c7924a7

0xffffff911c5b3170 : 0xffffff800c7b38b1

0xffffff911c5b31d0 : 0xffffff800c80de4a

0xffffff911c5b3220 : 0xffffff800c7aeefe

0xffffff911c5b3c70 : 0xffffff800c7af1ba

0xffffff911c5b3cd0 : 0xffffff800ccb950b

0xffffff911c5b3d40 : 0xffffff800ccb92b3

0xffffff911c5b3db0 : 0xffffff800ccd48d0

0xffffff911c5b3e30 : 0xffffff800ccd4d37

0xffffff911c5b3e80 : 0xffffff800c7a5629

0xffffff911c5b3ec0 : 0xffffff800c75a99c


BSD process name corresponding to current thread: Notion


Mac OS version:

18G9028


Kernel version:

Darwin Kernel Version 18.7.0: Mon Mar 8 22:11:48 PST 2021; root:xnu-4903.278.65~1/RELEASE_X86_64

Kernel UUID: 89746746-E781-3BCB-9F35-DB39029ECB25

Kernel slide: 0x000000000c400000

Kernel text base: 0xffffff800c600000

__HIB text base: 0xffffff800c500000

System model name: MacBookPro12,1 (Mac-E43C1C25D4880AD6)


System uptime in nanoseconds: 141798449096

last loaded kext at 16801823765: com.apple.driver.AudioAUUC


Appreciate some help with fixing this, or else a few clues about what may be the problem. I can't afford to upgrade my macbook right now, but this problem is getting quite disruptive.


Best regards,

MacBook Pro 13″, macOS 10.14

Posted on May 14, 2021 8:34 AM

Reply
Question marked as Top-ranking reply

Posted on May 22, 2021 2:20 AM

Removing third-party kernel extensions is a good first step.


I can see that the only third-party extension that you had loaded at the time of the panic was com.usboverdrive.driver.hid, which could be the culprit.


For an exhaustive list of third-party kernel extensions, launch Terminal and enter:

kextstat | grep -v com.apple


The extensions will be located in /Library/Extensions.


If that doesn't work, I'd suggest trying the steps listed in Apple's relevant Support article.

If your Mac restarts and a message appears - Apple Support


Cheers.

Similar questions

11 replies
Question marked as Top-ranking reply

May 22, 2021 2:20 AM in response to Camero99

Removing third-party kernel extensions is a good first step.


I can see that the only third-party extension that you had loaded at the time of the panic was com.usboverdrive.driver.hid, which could be the culprit.


For an exhaustive list of third-party kernel extensions, launch Terminal and enter:

kextstat | grep -v com.apple


The extensions will be located in /Library/Extensions.


If that doesn't work, I'd suggest trying the steps listed in Apple's relevant Support article.

If your Mac restarts and a message appears - Apple Support


Cheers.

May 24, 2021 4:57 PM in response to BobHarris

Hi,

It appears I spoke too soon.... there was another kernel panic crash this morning. So the problem remains even though I uninstalled USB overdrive (and when I enter "kextstat | grep -v com.apple" in the terminal I can see USB overdirve is no longer running. There are no other 3rd party extensions running).


The kernal panics seem to be happening less though. This was the first one in over 2 days, and usually it happens at least once a day.


I still suspect it has something to do with the external monitor cos it never crashes when I don't have it connecting. This would be my best guess, but I don't know how to solve this barring buying a new monitor.


What else can I do?


PS. I've attached the report of the latest crash (after uninstalling USB Overdrive)


May 25, 2021 2:09 PM in response to Camero99

You could run Rember if you want to check your memory. If Rember does not detect anything that does not prove you are good memory, just that Rember did not create a situation that caused the memory to fail. Which could be because the memory is not failing. Only a failure report is useful information.


http://www.kelleycomputing.net/rember

.

Quit as many apps and background tasks as you can (such as menu bar items) so more RAM is available for testing. Booting into Safe mode http://support.apple.com/kb/ht1564 can also free up more RAM for testing, by not loading any 3rd party additions you may have installed.

.

Set Loops: [X] Maximum

and run overnight

May 25, 2021 2:04 PM in response to Camero99

Random thoughts.


  • You have found a situation in Mojave that does make a mistake?
  • You are having memory issues, and a bit in a kernel lock is getting flipped making the code think the lock had already been unlocked.
  • If a Thunderbolt 2 cable connection is being used, Thunderbolt is a bus interface, so maybe the Thunderbold connected device is putting strange signals on the bus
  • If DisplayPort over USB is being used, then the USB bus has been known to cause issues if the device fails or the cable is faulty.
  • HDMI is less likely to cause bus errors, but I will not rule it out.


Think about what you can change. Cables. Adapters, ports you plug into, a different monitor (as an experiment), using a different port to connect a monitor (again as an experiment). Assumes you have another monitor in the house, or can borrow one from a friend. I'm not suggesting spending any big money, but see if you can change something and observe the change (or no change) in behavior. Keep notes.

May 14, 2021 8:39 AM in response to Camero99

Please post one or more panic reports

Finder -> Go (menu) -> Go to folder -> /Library/Logs/DiagnosticReports


Command-Shift-Period will show invisible files. Look for files that end in the word .panic or .contents.panic and post them in an Additional Text box


Press Command-Shift-Period to hid the Finder invisible files again.




thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock

This kind of panic is generally caused by 3rd party kernel extensions. In this case attempting to unlock an internal kernel lock that is already unlocked. macOS does not generally make that kind of mistake.

May 22, 2021 2:31 AM in response to Solid-State Me

The only thing showing up when I search Kext on the terminal is :

Index Refs Address Size Wired Name (Version) UUID <Linked Against>

104 0 0xffffff7f80daa000 0x10000 0x10000 com.usboverdrive.driver.hid (4016) 2F37229C-F840-3242-B938-70EE79F0048E <43 6 5 3>


I've had this app for many years without problem, but maybe the update to Mojave from El Capitan makes it problematic. Anyway seeing as it's the only thing active I will uninstall and see if the panics continue to occur.


Btw, I have several other extensions -- in the library -- but they aren't active right? So I should only focus on the USB overdrive one?

May 22, 2021 2:43 AM in response to Camero99

I've had this app for many years without problem, but maybe the update to Mojave from El Capitan makes it problematic.

This is very likely. A new OS can bring many new changes, and kernel extensions interact with the OS at a very low level.


Btw, I have several other extensions -- in the library -- but they aren't active right? So I should only focus on the USB overdrive one?

Make sure you don't remove the other extensions. If these weren't listed by the aforementioned Terminal command, then they were pre-installed by Apple in macOS.


Best of luck!

May 22, 2021 8:02 AM in response to Camero99

I agree with Solid-State Me that the likely candidate is the USB Overdrive kernel extension. The unlocking of a already unlocked kernel lock is only something that is going to happen in the kernel address space, and generally macOS does not generate these errors, but 3rd party kernel extensions are often the cause of kernel panics.


Years (and years) ago I was a USB Overdrive kernel extension, and at the time it was great.


These days I use BetterTouchTool

https://folivora.ai

Which allows me to customize my mouse, trackpad, keyboard, toutchbar, and my new favorite feature, an extremely useful clipboard manager I can bind to any key, mouse, trackpad gesture. . Not free, but not expensive either, and it is the most useful utility I have on my Mac.

MBP kernel panic when connecting to external monitor

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.