- Joined
- Nov 27, 2015
- Messages
- 13
- Motherboard
- Asus Prime Z370-A
- CPU
- i7 8700
- Graphics
- UHD630
- Mac
- Mobile Phone
Hi everyone,
I'm currently building a hackintosh with the Asus Prime Z370 A and ASRock's Thunderbolt 3 AIC.
BIOS version 1002
OSX Sierra 10.13.5
Clover version 4458 (Latest version gets stuck at the plus signs every time)
The card works perfectly on Windows, on Mac it behaves very weirdly:
- Thunderbolt devices will be recognized on OSX if the system was previously booted in Windows
- OSX won't boot if it gets "cold booted", it will just get stuck at "Couldn't allocate runtime area"
- OSX WILL BOOT WITH WORKING THUNDERBOLT every time if I get into BIOS, hit "save changes and reset" (Even with no changes)
- OSX WILL BOOT WITH WORKING THUNDERBOLT if I boot from USB Installer Bootloader
I will keep updating you as I experiment and try to get this working properly, If anyone has suggestions they would be really appreciated!
UPDATE 13/07/2018:
The problem seems to be the memory below 4GB is too fragmented to allocate the memory needed.
I tried all versions of AptioFix to no avail, also tried with LowMemFix, Fix2Drv-Free2000.efi and Test2.efi
These are the outputs from various combinations:
I'm currently building a hackintosh with the Asus Prime Z370 A and ASRock's Thunderbolt 3 AIC.
BIOS version 1002
OSX Sierra 10.13.5
Clover version 4458 (Latest version gets stuck at the plus signs every time)
The card works perfectly on Windows, on Mac it behaves very weirdly:
- Thunderbolt devices will be recognized on OSX if the system was previously booted in Windows
- OSX won't boot if it gets "cold booted", it will just get stuck at "Couldn't allocate runtime area"
- OSX WILL BOOT WITH WORKING THUNDERBOLT every time if I get into BIOS, hit "save changes and reset" (Even with no changes)
- OSX WILL BOOT WITH WORKING THUNDERBOLT if I boot from USB Installer Bootloader
I will keep updating you as I experiment and try to get this working properly, If anyone has suggestions they would be really appreciated!
UPDATE 13/07/2018:
The problem seems to be the memory below 4GB is too fragmented to allocate the memory needed.
I tried all versions of AptioFix to no avail, also tried with LowMemFix, Fix2Drv-Free2000.efi and Test2.efi
These are the outputs from various combinations:
- LOWMEMFIX + CLEAR CMOS: Failed to allocate 0x11eca pages at 0x##### - NEVER BOOTS
- FREE2000.EFI + CLEAR CMOS: Failed to allocate 0x11ecb pages at 0x##### / BOOTS MOST OFTEN
- TEST2.EFI + APTIOFIX1 + CLEAR CMOS: MEMORY EXCEEDS OUR ALLOCATED RELOCATION BLOCK (even if the size of the reallocation block seems like it should be large enough)
- TEST2.EFI + APTIOFIX2 + CLEAR CMOS: SOMETIMES BOOTS
- TEST2.EFI + APTIOFIX3 + CLEAR CMOS: REBOOTS TO CLOVER / ERROR ALLOCATING 0x11ece AT 0x#####
- TEST2.EFI + CLEAR CMOS: REBOOTS TO CLOVER / ERROR ALLOCATING 0x11ece AT 0x####
Last edited: