Install freezes at 12 min; AMD Threadripper 3970x

maccaroni

New member
AMD OS X Member
Jan 9, 2026
7
0
1
CPU:
AMD Ryzen Threadripper 3970x
I was gifted a Threadripper w/ motherboard from a friend so I decided to try my hands at a Ryzentosh before I go back to a Apple. The website has been super helpful in getting started, but after many adjustments and attempts I'm stuck with the same results. Install of MacOS Ventura / Sonoma hangs at 12 min and computer freezes up (mouse stops working). I've tried different OpenCore versions, Quirks, boot-args, kexts, MMIO Whitelist with the same results. I've also patched for the 32-core Threadripper in the kernel but I feel like there could be patches I'm overlooking in the ACPI. Any help getting the install done would be appreciated.

Build:
AMD Ryzen Threadripper 3970x 32-core 3.7GHz
Gigabyte Aorus Trx40 Xtreme ver 1.1 (BIOS Feg latest)
G.Skill Trident Z Neo RGB 192B (6 x 32GB) 2666MHz
EVGA NVIDIA GTX 1080ti Hybrid (temporary until my RX 6600 arrives)
WD Black SN7100 1TB PCIe 4.0
SanDisk 64GB UHS-I USB 3.2 (installer thumb drive)
Dynatron L29 Liquid Cooler (280W TDW)
Lian-Li Edge Gold 750W PSU
Lian-Li Odyessey X Black Ed XL-ATX Case

OpenCore 1.05
MacOS Ventura (latest)
 

Attachments

Last edited:
The most common cause for the installation stalling at the 12 minutes remaining mark, is a borked macOS installer. It is not likely to be a issue with the OC EFI, as an issue in the EFI is more likely to cause an early kernel panic.

You would be advised to delete/erase the current USB installer and macOS application. Download a new installation app using gibMacOS and recreating your USB installation drive. Obviously you have a working OC EFI, so the hard part has already been done.
 
  • Like
Reactions: maccaroni
I tried the install using MacOS Sonoma. This time the system rebooted at 12 min, and I expected to see the partition on the SSD appear, but no luck. I’ll try a Monterey installer when my Radeon card arrives; GeForce card may have pulled too much wattage and the PSU fan stopped working.
 
After a month of my RX 6600 XT being lost in the mail, I've finally have it installed and configured to get me to the macOS installer, but the system still freezes at 12 minutes left. I'm going to attempt to redo my thumb drive with builds from the gibMacOS instead of the AppleStore. 🤞
 
FYI. The installers are downloaded/served from the same location, i.e. Apple’s servers.
 
Tried a new thumb drive. Progress bar moved slightly differently but same result, Stuck at 12 minutes remaining. I even let it run for 10 hours to see if it resumed like another user experienced; it did nothing but keep my room warm. 😩
 
You tried a new thumb drive, was it created with the same macOS installation application your previous USB drive used, or was it created with a completely new macOS download?

The fix for a 12 minute remaining stoppage is to recreate the USB with a new download. Using the same macOS application to create the new drive will just move the borked installer to the new thumb drive.
 
I tried a new download, I've tried 3 thumb drives, and I've tried Monterey, Ventura and Sonoma. All end up with the same result of stuck at 12 min remaining. the only thing I could do differently besides something in the EFI is to create it using a different computer.
 

Attachments

Are you using a USB3 or USB2 port when running the installer? You don't have a custom USB configuration in your OC setup, so that might be part of the issue.

I would recommend booting in to Windows, downloading and running USBToolBox Tool and creating a custom UTBMap.kext for your system before you try to change anything else.

Also the SSDTEC-USBX-Desktop.aml and MaLd0n.aml ACPI tables do the same task, so you only need one of the two tables to be present and enabled in your setup.

I am not sure why you have the SSDT-RX-5700-XT-Version-1.0.aml table in your setup. I have a couple of RX 5700 XT dGPU's and don't require a similar SSDT. I would also look at the extra '.' in the name, as that is not likely to be helping.

Your /EFI/OC/Kexts folder contains a lot of non-essential kexts for booting macOS Ventura. Personally I would recommend reducing these kexts to just above the minimum. By that I mean don't include any Sensor, WiFi or Bluetooth kexts until you reach the Ventura desktop, as this will minimise the issues that might occur due to kext clashes etc.

You have 5 x Ethernet kexts in your setup, I doubt you need any of them.
  1. AppleIGC.kext
  2. AtherosE2200Ethernet.kext
  3. IntelMausi.kext
  4. LucyRTL8125Ethernet.kext
  5. RealtekRTL8111.kext
The specification page for your TRX40 motherboard says it contains Intel® X550-AT2 Dual 10GbE BASE-T LAN. None of the kexts listed above work with this Server grade Ethernet controller.

