- Joined
- Dec 29, 2018
- Messages
- 5
- Motherboard
- Gigabyte Aorus Z390 Pro
- CPU
- i9-9900K
- Graphics
- GTX 1080 Ti
- Mac
- Mobile Phone
I have been banging my head at some boot-issues I am having with a new hackintosh (Gigabyte Aorus Z390 + 9900K).
Specifically it will often fail to boot with the message "Couldn't allocate runtime area", but sometimes it will boot fine (regardless of it being a cold boot or reboot).
As far as I can see, the culprit seems to be EmuVariableUefi-64, which I have installed as I need nvram emulation for iMessage etc.
I'm currently using Clover r4813, but here are other things I have tried:
After trying all these things, I have reverted to simply uninstalling EmuVariableUefi-64 now, and no more boot issues - but also no more NVRAM emulation, which is kind of an issue.
Anybody got any suggestions what to try? I have tried finding others with this particular problem, but haven't found any posts on it - typically is a problem with the AptioFix to use, not specifically with nvram emulation being the cause.
Specifically it will often fail to boot with the message "Couldn't allocate runtime area", but sometimes it will boot fine (regardless of it being a cold boot or reboot).
As far as I can see, the culprit seems to be EmuVariableUefi-64, which I have installed as I need nvram emulation for iMessage etc.
I'm currently using Clover r4813, but here are other things I have tried:
- Using Rehabman's Clover builds (r4701.RM-4963)
- Using OsxAptioFixDrv-64 (from Clover r4813)
- Using OsxAptioFixDrv3-64 (from Clover r4813)
- Using AptioMemoryFix-64 (from Clover r4813), also tried pulling latest build RR24 from github acidanthera/AptioFixPkg
- Tried with "-f UseKernelCache=No" using Rehabman Clover as I was seeing some "Could not load kernel cache" errors using OsxAptioFixDrv3-64
- Tried defining memory modules in SMBIOS so clover shouldn't do ram module discovery
- Tried swapping ram modules over into slot 1+3 instead of 0+2
- Tried running RAM without X.M.P. profile at native DDR4-2133 (running at DDR4-3000 now)
After trying all these things, I have reverted to simply uninstalling EmuVariableUefi-64 now, and no more boot issues - but also no more NVRAM emulation, which is kind of an issue.
Anybody got any suggestions what to try? I have tried finding others with this particular problem, but haven't found any posts on it - typically is a problem with the AptioFix to use, not specifically with nvram emulation being the cause.