Macbook Pro Panic(Cpu 2 Caller Nvrm[0/1:0:0]: Read Error

# Kernel Issues

Issues surrounding from initial booting the macOS installer to right earlier the install GUI pops up.

• Stuck on [EB|#LOG:EXITBS:START]
  • Booter Issues
  • Kernel Patch Issues
  • UEFI Issues
• Stuck on EndRandomSeed
• Stuck after selecting macOS partitioning in OpenCore
• Kernel Panic on Invalid frame pointer
• Stuck on [EB|LD:OFS] Err(0xE) when booting preboot book
• Stuck on OCB: LoadImage failed - Security Violation
• Stuck on OCABC: Memory puddle allocation failure - Not Found
• Stuck on Buffer Too Small
• Stuck on Plist only kext has CFBundleExecutable key
• Stuck on This version of Mac Bone X is not supported: Reason Mac...
• Couldn't allocate runtime area errors
• Stuck on RTC..., PCI Configuration Begins, Previous Shutdown..., HPET, HID: Legacy...
• Stuck at ACPI table loading on B550
• "Waiting for Root Device" or Prohibited Sign error
  • USB Issues
  • SATA Problems
• Kernel panic with IOPCIFamily on X99
• Stuck on or near IOConsoleUsers: gIOScreenLock.../gIOLockState (3...
• Scrambled Screen on laptops
• Black screen after IOConsoleUsers: gIOScreenLock... on Navi
• Kernel Panic Cannot perform kext summary
• Kernel Panic AppleIntelMCEReporter
• Kernel Panic AppleIntelCPUPowerManagement
• Kernel Panic AppleACPIPlatform in 10.13
• macOS frozen correct before login
• Keyboard works simply trackpad does non
• kextd stall[0]: AppleACPICPU
• Kernel Panic on AppleIntelI210Ethernet
• Kernel panic on "Wrong CD Clock Frequency" with Icelake laptop
• Kernel panic on "cckprngintgen"
• Stuck at Forcing CS_RUNTIME for entitlement in Big Sur
• Stuck on ramrod(^^^^^^^^^^^^^)
• Virtual Machine Issues
• Reboot on "AppleUSBHostPort::createDevice: failed to create device" on macOS 11.three+

# Stuck on [EB|#LOG:EXITBS:Get-go]

This section will be split into iii parts, and so pay close attending:

• Booter Issues
• Kernel Patch Issues
• UEFI Bug
• Virtual Machine Issues

# Booter Problems

The main culprits to spotter for in the Booter section are:

• DevirtualiseMmio

  • Certain MMIO spaces are nevertheless required to part correctly, so you'll demand to either exclude these regions in Booter -> MmioWhitelist or disable this quirk outright. More than info here: Using DevirtualiseMmio
  • For TRx40 users, enable this quirk
  • For X99 users, disable this quirk as it breaks with some firmwares

• SetupVirtualMap

  • This quirk is required for the bulk of firmwares and without it it'south very common to kernel panic here, so enable it if non already
    • Mainly Z390 and older require this quirk enabled
    • Notwithstanding, certain firmwares(mainly 2020+) do non work with this quirk then may really cause this kernel panic:
      • Intel'south Ice Lake serial
      • Intel's Comet Lake serial(B460, H470, Z490, etc)
      • AMD's B550 and A520(Latest BIOS on X570 are besides included now)
        • Many B450 and X470 boards with late 2022 BIOS updates are also included
      • AMD'south TRx40
      • VMs like QEMU
      • X299 2020+ BIOS updates(This applies to other X299 boards on the latest BIOS that released either in late 2022 or 2020+)

• EnableWriteUnprotector

  • Some other issue may be that macOS is conflicting with the write protection from CR0 register, to resolve this we have 2 options:
    • If your firmware supports MATs(2018+ firmwares):
      • EnableWriteUnprotector -> Imitation
      • RebuildAppleMemoryMap -> True
      • SyncRuntimePermissions -> True
    • For older firmwares:
      • EnableWriteUnprotector -> True
      • RebuildAppleMemoryMap -> False
      • SyncRuntimePermissions -> Faux
    • Annotation: Some laptops(ex. Dell Inspiron 5370) even with MATs back up will halt on kicking upwards, in these cases y'all'll have two options:
      • Kicking with the old firmware quirk combo(ie. With EnableWriteUnprotector and disable RebuildAppleMemoryMap + SyncRuntimePermissions)
      • Enable DevirtualiseMmio and follow MmioWhitelist guide (opens new window)

Regarding MATs support, firmwares congenital against EDK 2022 volition support this and many OEMs have even added support all the manner back to Skylake laptops. Outcome is it's non always obvious if an OEM has updated the firmware, you tin check the OpenCore logs whether yours supports it(Run across here how to get a log):

• Note: 1 means information technology supports MATs, while 0 means information technology does not.

# Kernel Patch Bug

This department will be separate between Intel and AMD users:

# AMD Users

• Missing kernel patches (opens new window) (only applies for AMD CPUs, make sure they're OpenCore patches and non Clover. Clover uses MatchOS while OpenCore has MinKernel and Maxkernel)
  • Note outdated kernel patches volition also have the same issue delight ensure you're using the latest patches from AMD OS Ten

# Intel Users

• AppleXcpmCfgLock and AppleCpuPmCfgLock
  • Missing CFG or XCPM patches, please enable AppleXcpmCfgLock and AppleCpuPmCfgLock
    • Haswell and newer but need AppleXcpmCfgLock
    • Ivy Bridge and older simply need AppleCpuPmCfgLock
      • Broadwell and older need AppleCpuPmCfgLock if running ten.10 or older
  • Alternatively you lot can properly disable CFG-Lock: Fixing CFG Lock (opens new window)
• AppleXcpmExtraMsrs
  • May also be required, this is mostly meant for Pentiums, HEDT and other odd systems not natively supported in macOS.

# Legacy Intel users

For macOS Big Sur, many firmwares have issues determining the CPU core count and thus will kernel panic besides early for screen printing. Via serial, you tin can see the following panic:

To resolve:

• Enable AvoidRuntimeDefrag under Booter -> Quirks
  • This should work for about firmwares

Notwithstanding on certain machines similar the HP Compaq DC 7900, the firmware volition even so panic and then we need to force a CPU core count value. Only use the below patch if AvoidRuntimeDefrag didn't work:

Legacy CPU Core patch

To exercise this, Add the following patch(replacing the 04 from B8 04 00 00 00 C3 with the amount of CPU threads your hardware supports):

Fundamental	Type	Value
Base	Cord	_acpi_count_enabled_logical_processors
Count	Integer	one
Enabled	Boolean	Truthful
Find	Data
Identifier	String	Kernel
Limit	Integer	0
Mask	Data
MaxKernel	String
MinKernel	String	xx.0.0
Supercede	Information	B804000000C3
ReplaceMask	Information
Skip	Integer	0

# UEFI Bug

• ProvideConsoleGop
  • Needed for transitioning to the next screen, this was originally part of AptioMemoryFix merely is now within OpenCore every bit this quirk. Can be found under UEFI -> Output
  • Note as of 0.5.6, this quirk is enabled by default in the sample.plist
• IgnoreInvalidFlexRatio
  • This is needed for Broadwell and older. Non for AMD and Skylake or newer

# Stuck on EndRandomSeed

Same problems to a higher place, come across here for more than details: Stuck on [EB|#LOG:EXITBS:START]

# Stuck later selecting macOS partition in OpenCore

Aforementioned issues higher up, see here for more than details: Stuck on [EB|#LOG:EXITBS:Showtime]

• Note: Enabling DEBUG OpenCore can help shed some low-cal besides

# Kernel Panic on Invalid frame pointer

So this is due to some event around the Booter -> Quirks you prepare, main things to cheque for:

• DevirtualiseMmio

  • Certain MMIO spaces are all the same required to function correctly, so you'll need to either exclude these regions in Booter -> MmioWhitelist or disable this quirk outright
  • More info here: Using DevirtualiseMmio

• SetupVirtualMap

  • This quirk is required for the majority of firmwares and without it it'southward very mutual to kernel panic here, and so enable it if not already
    • However, sure firmwares do not work with this quirk and so may really cause this kernel panic:
      • Intel's Water ice Lake series
      • Intel's Comet Lake series
      • AMD's B550
      • AMD'due south A520
      • AMD's TRx40
      • VMs similar QEMU

Another issue may be that macOS is conflicting with the write protection from CR0 register, to resolve this we have 2 options:

• If your firmware supports MATs(2018+ firmwares):
  • EnableWriteUnprotector -> Faux
  • RebuildAppleMemoryMap -> True
  • SyncRuntimePermissions -> True
• For older firmwares:
  • EnableWriteUnprotector -> Truthful
  • RebuildAppleMemoryMap -> False
  • SyncRuntimePermissions -> False

Regarding MATs support, firmwares congenital confronting EDK 2022 will support this and many OEMs have even added support all the fashion back to Skylake laptops. Issue is it's not always obvious if an OEM has updated the firmware, you lot can bank check the OpenCore logs whether yours supports it:

Note: 1 means it supports MATs, while 0 ways it does not.

# Stuck on [EB|LD:OFS] Err(0xE) when booting preboot volume

Full fault:

This tin happen when the preboot volume isn't properly updated, to fix this y'all'll need to kicking into recovery and repair it:

1. Enable JumpstartHotplug nether UEFI -> APFS(Recovery may not boot on macOS Big Sur without this option)
2. Boot into recovery
3. Open the final, and run the following:

And so finally reboot

# Stuck on OCB: LoadImage failed - Security Violation

This is due to missing outdated Apple Secure Kicking manifests present on your preboot volume resulting is a failure to load if y'all accept SecureBootModel set, reason for these files being missing is actually a bug in macOS.

To resolve this you lot can do one of the following:

• Disable SecureBootModel
  • ie. ready Misc -> Security -> SecureBootModel -> Disabled
• Reinstall macOS with the latest version
• Or copy over the Secure Boot manifests from /usr/standalone/i386 to /Volumes/Preboot/<UUID>/System/Library/CoreServices
  • Annotation you will nigh likely need to do this via last as the Preboot volume isn't easily editable via the Finder

To do this via terminal:

# Stuck on OCABC: Retentivity puddle allocation failure - Not Found

This is due to wrong BIOS settings:

• Above4GDecoding is Enabled
• CSM is Disabled(Enabling Windows8.1/x WHQL Mode can exercise the same on some boards)
  • Note on some laptops, CSM must exist enabled
• BIOS is upward-to-appointment(Z390 and HEDT are known for having poorly written firmwares)

# Stuck on Buffer Too Small

• Enable Above4GDecoding in the BIOS

# Stuck on Plist simply kext has CFBundleExecutable key

Missing or wrong Executable path in your config.plist, this should exist resolved by re-running ProperTree'south snapshot tool(Cmd/Ctrl+R).

# Stuck on This version of Mac OS 10 is not supported: Reason Mac...

This error happens when SMBIOS is ane no longer supported by that version of macOS, make certain values are set in PlatformInfo->Generic with Automatic enabled. For a total listing of supported SMBIOS and their OSes, run across here: Choosing the right SMBIOS

Supported SMBIOS in macOS 10.15, Catalina

• iMac13,x+
• iMacPro1,1
• MacPro6,1+
• Macmini6,x+
• MacBook8,1+
• MacBookAir5,x+
• MacBookPro9,10+

Supported SMBIOS in macOS xi, Big Sur

• iMac14,4+
• iMacPro1,1
• MacPro6,1+
• Macmini7,1+
• MacBook8,i+
• MacBookAir6,x+
• MacBookPro11,x+

Supported SMBIOS in macOS 12, Monterey

• iMac16,1+
• iMacPro1,1
• MacPro6,1+
• Macmini7,1+
• MacBook9,1+
• MacBookAir7,1+
• MacBookPro11,3+

# Couldn't allocate runtime expanse errors

See Fixing KASLR slide values

Well this full general surface area is where a lot of PCI devices are first setup and configured, and is where most booting problems volition happen. Other names include:

• apfs_module_start...,
• Waiting for Root device,
• Waiting on...IOResources...,
• previous shutdown crusade...

The main places to cheque:

• Missing EC patch:

  • Make certain you have your EC SSDT both in EFI/OC/ACPI and ACPI -> Add together, double check it'southward enabled.
  • If you don't have one, grab it here: Getting started with ACPI (opens new window)

• IRQ conflict:

  • Most common on older laptops and pre-builts, run SSDTTime's FixHPET choice and add the resulting SSDT-HPET.aml and ACPI patches to your config( the SSDT will not work without the ACPI patches)

• PCI allocation issue:

  • UPDATE YOUR BIOS, make sure it'south on the latest. Most OEMs have very cleaved PCI allotment on older firmwares, especially AMD
  • Brand sure either Above4G is enabled in the BIOS, if no option available then add npci=0x2000 to boot args.
    • Some X99 and X299 boards(ie. GA-X299-UD4) may require both npci boot-arg and Above4G enabled
    • AMD CPU Note: Exercise not take both the Above4G setting enabled and npci in kick args, they will conflict
    • 2020+ BIOS Notes: When enabling Above4G, Resizable BAR Support may become an available. Please ensure that Booter -> Quirks -> ResizeAppleGpuBars is prepare to 0 if this is enabled.
  • Other BIOS settings that are important: CSM disabled, Windows eight.1/10 UEFI Mode enabled

• NVMe or SATA issue:

  • Sometimes if either a bad SATA controller or an unsupported NVMe drive are used, you can usually get stuck here. Things you tin can check:
    • Not using either a Samsung PM981 or Micron 2200S NVMe SSD
    • Samsung 970 EVO Plus running the latest firmware(older firmwares were known for instability and stalls, run across here for more info (opens new window) )
    • SATA Hot-Plug is disabled in the BIOS(more than commonly to crusade problems on AMD CPU based systems)
    • Ensure NVMe drives are set as NVMe mode in BIOS(some BIOS take a bug where you tin can set NVMe drives as SATA)

• NVRAM Failing:

  • Mutual issue HEDT and 300 series motherboards, y'all have a couple paths to go downward:
    • 300 Serial Consumer Intel: See Getting started with ACPI (opens new window) on making SSDT-PMC.aml
    • HEDT(ie. X99): Meet Emulating NVRAM (opens new window) on how to stop NVRAM write, annotation that for install you do not need to run the script. Only setup the config.plist

• RTC Missing:

  • Commonly constitute on Intel'due south 300+ series(ie. Z370, Z490), acquired by the RTC clock beingness disabled by default. See Getting started with ACPI (opens new window) on creating an SSDT-AWAC.aml
  • X99 and X299 take broken RTC devices, and so will need to be fixed with SSDT-RTC0-RANGE. Meet Getting started with ACPI (opens new window) on creating said file
  • Some boozer firmware writer at HP also disabled the RTC on the HP 250 G6 with no way to really re-enable it
    • Known affected models: HP 15-DA0014dx, HP 250 G6
    • For users cursed with such hardware you'll need to create a false RTC clock for macOS to play with. See getting started with ACPI for more than details, every bit well as below epitome example:

Example of what a disabled RTC with no way to enable looks like(note that at that place is no value to re-enable information technology like STAS):

# Stuck at ACPI table loading on B550

If you're getting stuck at or well-nigh ACPI table loading with an AMD B550 or A520 motherboard, add together the following SSDT:

• SSDT-CPUR.aml (opens new window)

And please remember to add this SSDT to both EFI/OC/ACPI and your config.plist under ACPI -> Add together(ProperTree's snapshot function tin can practice this for you)

# "Waiting for Root Device" or Prohibited Sign error

• Other names: Stop Sign, Scrambled

This is generally seen every bit a USB or SATA mistake, couple ways to fix:

# USB Problems

This assumes y'all're simply booting the installer USB and not macOS itself.

• If you're hit the xv port limit, you can temporarily go around this with XhciPortLimit but for long term use, nosotros recommend making a USBmap (opens new window)

  • Kernel -> Quirks -> XhciPortLimit -> True

• Another upshot tin exist that sure firmware won't pass USB ownership to macOS

  • UEFI -> Quirks -> ReleaseUsbOwnership -> Truthful
  • Enabling XHCI Handoff in the BIOS can fix this equally well

• Sometimes, if the USB is plugged into a iii.x port, plugging information technology into a two.0 port can fix this fault.

• For AMD'due south 15h and 16h CPUs, yous may need to add the post-obit:

  • XLNCUSBFix.kext (opens new window)

• If XLNCUSBFix still doesn't work, then try the following:

  • AMD StopSign-fixv5 (opens new window)

• X299 Users: Enable Above4G Decoding

  • Odd firmware bug on X299 where USB breaks otherwise

• Missing USB ports in ACPI:

  • For Intel's Coffee Lake and older, we recommend using USBInjectAll (opens new window)
  • For Intel's Ice Lake and Comet Lake, nosotros recommend SSDT-RHUB (opens new window)
    • SSDTTime'south 7. USB Reset selection tin can practice the aforementioned
  • For AMD, run SSDTTime's seven. USB Reset option and add the provided SSDT-RHUB to your EFI and config.plist

# SATA Issues

On rare occasions(mainly laptops), the SATA controller isn't officially supported by macOS. To resolve this, nosotros'll want to exercise a few things:

• Set SATA to AHCI mode in the BIOS
  • macOS doesn't back up hardware RAID or IDE mode properly.
  • Note drives already using Intel Rapid Storage Technology(RST, soft RAID for Windows and Linux) will not be attainable in macOS.
• SATA-unsupported.kext (opens new window)
  • Adds support to obscure SATA controllers, commonly being laptops.
  • For very legacy SATA controllers, AHCIPortInjector.kext (opens new window) may be more than suitable.
• Catalina's patched AppleAHCIPort.kext (opens new window)
  • For users running macOS 11, Large Sur and having issues. This backports the known working Catalina kext, SATA-unsupported is not needed with this kext

Note that you volition only experience this upshot afterward installing macOS onto the drive, booting the macOS installer will not error out due to SATA issues.

# Kernel panic with IOPCIFamily on X99

For those running the X99 platform from Intel, please go over the following:

• The following kernel patches are enabled:
  • AppleCpuPmCfgLock
  • AppleXcpmCfgLock
  • AppleXcpmExtraMsrs
• You lot have the following SSDTs:
  • SSDT-UNC(if non, run across Getting started with ACPI (opens new window) on creating said file)

# Stuck on or nigh IOConsoleUsers: gIOScreenLock.../gIOLockState (iii...

This is correct before the GPU is properly initialized, verify the following:

• GPU is UEFI capable(GTX 7XX/2013+)
• CSM is off in the BIOS
  • May demand to be enabled on laptops
• Forcing PCIe 3.0 link speed
• Double check that ig-platform-id and device-id are valid if running an iGPU.
  • Desktop UHD 630'due south may demand to use 00009B3E instead
• Trying various WhateverGreen Fixes (opens new window)
  • -igfxmlr boot statement. This can too manifest every bit a "Carve up by Zero" mistake.
• Coffee Lake iGPU users may as well need igfxonln=one in 10.15.4 and newer

# Scrambled Screen on laptops

Enable CSM in your UEFI settings. This may appear equally "Kick legacy ROMs" or other legacy setting.

# Black screen after IOConsoleUsers: gIOScreenLock... on Navi

• Add agdpmod=pikera to boot args
• Switch betwixt unlike display outputs
• Try running MacPro7,one SMBIOS with the boot-arg agdpmod=ignore

For MSI Navi users, y'all'll demand to employ the patch mentioned hither: Installer not working with 5700XT #901 (opens new window)

Specifically, add together the following entry under Kernel -> Patch:

MSI Navi Patch

Note: macOS eleven, Big Sur no longer requires this patch for MSI Navi.

# Kernel Panic Cannot perform kext summary

Generally seen as an effect surrounding the prelinked kernel, specifically that macOS is having a difficult fourth dimension interpreting the ones nosotros injected. Verify that:

• Your kexts are in the correct society(chief and so plugins, Lilu e'er before the plugins)
• Kexts with executables take them and plist but kexts don't(ie. USBmap.kext, XHCI-unspported.kext, etc does not contain an executable)
• Don't include multiple of the same kexts in your config.plist(ie. including multiple copies of VoodooInput from multiple kexts, nosotros recommend choosing the first kext in your config's assortment and disable the residuum)

Annotation: this fault may besides look very like to Kernel Panic on Invalid frame pointer

# Kernel Panic AppleIntelMCEReporter

With macOS Catalina, dual socket support is broken, and a fun fact about AMD firmware is that some boards will actually report multiple socketed CPUs. To fix this, add AppleMCEReporterDisabler (opens new window) to both EFI/OC/Kexts and config.plist -> Kernel -> Add

# Kernel Panic AppleIntelCPUPowerManagement

This is likely due to faulty or outright missing NullCPUPowerManagement. To ready the issue, remove NullCPUPowerManagement from Kernel -> Add and EFI/OC/Kexts then enable DummyPowerManagement under Kernel -> Emulate

• Note: On older Intel CPUs(ie. Penryn and older), it may be due to IRQ conflicts or the HPET device being disabled. To resolve, you have 2 options:
  • SSDTTime'south FixHPET Choice (opens new window)
  • Forcing the HPET Device on

Forcing the HPET Device on

Nether ACPI -> Patch:

Comment	String	Force HPET Online
Enabled	Boolean	Yeah
Count	Number	0
Limit	Number	0
Find	Data	A010934F53464C00
Replace	Data	A40A0FA3A3A3A3A3

# Kernel Panic AppleACPIPlatform in 10.13

On macOS 10.13, High Sierra the OS is much stricter with ACPI tables, specifically a bug with how headers were handled (opens new window) . To resolve, enable NormalizeHeaders under ACPI -> Quirks in your config.plist

# macOS frozen right before login

This is a common case of screwed up TSC, for most arrangement add CpuTscSync (opens new window)

The most common way to meet the TSC issue:

Case one	Instance 2

# Keyboard works just trackpad does non

Make certain that VoodooInput is listed earlier VoodooPS2 and VoodooI2C kexts in your config.plist.

VoodooI2C Troubleshooting

Check the order that your kexts load - make they match what is shown nether Gathering Files:

1. VoodooGPIO, VoodooInput, and VoodooI2CServices in whatsoever gild (Constitute nether VoodooI2C.kext/Contents/PlugIns)
2. VoodooI2C
3. Satellite/Plugin Kext

Make sure you have SSDT-GPIO in EFI/OC/ACPI and in your config.plist under ACPI -> Add in your config.plist. If you are still having issues, reference the Getting Started With ACPI GPIO page (opens new window) .

# kextd stall[0]: AppleACPICPU

This is due to either a missing SMC emulator or broken i, make sure of the following:

• Lilu and VirtualSMC are both in EFI/OC/kexts and in your config.plist
• Lilu is before VirtualSMC in the kext list
• Last resort is to try FakeSMC instead, practise non have both VirtualSMC and FakeSMC enabled

# Kernel Panic on AppleIntelI210Ethernet

For those running Comet lake motherboards with the I225-V NIC, you may experience a kernel panic on boot due to the I210 kext. To resolve this, make sure yous take the correct PciRoot for your Ethernet. This commonly being either:

• PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0, 0x0)
  • By default, this is what Asus and Gigabyte motherboards use
• PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
  • Some OEMs may utilise this instead

For those who can to your PciRoot manually, you'll want to install macOS fully and run the post-obit with gfxutil (opens new window) :

This should spit out something like this:

The ending PciRoot(0x0)/Pci(0x1F,0x6) is what you want to add in your config.plist with device-id of F2150000

# Kernel panic on "Incorrect CD Clock Frequency" with Icelake laptop

To resolve this kernel panic, ensure y'all take -igfxcdc in your kicking-args.

# Kernel panic on "cckprng_int_gen"

Full panic:

This is probable to be 1 of 2 things:

• Missing SMC Emulator(ie. no VirtualSMC in your config.plist or EFI)
  • Add VirtualSMC.kext (opens new window) to your config.plist and EFI
• Incorrect SSDT usage with SSDT-CPUR

For the latter, ensure you lot're only using SSDT-CPUR with B550 and A520. Do not employ on X570 or older hardware(ie. B450 or A320)

# Stuck at Forcing CS_RUNTIME for entitlement in Large Sur

This is actually the role at where macOS will seal the organisation volume, and where it may seem that macOS has gotten stuck. Practise Not RESTART thinking you're stuck, this volition take quite some time to consummate.

# Stuck on ramrod(^^^^^^^^^^^^^)

If you become stuck around the ramrod department (specifically, it boots, hits this mistake, and reboots again dorsum into this, causing a loop), this hints that your SMC emulator is broken. To ready this, you lot have 2 options:

• Ensure you're using the latest builds of VirtualSMC and Lilu, with the vsmcgen=one kick-arg
• Switch over to Rehabman'south FakeSMC (opens new window) (y'all can utilise the MinKernel/MaxKernel trick mentioned above to restrict FakeSMC to Big Sur and upwardly

And when switching kexts, ensure you don't have both FakeSMC and VirtualSMC enabled in your config.plist, equally this will cause a conflict.

# Virtual Machine Issues

• VMWare 15 is known to get stuck on [EB|#LOG:EXITBS:Offset]. VMWare xvi resolves the problem.

# Reboot on "AppleUSBHostPort::createDevice: failed to create device" on macOS 11.three+

This is due to XhciPortLimit breaking with macOS 11.3 and newer (opens new window) , to resolve you must disable XhciPortLimit under Kernel -> Quirks. Please ensure you've mapped your USB ports correctly (opens new window) before doing so.

• Alternatively, you lot can boot macOS xi.2.3 or older to resolve
  • For educational purposes, we've provided some images:
    • macOS 11.2.3 InstallAssistant(macOS) (opens new window)

thompsonjudis1994.blogspot.com

Source: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html

Share this post