<< Solved >> Working machine now gets "Couldn't allocate runtime area" [FIXED]

[tholstro]

I've had a very well working machine for several weeks. Was in the process of adding a second display and just happen to restart. Came back with "Error allocating 0x126b0 pages at" followed by "Couldn't allocate runtime area". I was thinking, surely a second monitor didn't cause this. Unplugged the monitor and same error. Then restarted again and told Clover to start from my backup drive and oddly enough that threw the same error. Overrode default boot drive in BIOS and started Clover from the backup drive and that worked.

Compared internal drive boot configuration to backup drive and they are the same. Differenced the config.plist and they are identical. Then thought I'd just copy the EFI folder from the working backup drive to the internal drive. Same error.

I'm stumped!

Thoughts????

 

[P1LGRIM]

Thoughts????

You have two memory fix drivers.
AptioMemoryFix-64.efi and OsxAptioFix2Drv-free2000.efi both do the same job and are mutually exclusive.
Suggest you remove AptioMemoryFix-64.efi.

 

[tholstro]

You have two memory fix drivers.
AptioMemoryFix-64.efi and OsxAptioFix2Drv-free2000.efi both do the same job and are mutually exclusive.
Suggest you remove AptioMemoryFix-64.efi.

View attachment 397103

Cooler and wiser heads prevail. I totally got in my own way and didn't consider the simplest of things like going back to archives of working configurations!

Thank you so much @P1LGRIM !