Panic(cpu 5 caller) system freezes

Hi all, I'm new here and hoping to get some help with my setup.

I'm basically running into system freezes when I run safari, Zoom and Mimolive concurrently. The system error is get is as follows. Any help on how I could fix this would be greatly appreciated. Thanks!

panic(cpu 5 caller 0xffffff800a248a5a): Kernel trap at 0xffffff800a68528c, type 6=invalid opcode, registers:
CR0: 0x000000008001003b, CR2: 0x000000010a7be000, CR3: 0x000000041f68113c, CR4: 0x00000000003626e0
RAX: 0x000000047bf00000, RBX: 0x0000000000000315, RCX: 0x0000000000000025, RDX: 0xffffff921ac7be60
RSP: 0xffffff921ac7b750, RBP: 0xffffff921ac7b770, RSI: 0x0000000000000315, RDI: 0x000000047bf00000
R8: 0x0000000000000315, R9: 0x0000000000000000, R10: 0xffffff921ac7be98, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0x0000000000000315, R15: 0x0000000000000000
RFL: 0x0000000000010206, RIP: 0xffffff800a68528c, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000010a7be000, Error code: 0x0000000000000000, Fault CPU: 0x5, PL: 0, VF: 0

Backtrace (CPU 5), Frame : Return Address
0xffffff921ac7b1b0 : 0xffffff800a11c63d mach_kernel : _handle_debugger_trap + 0x49d
0xffffff921ac7b200 : 0xffffff800a256b25 mach_kernel : _kdp_i386_trap + 0x155
0xffffff921ac7b240 : 0xffffff800a2486ae mach_kernel : _kernel_trap + 0x4ee
0xffffff921ac7b290 : 0xffffff800a0c2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff921ac7b2b0 : 0xffffff800a11bd07 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff921ac7b3b0 : 0xffffff800a11c0f7 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff921ac7b400 : 0xffffff800a8c0b5c mach_kernel : _panic + 0x54
0xffffff921ac7b470 : 0xffffff800a248a5a mach_kernel : _sync_iss_to_iks + 0x2aa
xffffff921ac7b5f0 : 0xffffff800a248758 mach_kernel : _kernel_trap + 0x598
0xffffff921ac7b640 : 0xffffff800a0c2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff921ac7b660 : 0xffffff800a68528c mach_kernel : _uiomove64 + 0xc
0xffffff921ac7b770 : 0xffffff800a195d82 mach_kernel : _memory_object_control_uiomove + 0x2b2
0xffffff921ac7b8f0 : 0xffffff800a368bb8 mach_kernel : _cluster_write_ext + 0x3ae8
0xffffff921ac7b930 : 0xffffff800a36b3f9 mach_kernel : _cluster_read_ext + 0x2129
0xffffff921ac7bab0 : 0xffffff800a369c1f mach_kernel : _cluster_read_ext + 0x94f
0xffffff921ac7bd00 : 0xffffff7f8d8bf857 com.apple.filesystems.apfs : _apfs_vnop_read + 0x3ec
0xffffff921ac7bd80 : 0xffffff800a3a00b3 mach_kernel : _utf8_normalizestr + 0x573
0xffffff921ac7be30 : 0xffffff800a69fd62 mach_kernel : _preparefileread + 0x282
0xffffff921ac7bee0 : 0xffffff800a69fa9a mach_kernel : _read_nocancel + 0x8a
0xffffff921ac7bf40 : 0xffffff800a783cd7 mach_kernel : _unix_syscall64 + 0x287
0xffffff921ac7bfa0 : 0xffffff800a0c3206 mach_kernel : _hndl_unix_scall64 + 0x16

Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1412.141.2)[C7BC9A4C-A233-3F83-ACFC-03EAAE280982]@0xffffff7f8d880000->0xffffff7f8d9bbfff
dependency: com.apple.kec.corecrypto(1.0)[02FBB664-AC65-33FE-B843-D0F6EDF20B91]@0xffffff7f8b146000
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[167EE907-2180-3280-973E-33F1CF9F0B33]@0xffffff7f8b09e000
dependency: com.apple.iokit.IOStorageFamily(2.1)[401848BE-FFE8-3A23-9313-0BC891B2BF1F]@0xffffff7f8ae80000


BSD process name corresponding to current thread: ReportCrash
Boot args: keepsyms=1 debug=0x100 alcid=1 agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19H1323

