Contribute
Register

Unstable boot (Couldn't allocate runtime area) when EmuVariableUefi-64 installed

Status
Not open for further replies.
Joined
Dec 29, 2018
Messages
5
Motherboard
Gigabyte Aorus Z390 Pro
CPU
i9-9900K
Graphics
GTX 1080 Ti
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
Mobile Phone
  1. iOS
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:
  • 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.
 
Maybe OsxAptioFix2Drv-free2000.efi would help.
 
Maybe OsxAptioFix2Drv-free2000.efi would help.

I have not tried OsxAptioFix2Drv-free2000.efi so I guess it's worth a shot, but to my understanding this is an older and non-maintained fix for X99 specifically? Hate to be using something which will not be kept updated?
 
Your choice.
Well, I'll be damned, using OsxAptioFix2Drv-free2000.efi seems to work! :headbang:

Do you know of any consequences of using this rather than the other and newer alternatives?
 
I had exactly the same issue (Gigabyte Aorus Z390-I WiFi). I wanted to enable NVRAM for correct system behaviour (sleep etc).

OsxAptioFix2Drv-free2000.efi fixed the problem. I wonder if it would be possible to port the fixes to OsxAptioFixDrv3-64.efi...
 
Well, I'll be damned, using OsxAptioFix2Drv-free2000.efi seems to work! :headbang:

Do you know of any consequences of using this rather than the other and newer alternatives?
Hey, can you please tell me what drivers do you have exactly installed? I have the same problem, and i have

ApfsDriverLoader-64.efi
AudioDxe-64.efi
DataHubDxe-64.efi
EmuVariableUefi-64.efi
FSInject-64.efi
OsxAptioFix2Drv-free2000.efi
OsxAptioFix3Drv-64.efi
PartitionDxe-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi

and it gives the prohibited sign. Wierd thing is I can install and it works for some time. Ever after some restarts. After one of the restarts it just stops.
 
This is a listing of the UEFI drivers I am using
Code:
  rw-r--r--  micdah  staff    11 KiB  Wed Jan  9 17:25:20 2019    ApfsDriverLoader-64.efi
  rw-r--r--  micdah  staff    44 KiB  Sat May  4 10:39:17 2019    AudioDxe-64.efi
  rw-r--r--  micdah  staff     5 KiB  Wed Jan  9 17:25:20 2019    DataHubDxe-64.efi
  rw-r--r--  micdah  staff    21 KiB  Wed Jan  9 17:25:20 2019    EmuVariableUefi-64.efi
  rw-r--r--  micdah  staff    21 KiB  Sat May  4 10:39:17 2019    FSInject-64.efi
  rw-r--r--  micdah  staff    17 KiB  Wed Jan  9 17:25:20 2019    OsxAptioFix2Drv-free2000.efi
  rw-r--r--  micdah  staff    23 KiB  Wed Jan  9 17:25:20 2019    PartitionDxe-64.efi
  rw-r--r--  micdah  staff     4 KiB  Sat May  4 10:39:17 2019    SMCHelper-64.efi
  rw-r--r--  micdah  staff    29 KiB  Sat May  4 10:39:17 2019    VBoxHfs-64.efi

I see that you are using both `OsxAptioFix2Drv-free2000.efi` and `OsxAptioFix3Drv-64.efi`, I believe you should ever only be using one such driver, among all the different choices.

I rarely see the prohibited sign, it happens once in a while, but a reboot normally "fixes" it.
 
i have

ApfsDriverLoader-64.efi
AudioDxe-64.efi
DataHubDxe-64.efi
EmuVariableUefi-64.efi
FSInject-64.efi
OsxAptioFix2Drv-free2000.efi
OsxAptioFix3Drv-64.efi
PartitionDxe-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi
OsxAptioFix2Drv-free2000.efi and OsxAptioFix3Drv-64.efi both do the same job and are mutually exclusive.
Suggest delete OsxAptioFix3Drv-64.efi.
 
Status
Not open for further replies.
Back
Top