What causes Kernel Extension issues on Sequoia 15.1.1 MacOS?

I bought this maxed out 2018 Intel based Macbook Pro with that issue. At the time it would not boot, period. It was in the reboot loop scenario.

I was able to use Configurator 2 to 'revive' the device but even after that it continues to do that most times.

I have erased and re-partitioned the HD to no avail. On a few ocassions I have been able to boot 'successfully' -- in quotes -- because even when that is the case, some very basic apps like Safari and even System configuration just hangs. Further, audio is available but when I play music there's sporadic 'scratched record' sounds, not steady. I suspect this may be a hardware issue but cannot be sure. It is after this successful boot that the system puts out the kernel issue message. It does the same thing after I force quit the mentioned failed apps. It gives me the option to 'reopen' the failed app or to report/ignore the issue. I have reported man of these events, hoping Apple learns of this behaviour.

Once that happens, the restart button does not work, even though only Finder seems to be running and I have to use the power button to restart.

Further, after the failure to boot, the Apple chime no longer sounds and it keeps putting out the multi-language message about a 'problem' preventing the device from booting.

If I boot in safe mode then I lose the audio and camera devices and it takes for ever to setup. Each click takes 3-5 seconds to have any effect on the initial setup of the account in Safe Boot while the fan is noisy and the device heats up as though it was doing heavy work. ?????

There seems to be a fix to the kernel issue but the posting has been removed by the original poster for some misterious reason. I'm at the end of my wits.

Any help will be greately appreciated.


[Re-Titled by Moderator]

MacBook Pro 15″, macOS 15.1

Posted on Dec 7, 2024 8:49 AM

Reply
9 replies

Dec 7, 2024 8:56 AM in response to be-clear

Sounds like a hardware issue.


How to revive or restore Mac firmware - Apple Support

How to revive or restore Mac firmware - Apple Support


In or out of warranty you can get a free over the counter 'Apple Service Diagnostics' test /assessment

Make an appointment for a "hardware issue"

Genius Bar Reservation and Apple Support Options - Apple


Outside the USA

Contact Apple for support and service - Apple Support



Dec 16, 2024 10:25 AM in response to HWTech

I found an Australian technician @Staempunk on YouTube who shows how he repaired an exact same MB Pro with exactly the same symptoms. He went through all troubleshooting steps, to no avail, until he removed the device from its owner's iCloud and Apple ID. Obviously, he had his client's information and after a clean wiping of the HD and a fresh install of MacOS he was able to make it work 100%. I believe it was Sonoma which leads me to believe that I should not attempt to install an OS higher than what the MBP came with and resign myself to do without AI and the other bells and whistles of Sequoia.

Last night I had to revive the device again using Configurator and redo a fresh install of Sequoia. I was able to run diagnostics and all tests checked OK, to my surprise. This indicates hardware is NOT the issue. ??

The reports below were produced while running in SafeMode, again, with no audio or camera detected.



I also ran EtreCheckPro and it detected several kernel panic events, listed below, towards the end:


EtreCheckPro version: 6.8.7 (68068)

Report generated: 2024-12-16 10:36:40

......

Diagnostics Information (past 60 days):

    2024-12-15 21:58:48 Kernel Panic (24 times)

        First occurrence: 2024-12-15 20:09:50

        Details:

            panic(cpu 1 caller 0xfffffff02a069fe0): macOS panic detected

            Panicked task 0xffffffde1fcaaca0: 0 pages, 230 threads: pid 0: kernel_

            task


    2024-12-15 21:14:24 lsd - Crash (2 times)

        Executable: /usr/libexec/lsd


    2024-12-15 20:39:30 bluetoothd - Crash

        Executable: /usr/sbin/bluetoothd

        Details: 

            *** Terminating app due to uncaught exception 'NSRangeException', reas

            on: '*** -[_NSInlineData subdataWithRange:]: range {2, 6} exceeds data

             length 4'

            abort() called

            terminating with uncaught exception of type NSException


    2024-12-15 20:35:01 CalendarAgent - Memory


    2024-12-15 20:34:39 accountsd - Memory

        Executable: /System/Library/Frameworks/Accounts.framework/Versions/A/Support/accountsd


    2024-12-15 20:29:32 WindowServer - Crash

        Executable: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer

        Details: 

            StartTime:2024-12-15 17:18:27

            GPU:IG&AMD

            MetalDevice for accelerator(0x0): 0x7ff220f21548 (MTLDevice: 0x0)

            IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX

            0@0/ATY,Palena@0/AMDFramebufferVIB

            Assertion failed: (x_list_nth(active_managed_displays, 0) == PKGDispla

            yGetSpaceData(pkg_display)), function session_data_handle_display_conf

            ig_change_block_invoke, file /BuildRoot/Library/Caches/com.apple.xbs/S

            ources/SkyLight/SkyLight-312.103/SkyLight/Server/Packages/PKGSpace.c, 

            line 8717.

End of report


Based on the above I can only assume it's the OS which Apple did not test enough on older Intel based devices. I will try again this time installing Sonoma, to see whether the OS is the issue. I'll keep you posted.

Thank you for your feedback and interest on my post.

Dec 7, 2024 6:43 PM in response to be-clear

I agree with @leroydouglas that it is most likely a hardware issue, but there is also a possibility of an issue involving third party software. You can run the third party app EtreCheck and post the complete report here so we can examine it for possible clues.


I'm unclear if you bought a used laptop or whether you bought this laptop new in 2018 & had issues even then. If you bought it used, did you perform a clean install of macOS by first erasing the whole physical SSD (Intel Macs only) followed by reinstalling macOS? If not, then you may be using an OS that was corrupted with who knows what.

Dec 17, 2024 5:43 AM in response to be-clear

I tried installing Sonoma after wiping out the HD (cannot go back to an earlier OS) with disastrous results. The MBP is back at its ‘bricked’ state with the same symptoms: looping at boot, unable to enter recovery mode, and in most cases attempting to recover from Internet but failing to continue. Instead I got the dreaded Apple.support URL message.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

What causes Kernel Extension issues on Sequoia 15.1.1 MacOS?

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