HELP WITH KERNEL PANIC WITH BIG SUR 11.6.1 ASUS Z490

[dasboot5]

Can someone decipher this kernel panic?

panic(cpu 2 caller 0xffffff8007c9f926): [kext.kalloc.16]: element modified after free (off:0, val:0x0000000000000001, sz:16, ptr:0xffffff9357c64610, prot:zero)
0: 0x0000000000000001
8: 0x0000000000008040
Backtrace (CPU 2), Frame : Return Address
0xffffffa094583390 : 0xffffff800748d25d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0945833e0 : 0xffffff80075d49d3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa094583420 : 0xffffff80075c4fca mach_kernel : _kernel_trap + 0x55a
0xffffffa094583470 : 0xffffff8007431a2f mach_kernel : _return_from_trap + 0xff
0xffffffa094583490 : 0xffffff800748ca7d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0945835b0 : 0xffffff800748cd73 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa094583620 : 0xffffff8007c9d8fa mach_kernel : _panic + 0x54
0xffffffa094583690 : 0xffffff8007c9f926 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa094583b10 : 0xffffff80074ebd56 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa094583b80 : 0xffffff80074eb1a7 mach_kernel : _work_interval_port_type_render_server + 0x3897
0xffffffa094583c50 : 0xffffff800749c96c mach_kernel : _ipc_thread_port_unpin + 0x1cc
0xffffffa094583ca0 : 0xffffff8007bae582 mach_kernel : _IOMalloc + 0x22
0xffffffa094583cc0 : 0xffffff800a5e3da5 com.apple.filesystems.apfs : __ZN22CryptoBufferDescriptor12withCapacityEm + 0x51
0xffffffa094583d10 : 0xffffff800a5e1792 com.apple.filesystems.apfs : __ZN24AppleAPFSContainerScheme5startEP9IOService + 0x91a
0xffffffa094583dd0 : 0xffffff8007bc598b mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xeb
0xffffffa094583e40 : 0xffffff8007bc551e mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xcce
0xffffffa094583ef0 : 0xffffff8007bc46bf mach_kernel : __ZN9IOService14doServiceMatchEj + 0x30f
0xffffffa094583f50 : 0xffffff8007bc7436 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x186
0xffffffa094583fa0 : 0xffffff800743113e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1677.141.2)[A2E36135-081F-3EE7-9F8A-53103C506BE8]@0xffffff800a5ab000->0xffffff800a71afff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[511FC3DC-D63F-3993-9C5C-613AF51D837C]@0xffffff80088fe000->0xffffff8008907fff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[7AC5E118-B326-3E46-980F-4706B9C5ABF0]@0xffffff8008911000->0xffffff8008916fff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[3040B1E0-7488-35C7-9DB9-ED6C9EF965E7]@0xffffff8008d6d000->0xffffff8008d73fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[AEB16297-5950-3E23-84C4-2E9928878BA1]@0xffffff800a06e000->0xffffff800a07ffff
dependency: com.apple.kec.corecrypto(11.1)[379F0025-A70B-3A5D-A92F-3C557D6E4E68]@0xffffff800a748000->0xffffff800a7d9fff
dependency: com.apple.security.AppleImage4(3.0.0)[7B75FFFD-E85A-3686-8D37-27B84E4DFE6D]@0xffffff800897d000->0xffffff800898dfff

Process name corresponding to current thread: kernel_task
Boot args: debug=0x100 keepsyms=1 -revsbvmm chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 20.6.0: Tue Oct 12 18:33:42 PDT 2021; root:xnu-7195.141.8~1/RELEASE_X86_64
Kernel UUID:
KernelCache slide: 0x0000000007200000
KernelCache base: 0xffffff8007400000
Kernel slide: 0x0000000007210000
Kernel text base: 0xffffff8007410000
__HIB text base: 0xffffff8007300000
System model name: iMac20,1 (Mac-)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 906590191
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000000036097cbe

Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000000e6b882bda 0x0000000000000000

And could someone check my config.plist for error for Asus Rog Z490I:
And could someone explain the Launcher option vs Bootx64.efi to protect efi from Window 11 overwrite with dual boot separate disks? I am experiancing Kernel Panics after adding Win 11 install. NO K PANICS BEFORE...

 

[Edhawk]

No idea what caused the kernel panic, sorry.

The Misc > Boot > LauncherOption in OpenCore when set to Full, adds an OpenCore entry to the system bios. This should then be used to select your macOS drive as the first/priority drive in your system, assuming your OC EFI is located on your macOS drive.

This then means you can delete the Boot folder and Bootx64.efi from your /EFI folder, as it is no longer required for booting your system with OpenCore.

A common issue is that Bootx64.efi is overwritten by the Windows installer or during the upgrade process. This results in OpenCore being unable to find the Bootx64.efi driver, which means it can't boot your system. The LauncherOption does away with this issue, so you can update or install Linux or Windows without affecting the OpenCore boot process.

 

[dasboot5]

No idea what caused the kernel panic, sorry.

The Misc > Boot > LauncherOption in OpenCore when set to Full, adds an OpenCore entry to the system bios. This should then be used to select your macOS drive as the first/priority drive in your system, assuming your OC EFI is located on your macOS drive.

This then means you can delete the Boot folder and Bootx64.efi from your /EFI folder, as it is no longer required for booting your system with OpenCore.

A common issue is that Bootx64.efi is overwritten by the Windows installer or during the upgrade process. This results in OpenCore being unable to find the Bootx64.efi driver, which means it can't boot your system. The LauncherOption does away with this issue, so you can update or install Linux or Windows without affecting the OpenCore boot process.

Thank you for the answer. Edhawk. Do you think it might be the addition restrictevents.ext 1.0.5 and the boot arg: -revsbvmm? I did this to upgrade to Monterey from software update but that is not going to happen as I did a test install and lost bluetooth functionalty completely but WiFi stayed intact.

 

[Edhawk]

Not sure what the -revsbvmm boot argument would be used for, as I’ve not seen it before.

Losing Intel Bluetooth seems to be common with Monterey, Itlwm.kext, AirportItlwm.kext and the Intel Bluetooth Firmware kext need to be updated for Monterey if users are to have the same functionality they had with Big Sur.

 

[dasboot5]

Not sure what the -revsbvmm boot argument would be used for, as I’ve not seen it before.

From the restrictevent website:

Lilu Kernel extension for blocking unwanted processes causing compatibility issues on different hardware and unlocking the support for certain features restricted to other hardware.

v1.0.5​

• Added macOS 12 software update support with any Mac model via -revsbvmm

Boot arguments​

• -revsbvmm to force VMM SB model, allowing x86legacy SB model on T2 Mac model for macOS 12

 

[dasboot5]

Losing Intel Bluetooth seems to be common with Monterey, Itlwm.kext, AirportItlwm.kext and the Intel Bluetooth Firmware kext need to be updated for Monterey if users are to have the same functionality they had with Big Sur.

I have a Apple/Broadcom card in the Lower M.2 slot using a adapter to M.2 Sata. Only the Bluetooth finctionality was lost from 11.6.1 to 12.1. The factory intel car was removed from its can, and the port was disabled in the bios, I extended the bulkhead antenna wires from the can throgh a drilled hole with a rubber grommet to the Apple card on lower (stacked) M.2 Nvme/Sata slot array. Intel kexts will not help a natively supported Broadcom card.