Hi there.
I kind of think I have to disagree here. This is not your bad.
There is no rule-book on what will and what won't work. Except things like the stand-out XFX brand RX560 GPU which famously has a non-compatible VBIOS for Hackintosh use. However, some brave souls managed to flash it with a different VBIOS, and got it working. That's an extreme example. Motherboards from the main companies, with standard components, rarely cause such problems.
The Gigabyte Z270X Designare has no "extra" components not featured in other boards, albeit maybe separately, that make it unsuitable for a Hackintosh use. If they started making boards with radically different ways of doing things that would cause problems for Windows too - their main market - and something to avoid.
Yes, there are "Golden Builds" featuring components known to require little or no trickery to get working, but as @pastrychef implies, there is nothing we can see hardware-wise preventing your particular motherboard being used. True, you do have some problems that need identifying and addressing. This is not impossible.
To get to the bottom of this you need to go back to the beginning:
How did you create your UniBeast installer?
Where did you get the installer?
What version macOS?
How did you format your destination drive?
What components did you have attached when performing the installation?
Were there any other drives attached at the time?
That latest screengrab is indicative of a "memory fix" problem. On my old Z270 Gigabyte build I used OsxAptioFix2Drv-64.efi, for what it's worth. I had similar problems recently moving over to OpenCore and our friend @pastrychef pointed me in the right direction. Same solution, different Aptio fix version. He was right
So don't think I'm taking issue with what you are saying, but I am saying we need to know why this build isn't progressing because it really should.