Kernel version:
Darwin Kernel Version 19.6.0: Tue Jun 22 19:49:55 PDT 2021; root:xnu-6153.141.35~1/RELEASE_X86_64
Kernel UUID: EA37759C-12E3-3509-AD57-4B4A4FC5E7AD
Kernel slide: 0x0000000009e00000
Kernel text base: 0xffffff800a000000
__HIB text base: 0xffffff8009f00000


System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)

System shutdown begun: NO
Panic diags file available: YES (0x0)
m uptime in nanoseconds: 494425108786

Hi, is there anybody that could offer some help? Thanks!

Post a copy of your EFI folder, so we can see what you are using and just as importantly what you are not using. Don't tell us you used the EFI from a guide, as you will have needed to edit the guide folder.

Remember to remove/delete the Serial Number, MLB, ROM, SystemUUID/SmUUID etc from your config.plist before you post a copy here.

Edhawk said:

Post a copy of your EFI folder, so we can see what you are using and just as importantly what you are not using. Don't tell us you used the EFI from a guide, as you will have needed to edit the guide folder.

Remember to remove/delete the Serial Number, MLB, ROM, SystemUUID/SmUUID etc from your config.plist before you post a copy here.

Click to expand...

Thanks Edhawk... uploaded the files here. First time here so if there's anything else I need to show, please let me know! Much appreciated

Update you User Profile to show which model CPU you are using, i9 doesn't cut it.

I'll have a look at your EFI folder today and get back to you later.

Edhawk said:

Update you User Profile to show which model CPU you are using, i9 doesn't cut it.

I'll have a look at your EFI folder today and get back to you later.

Click to expand...

Done! Thank you very much!

First thing of note:
You have a USBPorts.kext and USBInjectAll.kext in your /EFI/OC/Kexts folder. This should never be the case.

• If you are using USBPorts.kext to configure your USB ports, then you don't need to have USBInjectAll.kext installed.
• If you are using an SSDT-UIAC.aml to configure your USB ports, then you do require USBInjectAll.kext to be in this folder.

Remove the USBInjectAll.kext from your /EFI/OC/Kexts folder and the corresponding entry in your config.plist, see if this fixes your intermittent kernel panics when using those applications.

Second thing of note:
The beginning of your config.plist contains an entry has been carried over from a Clover config.plist - PluginType=True, which is not used in any version of OC that I have used.



Your config.plist is out of order from the way the sample.plist is normally arranged. Not sure what difference this would really make but it is something you need to be aware of, as there are a lot of misplaced sections in your config.plist. The fact you can boot with this config.plist says something but it gave me a bit of a surprise to see so many sections displaced.

This is the end of the config.plist, where you have three sections that are normally much higher in the layout of the config. ReservedMemory is usually the last section, not DeviceProperties followed by PlatformInformation.

End of config.plist with misplaced sections.

You are using an old version of OpenCore, OC 0.6.3 from November 2020, according to the created date for the OpenCore.efi in your folder.



Creation date of OpenCore.efi is the simplest way to see which version of OpenCore is being used. In this case 2 November 2020 relates to OpenCore 0.6.3.

You should ideally be using OC 0.7.1 or newer, to take in to account the majority of the improvements and fixes that have been applied to OpenCore over the last 8-10 months.

This is a screenshot showing the order of the main sections of the OpenCore 0.6.3 sample.plist, which you would have used to create your config.plist:



This is the same screenshot from your config.plist:



Hope this helps.

Thank you for taking the time to look through my config files. I will try work on it and hopefully it'll sort things out.

How would I re-order the sections in the plist?

Another behaviour I notice is when I launch QuickTime or Zoom, there would be a good 10-15 seconds of the spinning beach ball before I can start using the app. Do you think this has anything to do with the kext files or misplaced sections?

Possibly, the issues I have seen in your OC setup are more likely to be reflected in your boot times and other startup processes. Not so much apps that are run after you have booted the system.

To reorder the contents of your config do the following:

1. Open the config.plist in the latest version of ProperTree,
2. Minimise all the main sections down to a single entry, like I showed in the screenshots in post #8.
3. Then drag the sections to the correct order.

I am not sure what would cause these apps to behave as you have reported. Given the specification of your system I doubt that the issue is insufficient processing or Graphics power.