After I upgraded my iMac to Ventura, I received a kernel panic

Hello


Can anyone help me with this problem?


After I upgrade my iMac to Ventura, I receive this error and iMac restart again and again...


I reinstall MacOS and this error aper again and iMac restart...


What can I do with this problem?


First time when my iMac was restart alone and I receive this error was after I used After Effects and blender 3d...




panic(cpu 6 caller 0xffffff800b50a796):  initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib


  Referenced from: <2D7AC05B-8AF0-3676-A40A-E40B77ACA459> /sbin/launchd


  Reason: tried: '/usr/lib/libSystem.B.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/libSystem.B.dylib' (no such file), '/usr/lib/libSystem.B.dylib' (no such file, no dyld cache), '/usr/local/lib/libSystem.B.dylib' (no such file)




uuid info:


 0x109d33000 uuid = <2d7ac05b-8af0-3676-a40a-e40b77aca459>


 0x10da80000 uuid = <0f050705-2258-3d40-b7bc-f3b35a44bbea>




Thread 0 crashed




RAX: 0x0000000002000209, RBX: 0x0000000000000000, RCX: 0x00007ff7b61cb738, RDX: 0x00007ff7b61cbba0


RSP: 0x00007ff7b61cb738, RBP: 0x00007ff7b61cb780, RSI: 0x0000000000000001, RDI: 0x0000000000000006


R8:  0x00007ff7b61cb7a0, R9:  0x0000000000000000, R10: 0x000000000000003d, R11: 0x0000000000000246


R12: 0x000000000000003d, R13: 0x00007ff7b61cbba0, R14: 0x0000000000000001, R15: 0x0000000000000006


RFL: 0x0000000000000246, RIP: 0x000000010dae983a, CS:  0x0000000000000007, SS:  0x0000000000000023




Thread 0: 0xffffff95acee7b30


0x000000010dae983a


0x000000010db029f9


0x000000010da8a1e1


0x000000010da87660


0x000000010da86281


[Re-Titled by Moderator]

iMac 27″, macOS 13.0

Posted on Nov 5, 2022 4:59 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 17, 2022 5:00 AM

Hello guys

I returned with a result related to the problem with this error.

Finally, I managed to discover with your help what the error was.

It was from one of the memory.

I tested one of the 4 memory in turn and discovered that one of them no longer works as it should.

Considering that the Crucial company offers a lifetime warranty, I will change this memory. :)

Thank you for your help!

Be blessed!

Similar questions

34 replies
Question marked as Top-ranking reply

Nov 17, 2022 5:00 AM in response to HWTech

Hello guys

I returned with a result related to the problem with this error.

Finally, I managed to discover with your help what the error was.

It was from one of the memory.

I tested one of the 4 memory in turn and discovered that one of them no longer works as it should.

Considering that the Crucial company offers a lifetime warranty, I will change this memory. :)

Thank you for your help!

Be blessed!

Nov 7, 2022 7:14 AM in response to manaes

Did you have any crashes after performing the clean install of macOS, but before installing any third party software or migrating/restoring from backup? If so, then you have a hardware problem of some sort.


The last EtreCheck report really doesn't help much since it appears you restored/migrated from a backup which may have brought back the problem to the clean OS. Personally I would perform another clean install of macOS, but only migrate/restore the home user folder leaving everything else unchecked. Then manually reinstall your third party apps. It is best to first test the system thoroughly before installing any third party apps. If there are no issues, then try installing third party apps one at a time and test thoroughly each time so you may be able to determine which app may be causing the problem. It may mean that app has a problem, or maybe that app is more sensitive to the hardware issue, but either way it helps narrow down the problem and make it more reproducible.


The Kernel Panic you posted only suggests that bad memory or Logic Board may be the problem. The last started drive was for a Keyboard.


You can try checking the memory using a bootable Memtest86 USB stick. Testing 128GB of RAM will take a very log time. If the default Memtest86 settings don't report any issues, then I like to change the Memtest86 CPU settings to "Sequential" and "Round Robin" as they seem to be alerting to issues more often than the default CPU settings. Memtest86 may report an actual memory error, or the test may just freeze the system which is just as useful since it indicates a problem.


What is the make & model of the memory?


Nov 7, 2022 11:45 AM in response to manaes

Looking up the CT32G4SFD8266.16FB2 part number does not show it as Mac compatible (no where on this link does it mention the Mac or any specific system this particular part is compatible):

https://www.crucial.com/memory/ddr4/ct32g4sfd8266


Here is the memory which is Mac Compatible for your specific iMac. The 32GB modules which are Mac compatible have a part number CT32G4S266M (or Configuration ID CT19090528).

https://www.crucial.com/compatible-upgrade-for/apple/imac-(retina-5k--27-inch--2020)-imac20-1


I suggest you contact Crucial tech support and show them the picture of the memory you posted here so they can confirm whether that memory is indeed compatible with your iMac. From everything we have available, I would say the memory is not Mac compatible, but only Crucial can confirm for sure.

Nov 5, 2022 1:26 PM in response to manaes

manaes wrote:

I open in safe mode, I use Disk Utility for First Air but after restart the error is still there.

I installed the system on an EXTERNAL SSD and the problem persists...

