How to Diagnose an HP Pavilion Ryzen 5 4600H Stuck After ACPI Loading

By Ufuk Durgun
How to Diagnose an HP Pavilion Ryzen 5 4600H Stuck After ACPI Loading

How to Diagnose an HP Pavilion Ryzen 5 4600H Stuck After ACPI Loading

This original troubleshooting guide addresses a recent community report where Recovery shows a prohibitory sign or freezes shortly after ACPI tables load. It uses a controlled workflow: identify the hardware, protect the current boot path, test one layer at a time and keep a rollback option.

1. Prerequisites

  • Record the hardware: HP Pavilion 15-ec1003nq, Ryzen 5 4600H, Vega integrated graphics and disabled GTX 1650.
  • Target system: macOS Ventura; treat Tahoe as experimental unless the required AMD graphics path is documented as supported.
  • Prepare a 16 GB USB installer, a second USB containing the previous working EFI, ProperTree, MountEFI and a full backup.
  • Do not reuse serial, MLB, ROM or UUID values from an online EFI.

2. Compatibility Snapshot

Confirm the CPU, GPU, storage controller and wireless chipset against the current Dortania OpenCore guide or OCLP documentation. OpenCore is the modern baseline; Clover is only legacy migration context. Unsupported graphics, Intel Iris Xe paths and unverified wireless chipsets must be treated as limits, not configuration mistakes.

3. Installation Preparation

  1. Use UEFI, AHCI, XHCI Hand-off and a current BIOS. Disable the GTX 1650 for macOS where the firmware allows it; do not assume its presence can be patched into a supported graphics path.
  2. Recreate the USB from an authorised macOS source and use GUID partitioning. Do not use modified distributions.
  3. Disconnect non-essential USB devices and use a reliable USB 2.0 port or hub if the installer loses input.
  4. Write down the macOS build, OpenCore version and kext versions before every boot test.

4. EFI and config.plist Review

Use AMD kernel patches configured for the core count, hardware-specific SSDTs and a validated USB map. Keep DevirtualiseMmio and other Booter quirks only when they solve a documented firmware requirement; do not stack experimental quirks.

  • Review ACPI, Booter, DeviceProperties, Kernel, Misc, NVRAM, PlatformInfo and UEFI rather than changing random settings.
  • Use -v keepsyms=1 debug=0x100 during diagnosis and photograph the last useful line.
  • Confirm the EFI layout contains BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools.

5. Post-Installation

  1. Once macOS boots, move only the tested EFI to the internal disk.
  2. Test graphics acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and NVRAM separately.
  3. Map USB ports with USBToolBox or a hardware-specific map; do not copy a map from another machine.
  4. For Apple services, verify a unique SMBIOS and stable NVRAM before troubleshooting accounts.

6. Troubleshooting the Reported Issue

Capture the final verbose line and compare it with the debug OpenCore log. A freeze after ACPI loading often means a misplaced SSDT, an incorrect kernel patch set, a conflicting quirk or a graphics hand-off problem, not a generic need to rebuild the USB.

  1. Return to the last known-good EFI and reset NVRAM from the OpenCore picker.
  2. Make one change, run ocvalidate, reboot twice and record the result.
  3. If the disk or installer is involved, check SMART health, cable/slot seating and the installer checksum before erasing data again.
Common checks
  • Boot stall: distinguish LOG:EXITBS:START, ACPI, storage and graphics hand-off rather than applying every quirk.
  • Graphics: check Metal support before browser or CEF troubleshooting.
  • Network: identify the PCI/USB IDs and macOS version before selecting Wi-Fi or Bluetooth kexts.

7. Dual Boot and Advanced Configuration

Keep Windows/Linux and macOS on separate disks when possible. Do not let Windows replace the EFI without keeping a bootable OpenCore USB. Leave SecureBootModel, FileVault, SIP, custom ACPI and firmware-variable changes until the base installation is stable.

8. Verification, Maintenance and Rollback

  • Boot twice without the installer USB and reproduce the original symptom.
  • Archive the working EFI with the macOS build, OpenCore version and kext versions.
  • Update OpenCore/OCLP and kexts first, verify a reboot, then update macOS.
  • If an update fails, boot from USB and restore the archived EFI or a Time Machine/APFS snapshot.

9. References and Glossary

Glossary: EFI is the boot partition; ACPI and SSDTs describe hardware; a kext is a macOS kernel extension; SMBIOS identifies the model; APFS is the modern macOS file system; verbose boot shows diagnostic output.


Inspired by a recent r/hackintosh discussion. This article is independently written and does not reproduce the original post.

Share:

Leave a Reply

Loading comments...