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

Constant kernel panic/Ventura 13.2.1/MacBook Pro M2 2023

I've bought new MacBook with M2 processor and get constant kernel panic.

  1. Reboot in safe mode - didn't help
  2. Repair hard disk with First Aid - didn't help
  3. Reinstall OS Ventura - didn't help


Analysing logs I found that the panicked core is always core 5.

I did the load test where I've got 98% CPU(all cores) load (several processes with 1100% load) and 95GB RAM allocated for process (data is from Activity Monitor). Result - no panic.


Then I realised that the panicked application is the app which is using GPU helpers like Google Chrome, Trading View, Visual Studio Code, Brave etc, and my assumption it could be a hardware acceleration feature.


Any ideas @Apple?










MacBook Pro 16″

Posted on Mar 2, 2023 3:25 AM

Reply
26 replies

Mar 14, 2023 9:34 AM in response to HWTech

Thanks for your feedbacks.


I did several investigations more. What I wrote "...which is using GPU helpers like Google Chrome, Trading View, Visual Studio Code, Brave etc, and my assumption it could be a hardware acceleration feature" is not the cause. I disabled/enabled hardware acceleration and the problem haven't gone.


Also, I thought that the root cause is Chrome. No, after re-installation of MacOS I didn't install Chrome but getting rebooting as well.

Now, I can not approve my assumptions about common characteristics of crashed apps. They are totally different.


It is my fifth MacPro (yes, I use three during the day and my partner uses two as well) but first one with ARM processor and the setup of applications is pretty the same on every one but only on this (M2) I have this problem even despite on re-installation of all apps with ARM arch or Universal arch.


Does anybody kmow, is that any option to catch debug log before panic occur as much low-level as it possible?

Mar 14, 2023 12:04 PM in response to PRP_53

Hello HWTech

Thanks for explanation about kexts.


In all (ALL) reports I see this text doesn't matter which process(App) was panicked. (or smbfs)


last started kext at 10468411905: com.apple.filesystems.autofs	3.0 (addr 0xfffffe00108bdb50, size 5904)\
loaded kexts:\
com.apple.filesystems.autofs	3.0\
com.apple.driver.AppleTopCaseHIDEventDriver	6000.22\


Does it mean that the app tried to access filesystem and got crashed by throwing error from kext?



Mar 16, 2023 7:11 AM in response to den.bilyk

If you are getting Kernel Panics (aka crashes) after a clean install or firmware Restore with no third party software installed and no migration/restoration from a backup, then it most likely means there is a hardware issue that needs repaired. Having Google Chrome should not really matter since so many people are using it on macOS without any problems.


An experienced tech knows the diagnostics rarely reveal hardware issues...it is really nice when it happens, but most times they do nothing for us.


It helps if the issue is fairly easy to reproduce so that they can actually see it themselves, but you can try showing them the Kernel Panic logs to show there have been crashes after the firmware Restore and just Google Chrome being installed.


It can be hard to get an Apple tech to take it seriously since Apple does not train them to look at Kernel Panic logs, but they should take it seriously if the crashes occur after a firmware restore. If they won't listen or do anything, then do you have any other local Apple Authorized Service Providers available in your area to see if they might take it more seriously?


I can tell you being a tech that a tech always prefers to see the issue first hand as it may provide clues to which part should be replaced, however, I am unusual in that I will look at the Kernel Panic logs for clues as well and use other means to try to identify even the smallest oddity as it may be related to the client's issue. Unfortunately Apple has very specific steps for their authorized techs to follow and for some this is all they know about troubleshooting computers. Keep in mind part of the problem is if the tech guesses wrong, then the customer will be upset that they paid for a repair which did not solve the problem...for a problem which is difficult to reproduce this is a real problem. For a problem easily reproducible it is less of an issue since the tech should know within a certain amount of time with testing if the problem appears to be gone. I can tell you from the tech's perspective, intermittent failures, especially ones hard to reproduce, are just as frustrating for us.

Mar 30, 2023 3:02 AM in response to Old Toad

Thanks for this info. It is useful for regular users, I believe, and related to VPN providers. From the article: "The VPN provider can see all your traffic, and do with it what they want - including logging."

Yes, it is very important to understand this and be aware of it.

But, it is not my case, because I use private p2p bridges on own servers, no any VPN providers, and BTW, I developed one of the popular VPN service :)

Constant kernel panic/Ventura 13.2.1/MacBook Pro M2 2023

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