This indicates you have some third party software installed which is interfering with the normal operation of macOS. Usual culprits are anti-virus apps, cleaning/optimizer apps, and third party security software....none of which are needed on a Mac. These types of apps usually cause more problems than they solve, plus they impact system performance. If you have any of these types of apps installed, then uninstall them by following the developer's instructions. If you still have issues after uninstalling these apps, then run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.

Nov 7, 2022 10:58 AM in response to manaes

Make sure all of the modules are firmly seated in their slots.


Do you still have the original RAM modules that came with the iMac? If you do you can replace them by themselves and run for a while to see idc you get panic attacks. If you do it might be, as P. Phillips mentioned, the logic board and that's the kiss of death $$$wise unless you're still under warranty.

Nov 7, 2022 1:53 PM in response to manaes

I understand what you are saying, but that doesn't necessarily mean anything.


You should definitely check with Crucial support to verify if those memory modules are compatible with your iMac. It doesn't make sense to do anything else until you get confirmation from Crucial. You should also verify all four modules have the same part number as well. If they have different part numbers, then you will need to confirm with Crucial if those two parts are compatible. If they were purchased as part of an official Crucial Kit, then they should be identical, but if they were purchased individually the modules may have different part numbers.


Memory compatibility is so crazy these days, that even buying the same part number from the same vendor at the same time can still cause compatibility issues when mixing memory if they were not all manufactured on the same day & on the same line. That is why Crucial and other memory vendors tend to sell memory in "kit" form. Like I said, memory is not simple these days. I can no longer keep up with all the changes and will ask Crucial or even the OEM of the device to confirm if the memory configuration I'm planning is acceptable before making a memory purchase. I never used to do that years ago.


This is also why most contributors on these forums will only recommend memory from Crucial or OWC. Even then the memory purchased must be the specific part number that the memory vendor recommends for that specific computer. Crucial & OWC make it very easy to identify the correct compatible parts. It is a bit more difficult & risky to then buy the RAM from a third party unless the third party vendor are very precise in providing actual Crucial part numbers to confirm compatibility -- most official authorized Crucial resellers do this, but other unauthorized resellers may not.


Nov 17, 2022 6:27 AM in response to manaes

1 - System Integrity Protection disabled - System Integrity Protection is disabled.


A - If Apple wanted the computer to run without SIP enabled - it would have designed the OS to run it this way


A - Suggest reading about SIP and to re-Enable this important feature of macOS Disabling and Enabling System Integrity Protection - Apple ...


2 - Kernel panics - This system has experienced kernel panics. This could be a sign of hardware failure. But it is not definitively so and maybe connected to Software issue


A - If in doubt Have the computer evaluated by the Professionals who have the Special Hardware / Software and Expertise to diagnose the issue and offer possible solutions

Nov 6, 2022 4:45 PM in response to manaes

You have System Integrity Protection (SIP) disabled which is very bad to do since any app on this Mac may be doing something unexpected. A few years ago a simple Google Chrome update caused people's Macs not to boot which had SIP disabled. I suggested re-enabling SIP to see what happens. If you are running an app that will not work unless SIP is disabled, then you should stop using that app.

https://arstechnica.com/information-technology/2019/09/no-it-wasnt-a-virus-it-was-chrome-that-stopped-macs-from-booting/


Also, you have a lot of those "ProxiedDevice-Bridge" crashes. I'm not sure what they are, or whether they may be the cause or just a symptom of the problem. You definitely have more of these crashes than most people who post an EtreCheck report here. Several of your Kernel Panic reports mention memory being modified after being freed.  This could indicate an app which is improperly accessing the memory, or perhaps a hardware memory failure. Since the panics seem otherwise unrelated with a couple showing "Page Faults" this could mean bad memory could be a contributing factor as well.


If these crashes only began after upgrading to Ventura, then make sure each of the apps listed in the report are versions which are compatible with Ventura. Do not consider an app is compatible with Ventura just because it may say something like "macOS 10.13 or later" since the developer may not have updated the website since Ventura was released.

Nov 7, 2022 9:36 AM in response to manaes

You are using memory from Micron, but that does not necessarily mean it is compatible with the Mac. When Crucial (the consumer branch of Micron) sells memory for use in a Mac, that memory is listed both on the product page and on the plastic packaging the memory ships in as "For Mac" or "Mac Compatible". Only a Crucial part number listed on the label of the physical module will be able to allow us to confirm a Mac compatible part with the Crucial website. Unfortunately Crucial stopped printing "For Mac" or "Mac Compatible" on the actual label on the physical RAM many years ago. If this not memory from Crucial (even if it is from Micron directly), then you will need to confirm with the memory manufacturer the memory is compatible with your exact Mac (and confirmation needs to be more than the pin count, speed, and CL ratings are correct since there are a lot more timings that also need to be compatible). If you did purchase Crucial memory, then remove one of the RAM sticks (unplug the Mac first) and post the part number(s) listed on the label (there may be two different part numbers on the label---I would want to see both in order to confirm Mac compatibility).


FYI, when purchasing RAM for any device, people should only purchase the exact part numbers the memory vendor assures is compatible with a product by using the tools on the memory manufacturer's website to confirm compatibility. Purchasing memory solely based on technical specifications will usually lead to compatibility issues since the computer/motherboard manufacturer does not usually list all of the technical specifications for full compatibility. Years ago (before 2006) it was possible to do so, but memory has gotten a lot more complicated in the intervening years.


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.

After I upgraded my iMac to Ventura, I received a kernel panic

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