Solved Stuck on [EB|#LOG:EXITBS:START]

KrisuTheWizu

New member
AMD OS X Member
Sep 11, 2025
7
0
1
CPU:
Ryzen 5 7500F
Hello!
So I've been following Dortania's installation guide very closely a few days and made my custom EFI folder. In addition, I made a full 14GB MacOS Ventura USB installer on a real MacBook using OCLP. The problem is, my installing hangs on [EB|#LOG:EXITBS:START] and I don't know what to do about it. I already checked Doartania's troubleshooting guides relating this issue but I found nothing that I could improve in my opinion.

I'm a bit concerned if I could map my USB the right way. Additionally there wasn't embedded controller in my motherboard so I used the ACPI path of SBRG device instead. Could you please help me out and point the right direction?

My system:
AsRock B650 PG Lightning
Ryzen 5 7500F
RX 6800

I made my AMD BIOS settings as said in Dortania's guide for Ryzen processors except that I didn't find "OS type" in my BIOS.
 

Attachments

Last edited:
First thing is you need to add SSDT-CPUR.aml table to your /EFI/OC/ACPI folder, as the B650 series of motherboards require this SSDT for macOS to boot.

Your SSDT-EC-USBX.aml looks to be set for an Intel system, not an AMD system.

You should not have any sub-folders within the /EFI/OC/Kexts folders, so delete the 'Tools' folder from this section.

You don't need these kexts or documents, they are not essential to your system booting macOS.
  • alc-verb - not a kext so shouldn't be in this folder.
  • AMDRyzenCPUPowerManagement.kext
  • SMCAMDProcessor.kext
  • SMCRadeonSensors.kext
They can be removed from your OC setup and added back in if required during the post installation phase.

Your UTBMap.kext looks slightly suspect! It may work but I wouldn't recommend relying on this USB configuration past the installation phase for Ventura.

Your config.plist contains a number of incorrect entries, some unnecessary entries and some that were missed for your AM5 system. These have been corrected, removed or enabled as required.

I have used your system DSDT.aml table and Corpnewt's SSDTTime script to generate some custom SSDT's for your system. These have been added to the /EFI/OC/ACPI folder and config. Along with a SSDT-CPUR_PLUG.aml table for your 6-core/12-thread CPU, which should help your system boot.

Some companion ACPI patches have also been added to the config.plist, as a couple of the SSDT's won't work without these patches.

Try the revised EFI attached below. See if that gets you any further with the macOS installation.
 

Attachments

Thank you kindly for your work and fast response. I appreciate it a lot! @Edhawk

I tried your EFI unmodified and unfortunately it didn't make any difference. I have perceived that if I set SetVirtualMap to enabled, installation stops at [EB|#LOG:EXITBS:START] and light goes out from keyboard and mouse even after I made UTBMap.kext again and more properly this time. If it is disabled, the system just reboots immediately when getting to [EB|#LOG:EXITBS:START]. I don't know if this should be enabled or not for my system. My BIOS version is the latest. In my USB mapping there were two usb controllers from which I disabled all ports but otherwise I left them be. I also disabled an usb port with a Led cotroller attached, I wonder if it could be the power/hdd led.

Interestingly now Windows throws a Bios error when booting it from Opencore. This wasn't the case with my EFI. (I'm okay with this, I'm just telling if this happens to be valid information.)

It is very confusing regarding SSDT-CPUR.aml. Especially it felt like Dortania's guide was quite contradictive about it. However, at this page "https://dortania.github.io/OpenCore-Install-Guide/AMD/zen.html#starting-point" the guide says: "Fixes CPU definitions with B550 and A520 motherboards, do not use if you don't have an AMD B550 or A520 system. You can find a prebuilt here: SSDT-CPUR.aml", so I decided to leave it outside at the beginning. Even more cofusing was when I didn't find this SSDT in the EFI you gave me. Still I tried to boot with a prebuilt one from the net and without it (and modifications to config.plist accordingly), which didn't give any results.

I have a question: to enable a SSDT in config.plist manually, can't I just copy another SSDT entry and replace SSDT name with the SSDT that I'm going to add? I did this with Xcode even though there are better tools for it. (checking the new entry is in the correct place ofc)

Thank you for your SSDTs! I tried booting with and without some of these, since Dortania said I would need only SSDT-EC-USBX. This also didn't change anything... Did you fix my SSDT-EC-USBX.aml, by the way? I haven't made any changes to that yet.

Yeah, I don't know what to do. Should I perhaps try different versions of macOS? (Though my dream is Ventura.) Or should I know something about Mmiowhitelist perhaps? I have already tried different USB ports, though only from one controller.

Attached is my new UTBMap.kext, first log is wth your EFI, second log with SetVirtualMap enabled, third log is with SSDT-CPUR.aml with according config modification and the fourth is with SSDT-CPUR.aml and SetVirtualMap enabled. Lastly is the config.plist according to LOG3.

Kind regards, Krisu
 

Attachments

Alright, buddies! The solution was to enable DeVirtualizeMMIO. Booting is still a little unstable, but I think I'll manage. Im so super excited of my new build!!! I'm also happy that I was able to find the solutions myself in the end. Still I'm warmly thanking Edhawk. :)
 
Good to hear you have been able to get your system working with macOS.
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.