Ryzen 9 9950X + ASUS ROG STRIX X870E-E — Monterey Recovery stops at "Registered CoreAnalyticsHub functions with xnu."

[idontknow]

Hi everyone,
I'm trying to install macOS Monterey on a new AMD system and I'm having trouble getting into Recovery.
Hardware:

• CPU: AMD Ryzen 9 9950X
• Motherboard: ASUS ROG STRIX X870E-E GAMING WIFI
• GPU: NVIDIA GTX 960
• RAM: 16GB
• Storage: Samsung 990 Pro but I'll install macOS on 2.5" SATA SSD.
• BIOS version: 0804
• OpenCore version: 1.0.7

My target is macOS Monterey 12.
OpenCore starts normally and I can enter verbose boot, but the boot process stops at:
Registered CoreAnalyticsHub functions with xnu.
After this line, there is no further visible progress and I cannot reach macOS Recovery.
I understand that this is a very new AMD platform, so I'm wondering if anyone here has experience with the Ryzen 9 9950X and X870E platform.
At this point I'm mainly trying to determine whether the problem is related to the platform itself, ACPI, PCIe/device initialization, or something else. I don't want to assume that the last line displayed is necessarily the actual cause.
Any advice on what I should check next would be greatly appreciated.
I can provide additional information such as my BIOS settings, boot arguments, OpenCore version, and more verbose output if needed.
Thanks!

 

[Edhawk]

CoreAnalyticsHub kernel panic - Common Causes & Fixes

• Incorrect ACPI / SSDT Tables: Missing or misconfigured ACPI patches—such as incorrect SSDT-PLUG(or SSDT-PLUG-ALT for newer CPUs) or missing embedded controller patches (SSDT-EC)—frequently cause this. Recompile your ACPI tables directly from the source.

• GPU Compatibility / Framebuffer Issues: Unsupported graphics cards or misconfigured VESA/display-injection parameters can halt the boot process right at this text line. Ensure your GPU patching or spoofing kexts (like WhateverGreen or NootedRed) match your hardware.

• USB Mapping: Faulty port mapping or missing USB controllers in your configuration can freeze initialization. Try rebuilding your USB map or testing with basic USB kext adjustments.

Given your GPU is an Nvidia card I would think that the most likely cause of the kernel panic.