You need to add IntelLucy.kext to your setup for your Intel 10GB ports to work.


This is a screenshot showing your current Kexts folder.

Screenshot 2026-02-19 at 14.51.24.png

You have WhateverGreen.kext and NootRX.kext present in your Kexts folder, you should never use both at the same time. With your RX 5700 XT I would recommend using WhateverGreen.kext and the agdpmod=pikera boot argument.

This is a screenshot showing your reduced Kexts folder, which I would use just for the installation process. The WiFi/BT and any Sensor kexts can be added once you have macOS installed.

Screenshot 2026-02-19 at 15.13.21.png cut down kexts folder contents, so only essential kexts are present during installation.

Hope this helps.
 
  • Like
Reactions: maccaroni
@Edhawk
Sorry this reply is late, my previous posts didn't go through. This motherboard only has USB 3.2 ports and I was using a 3.2 thumb drive. Everything you've suggested was helpful and informative. I've removed those kexts to lighten the load on my EFI folder, but the main culprit was the MMIO Whitelist. After disabling it I was able to install and I've been having progress ever since. A couple of interesting challenges.
  • RX 6600XT won't work without "agdpmod=ignore" in NVRAM and verbose mode OFF
  • Bluetooth stated working with latest kexts (2.7.1) and then stopped
  • Thunderbolt card can hot plug usb drives, but not recognizing Thunderbolt drive
  • Ethernet ports appear to be active, but I haven't been able to test them yet.
  • Can't wake from sleep. Will the boot-arg "darkwake=0" help with this?
 
You know that you can’t hot-plug a thunderbolt drive on your AMD Hack, yes? It has to be connected when you power on the system or it won’t work in macOS. This is a common issue with macOS and AMD Hacks.

I personally don’t think that using darkwake=0 will help but you can try using the boot argument and see. I don’t recall the darkwake boot argument being used or even mentioned as a solution to sleep/wake issues on AMD hardware, definitely not while using OpenCore. It was a commonly used boot argument while using Clover, but that was with older Intel hardware. I used darkwake=10 with my Gigabyte Haswell systems.

Which WiFi/Bluetooth module are you using Broadcom or Intel, make and model?

Which kext are you using with your RX 6600 XT, WhateverGreen or NootRX? If you are using the MacPro7,1 system definition as I expect, you may not need either kext. The normal boot argument for an AMD Navi GPU is agdpmod=pikera, which is used to prevent black screen issues when reaching the login screen, is this included in your config.plist?

Your motherboard has 2 x USB2.0 headers. 1 x header will be serving the case front USB2.0 ports, if present. The other header will be serving any device connected such as Bluetooth from PCIe card, or maybe a case front card reader. The external USB ports (Type-A & Type-C) on the rear I/O plate and the USB3 & Type-C motherboard headers are all USB3.2 capable as you stated.

How good is your USBMap.kext, would you share a copy so I can see if anything needs amending?
 
Thank you for letting me know about the lack of hotplugging for AMD hacks. Limitations like this are one of the reasons I opted to stay with Intel until now.

My WiFi/bluetooth module is Intel AX200 w/ BT 5 can’t find the chipset. I think something went wrong in the setup because now it won't toggle "ON", but also I have a crappy antenna.

I’m using the latest WhateverGreen kexts and I’ve tried multiple boot args but “agdpmod=ignore” is the only one that eliminates the black screen.

The USB 2.0 header (splitter) is not in use; the front panel for my case uses the USB 3.1 header. The only reason I would need it is if I could get the Maple Ridge card working to replace the Alpine Ridge card.

UPDATE: I was using the wrong kext for the BT; change back to Intel so it comes on and sees devices, but hasn't been able to stay connected to anything.
 

Attachments

Last edited:
Of the 3 x Bluetooth kexts in your /EFI/OC/Kexts folder only one is correct for an Intel Bluetooth device, BlueToolFixup.kext. The other two Bluetooth kexts are specifically for a Broadcom Bluetooth device.

You need to replace the other two kexts with Intel equivalent kexts - IntelBluetoothFirmware.kext & IntelBTPatcher.kext.

You also need to add some Bluetooth related entries to your config.plist under the NVRAM >Add & Delete sub-sections, without these entries the Bluetooth won’t work.

See the config.plist attached below.

Regarding poor antenna performance you probably need to use antenna that aren’t connected and sitting on the rear of your PC case. But rather a pair that are connected mounted up on your desk, via extension cables and a base, like these available from Amazon UK.


Are you using the latest Tahoe compatible version/fork of WhateverGreen.kext, version 1.7.1.7d. See the thread over at Tonymacx86’s for details.

 

Attachments

  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.