[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[bluepr0]

If you use Carbon Copy Cloner, it does a file-by-file copy instead of a so-called "sector" by "sector" copy. This means:

• Before using the new 250GB SSD, we need to run Disk Utility and format the drive as:
  • Type: APFS
  • Scheme: GUID Partition Map <-- this is very important
  • This creates a large 250GB APFS container (you can think of it as a partition)
  • Inside the container, macOS can dynamically create and resize multiple volumes
    • Recovery Disk is one of those volumes
    • Mojave boot disk is one of those volumes
    • Preboot disks that you often see are also one of these volumes
    • When macOS performs a software update, it creates an Install macOS volume
  • All of these volumes are created inside the single APFS container
• Then we run CCC and let it "clone" the 128GB onto the 250GB SSD.
  • CCC will copy all the volumes from the source disk to the destination disk
  • CCC will probably adjust the min-size and quota parameters of some volumes to better fit the destination disk

So in other words, just format the destination disk in Disk Utility and run Carbon Copy Cloner. It will take care of all the small details.

Thanks so much @CaseySJ

 

[oopsmybad]

I hate to ask a bunch of bonehead questions, or ask something that's been explained in more detail in other posts. However, I've done a bunch of reading and am still trying to figure out...

What's the "best" way to connect a new (but hereto unpurchased) 4K to monitor to my setup (Designaire Z390 + RX 580 + Fractial Design R6 USB-C)?

@CaseySJ - if I read everything correctly, your Designo has inputs for DisplayPort, HDMI and a (DisplayPort over?) USB-type C connector. Are you using straight DisplayPort out of the RX 580 to your monitor?

Another question - if HS08/HS09 are disabled, and the type C connectors on the back are controlled by Thunderbolt, does that mean that "DisplayPort over USB-C" doesn't work, or does it work? I see 4K monitors advertised as being "USB-C" and I assume that means "DisplayPort 1.4 over a USB type-c connector", and not "USB 3.1 v2 over a USB type-C connector" or "Thunderbolt 3 over a USB type C connector" (unless the monitor is specifically labeled Thunderbolt, of course.)

Since I have the Fractial Design R6 USB-C case, where the type C connector on the front panel is wired up as SS01, that physical type C connector on the front panel only supports "USB 3.1 v2" - and not DisplayPort or Thunderbolt over USB type C, correct?

Besides figuring out all the port options, I'm also thinking that...
1) I don't need 5K, but do use Final Cut Pro and would like to take full advantage of any hardware-based acceleration. (I think that happens in pretty much every case, since I'm set up as "headless".)
2) It's unlikely, but theoretically possible that I might boot into Windows and play a game or two from time to time. Having some connection methodology that supports AMD's FreeSync would be neat-o.

I know everyone's requirements are unique, and no one configuration best suits everyone - but before I buy anything, I thought I'd humbly request some opinions. Thanks in advance!

 

[FriFlo]

@CODYQX4
@bielxxx

You guys have tremendously helped me in getting the 128GB of RAM working. However, running MemTest I ran into some problems ... these are the results:

Spoiler

Memtest version 4.22 (64-bit)

Copyright (C) 2004 Charles Cazabon

Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)

Licensed under the GNU General Public License version 2 only



Mac OS X 10.14.6 (18G103) running in multiuser mode

Memory Page Size: 4096

System has 16 Intel core(s) with SSE

Requested memory: 117683MB (123400192000 bytes)

Available memory: 117683MB (123400192000 bytes)

Allocated memory: 117683MB (123400192000 bytes) at local address 0x000000010c7cf000

Attempting memory lock... locked successfully

Partitioning memory into 2 comparison buffers...

Buffer A: 58841MB (61700096000 bytes) starts at local address 0x000000010c7cf000

Buffer B: 58841MB (61700096000 bytes) starts at local address 0x0000000f6a19b000



Running 2 test sequences... (CTRL-C to quit)



Test sequence 1 of 2:



Running tests on full 117683MB region...

Stuck Address : ok

Linear PRN : testing 2 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Expected Data: 0xd504e4667409d5ae, Actual Data: 0xd504e4667409d5b2



Running comparison tests using 58841MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : testing 14 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000005



Block Sequential : testing 3 of 256



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0202020202020202, BUFB Data: 0x0202020202020208



Checkerboard : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xaaaaaaaaaaaaaaaa, BUFB Data: 0xaaaaaaaaaaaaaab1



Bit Spread : testing 17 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000050000, BUFB Data: 0x0000000000050002



Bit Flip : testing 7 of 512



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffe, BUFB Data: 0xffffffff00000010



Walking Ones : testing 2 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffd, BUFB Data: 0xffffffffffffffff



Walking Zeroes : testing 8 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000080, BUFB Data: 0x0000000000000087





Test sequence 2 of 2:



Running tests on full 117683MB region...

Stuck Address : testing 1 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Actual Data: 0x00000013b122b005



Linear PRN : testing 1 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Expected Data: 0x626b399ebae87bd0, Actual Data: 0x626b399ebae87bd1



Running comparison tests using 58841MB buffers...

Random Value :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x6fa77fc177cda0e5, BUFB Data: 0x6fa77fc177cda0e7



Compare XOR :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x207aea51c832b842, BUFB Data: 0x207aea51c832b840



Compare SUB :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xc97eea60c83cb6fc, BUFB Data: 0xc97eea60c83cb6fb



Compare MUL :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x66b7058da4d3e0c0, BUFB Data: 0x66b7efd6d5666cf0



Compare DIV :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000007



Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000003



Block Sequential : testing 2 of 256



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0101010101010101, BUFB Data: 0x0101010101010102



Checkerboard : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xaaaaaaaaaaaaaaaa, BUFB Data: 0xaaaaaaaaaaaaaab1



Bit Spread : testing 1 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000005, BUFB Data: 0x000000000000000a



Bit Flip : testing 2 of 512



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000001, BUFB Data: 0x000000000000000f



Walking Ones : testing 3 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffb, BUFB Data: 0xfffffffffffffffc



Walking Zeroes : testing 6 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000020, BUFB Data: 0x0000000000000021





*** Address Test Failed *** One or more DIMM address lines are non-functional.

Execution time: 1993 seconds.

This is what my configuration on Clover looks like (it goes on with Slot 6 and 7, as I have full 128GB of memory installed):

To be sure: this is the Memtest I ran (as recommended in the trouble shooting guide):

MemTest for Mac OS X Tests your RAM

If you have recently upgraded your Mac RAM, or if you are experiencing strange system crashes, it’s a good idea to test your memory modules integrity using a free tool called memtest. Essenti…

osxdaily.com

I don't think the RAM is not working hardware wise, as I also did a full memory test running windows and no mistakes were showing up. Could these mistakes be just due to the wrong attribution of 8 slots vs the actual 4 slots? Did you also do that Memtest? What were the results?

 

[CaseySJ]

I hate to ask a bunch of bonehead questions, or ask something that's been explained in more detail in other posts. However, I've done a bunch of reading and am still trying to figure out...

What's the "best" way to connect a new (but hereto unpurchased) 4K to monitor to my setup (Designaire Z390 + RX 580 + Fractial Design R6 USB-C)?

For 4K monitors I prefer the use of DisplayPort 1.2 or HDMI 2.0, both of which are available from the RX 580 and support 4K at 60Hz.

@CaseySJ - if I read everything correctly, your Designo has inputs for DisplayPort, HDMI and a (DisplayPort over?) USB-type C connector. Are you using straight DisplayPort out of the RX 580 to your monitor?

Yes I'm using DisplayPort out of the RX 580. If I understand correctly, just having a USB-C 3.1 Gen 2 port does not mean it is wired up to drive a USB-C monitor. The same holds for Thunderbolt monitors. If a graphics chip is not connected to that port then a video signal will not be produced on that port. Both Thunderbolt and USB-C are capable of carrying DisplayPort but only when a graphics chip is attached to it.

Another question - if HS08/HS09 are disabled, and the type C connectors on the back are controlled by Thunderbolt, does that mean that "DisplayPort over USB-C" doesn't work, or does it work?

A Thunderbolt 3 port is like a Swiss Army Knife with multiple pins for carrying multiple protocols. We can disable the USB 2 protocol without affecting the port's ability to carry DisplayPort video.

I see 4K monitors advertised as being "USB-C" and I assume that means "DisplayPort 1.4 over a USB type-c connector", and not "USB 3.1 v2 over a USB type-C connector" or "Thunderbolt 3 over a USB type C connector" (unless the monitor is specifically labeled Thunderbolt, of course.)

Because DisplayPort 1.2 supports 4K at 60Hz, most 4K monitors are DP 1.2 (even if they have a USB-C video input [not Thunderbolt]). When we step up to 5K and 8K monitors we need DP 1.4. The Alpine Ridge Thunderbolt controller does not support DP 1.4. But Titan Ridge on the Designare fully supports DP 1.4.

Apple, however, plays a trick with 5K monitors by sending two DP 1.2 streams to the monitor at the same time. Dual DP streams are supported by the Thunderbolt spec, but each stream is typically intended for a different monitor. On a 5K Apple computer, one stream paints the left half of the 5K monitor and the other paints the right half. In this way Apple can send more color information to the monitor even compared to DP 1.4. In other words, two DP 1.2 streams can be combined to generate an even more powerful signal than DP 1.4.

USB-C monitors, however, are different from Thunderbolt monitors and not interconnectable (as far as I know).

Since I have the Fractial Design R6 USB-C case, where the type C connector on the front panel is wired up as SS01, that physical type C connector on the front panel only supports "USB 3.1 v2" - and not DisplayPort or Thunderbolt over USB type C, correct?

Correct -- just because there is a USB-C port it does not mean that it's internally wired to a GPU!

Besides figuring out all the port options, I'm also thinking that...
1) I don't need 5K, but do use Final Cut Pro and would like to take full advantage of any hardware-based acceleration. (I think that happens in pretty much every case, since I'm set up as "headless".)

Both the AMD GPU and internal UHD630 provide hardware acceleration. The AMD GPU (RX 580) is significantly faster.

2) It's unlikely, but theoretically possible that I might boot into Windows and play a game or two from time to time. Having some connection methodology that supports AMD's FreeSync would be neat-o.

Your RX 580 is already FreeSync capable with AMD's video drivers in Windows. You would just need a FreeSync-capable monitor.

 

[FriFlo]

@CODYQX4
@bielxxx

You guys have tremendously helped me in getting the 128gb of ram working. However, running MemTest I ran into some problems ... these are the results:

Spoiler

Memtest version 4.22 (64-bit)

Copyright (C) 2004 Charles Cazabon

Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)

Licensed under the GNU General Public License version 2 only



Mac OS X 10.14.6 (18G103) running in multiuser mode

Memory Page Size: 4096

System has 16 Intel core(s) with SSE

Requested memory: 117683MB (123400192000 bytes)

Available memory: 117683MB (123400192000 bytes)

Allocated memory: 117683MB (123400192000 bytes) at local address 0x000000010c7cf000

Attempting memory lock... locked successfully

Partitioning memory into 2 comparison buffers...

Buffer A: 58841MB (61700096000 bytes) starts at local address 0x000000010c7cf000

Buffer B: 58841MB (61700096000 bytes) starts at local address 0x0000000f6a19b000



Running 2 test sequences... (CTRL-C to quit)



Test sequence 1 of 2:



Running tests on full 117683MB region...

Stuck Address : ok

Linear PRN : testing 2 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Expected Data: 0xd504e4667409d5ae, Actual Data: 0xd504e4667409d5b2



Running comparison tests using 58841MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : testing 14 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000005



Block Sequential : testing 3 of 256



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0202020202020202, BUFB Data: 0x0202020202020208



Checkerboard : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xaaaaaaaaaaaaaaaa, BUFB Data: 0xaaaaaaaaaaaaaab1



Bit Spread : testing 17 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000050000, BUFB Data: 0x0000000000050002



Bit Flip : testing 7 of 512



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffe, BUFB Data: 0xffffffff00000010



Walking Ones : testing 2 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffd, BUFB Data: 0xffffffffffffffff



Walking Zeroes : testing 8 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000080, BUFB Data: 0x0000000000000087





Test sequence 2 of 2:



Running tests on full 117683MB region...

Stuck Address : testing 1 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Actual Data: 0x00000013b122b005



Linear PRN : testing 1 of 16



FAILURE! Data mismatch at local address 0x00000013b122b000

Expected Data: 0x626b399ebae87bd0, Actual Data: 0x626b399ebae87bd1



Running comparison tests using 58841MB buffers...

Random Value :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x6fa77fc177cda0e5, BUFB Data: 0x6fa77fc177cda0e7



Compare XOR :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x207aea51c832b842, BUFB Data: 0x207aea51c832b840



Compare SUB :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xc97eea60c83cb6fc, BUFB Data: 0xc97eea60c83cb6fb



Compare MUL :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x66b7058da4d3e0c0, BUFB Data: 0x66b7efd6d5666cf0



Compare DIV :



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000007



Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000000, BUFB Data: 0x0000000000000003



Block Sequential : testing 2 of 256



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0101010101010101, BUFB Data: 0x0101010101010102



Checkerboard : testing 2 of 64



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xaaaaaaaaaaaaaaaa, BUFB Data: 0xaaaaaaaaaaaaaab1



Bit Spread : testing 1 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000005, BUFB Data: 0x000000000000000a



Bit Flip : testing 2 of 512



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000001, BUFB Data: 0x000000000000000f



Walking Ones : testing 3 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0xfffffffffffffffb, BUFB Data: 0xfffffffffffffffc



Walking Zeroes : testing 6 of 128



FAILURE! Data mismatch at local BUFA address 0x000000055385f000, BUFB address 0x00000013b122b000

BUFA Data: 0x0000000000000020, BUFB Data: 0x0000000000000021





*** Address Test Failed *** One or more DIMM address lines are non-functional.

Execution time: 1993 seconds.

This is what my configuration on Clover looks like (it goes on with Slot 6 and 7, as I have full 128gb of memory installed):

View attachment 428410

To be sure: this is the Memtest I ran (as recommended in the trouble shooting guide):

MemTest for Mac OS X Tests your RAM

If you have recently upgraded your Mac RAM, or if you are experiencing strange system crashes, it’s a good idea to test your memory modules integrity using a free tool called memtest. Essenti…

osxdaily.com

I don't think the RAM is not working hardware wise, as I also did a full memory test running windows and no mistakes were showing up. Could these mistakes be just due to the wrong attribution of 8 slots vs the actual 4 slots? Did you also do that Memtest? What were the results?

Wait ... I just did the same MemTest on my last backup on the external SSD. This was done before "Going the Extra Mile". Looks like the MemTest is going just fine there, so, some of the other steps must have screwed something up. It could only have been installing VirtualSMC instead of FakeSMC or Injecting Audio and Enabling On-Board HDMI (with Hackintool - third method) ...
I am gonna revert to the backup and test that.

 

[jmenco]

Hi people,

First time posting something so sorry if I do something wrong

I've just finished building and installing this build, but with a 9900K as an audio-post workstation, successfully running Apogee Ensemble via Thunderbolt 3->2 adapter and UAD Apollo x8 via Thunderbolt 3.

Just a quick tip for people experiencing problems with flakey PCIe detection. Try the iMacPro 1,1 system definition.
I'm using a Black Magic Intensity pro and TP-link wifi card which where both being recognized only half of the boots. The new sys. def. seems to fix this.
Also this fixes the problem where you can't preview and open jpeg's natively.

 

[genzai]

What else could be better except native 5K and larger text/icons? But the last also doesn't go together?

You seem really confused about HiDPI. You keep asking for larger text and icons. That is what HiDPI does, it maintains the true resolution of the monitor but draws the UI elements, text, etc larger (and more detailed than if you had a lower resolution on a similar sized display). There is nothing lacking on hackintosh, it is the same behavior on a real mac. That is how HiDPI mode is intended to work and it is probably the best solution to the issue of larger, high resolution monitors and "retina" displays. Apple has received a lot of accolade for how it handles HiDPI compared to for instance windows. the monitor is specifically intended to be used at 3360x1417 HiDPI. It is the default resolution when you plug in a real mac and it is the best balance of screen real-estate and usability. The screen still display full 5K2K its just being upscaled to look like 3360x1417, you don't lose any pixels. Before these 5K monitors came along, 34" widescreen monitors were native resolution at 3440x1440, so you see the "UI looks like" 3360x1417 is very close to this and looks correct. And because the monitor is actually displaying higher density 5K2K resolution, this 3360x1417 UI is much sharper and more attractive than on the older/cheaper 34" monitors.

You also do not need a thunderbolt connection to run calibrations, that is what the USB port is for.

g\

 

[skroutz999]

You seem really confused about HiDPI. You keep asking for larger text and icons. That is what HiDPI does, it maintains the true resolution of the monitor but draws the UI elements, text, etc larger (and more detailed than if you had a lower resolution on a similar sized display). There is nothing lacking on hackintosh, it is the same behavior on a real mac. That is how HiDPI mode is intended to work and it is probably the best solution to the issue of larger, high resolution monitors and "retina" displays. Apple has received a lot of accolade for how it handles HiDPI compared to for instance windows. the monitor is specifically intended to be used at 3360x1417 HiDPI. It is the default resolution when you plug in a real mac and it is the best balance of screen real-estate and usability. The screen still display full 5K2K its just being upscaled to look like 3360x1417, you don't lose any pixels. Before these 5K monitors came along, 34" widescreen monitors were native resolution at 3440x1440, so you see the "UI looks like" 3360x1417 is very close to this and looks correct. And because the monitor is actually displaying higher density 5K2K resolution, this 3360x1417 UI is much sharper and more attractive than on the older/cheaper 34" monitors.

You also do not need a thunderbolt connection to run calibrations, that is what the USB port is for.

g\

Yes after a lot of reading I now understood what is hidpi and how it works! Im using right now a UI at 2560x1080 and Im very happy with it. Yesterday will all these tests and testing many color profiles such as HDR and DCI-P3 and also doing different calibrations with different profiles, my eyes got tired! I will keep using this resolution for a few days and then I will change it back to 3360x1417 to check if it suits my needs! Im super happy with my new monitor!!

Everything is super crisp and sharp! Today I worked at Photoshop and fcpx and the experience with this monitor was amazing!!

 

[Ploddles]

The real cause of the error is probably something before the "keybag" error message. In any case, some things to try:

• Use MultiBeast 11.3.0. If this is already the version that was used, update Clover by download and running this file. It may be necessary to boot from the USB install disk or mount the NVMe into a different working system.
• In BIOS:
  • Is IGFX (IGPU) enabled?
  • If so, is DVMT-PreAlloc set to 64MB or larger?
  • Is Above 4G Decoding enabled?

@CaseySJ Thanks.

Turns out it was a corrupt EFI partition. I managed to boot up in Windows and use DiskPart to delete the EFI partition.

Rerunning MultiBeast to recreate it and install Clover sorted it all out and I am now up and running.

Thanks for your initial guide, and its subsequent updates, for getting it all working.

 

[billybuck092]

Just wanted to post a quick thank you for the build. I've replaced my Mac Pro (2013) with the following:

• Gigabyte Z390 Designare WiFi
• Intel Core i7-9700K
• Deepcool Gammaxx L240 CPU Cooler 6 ultra-bright RGB LED lights
• G.SKILL Ripjaws V Series 64GB (4x16GB) DDR4 3200MHz CL16 Dual Channel Memory Kit
• HP EX950 M.2 1TB PCIe 3.1 x4 NVMe 3D TLC NAND Internal Solid State Drive
• Corsair TMX Series TM750x 80 Plus Gold Semi-Modular Power Supply
• Cooler Master H500 ATX Mid-Tower Case
• Deepcool RGB LED Strip
• Installation
• Fenvi T919 BCM94360CD WiFi & BT 4.0 Card
• Sapphire 11265-05-20G Radeon PULSE RX 580 8GB GDDR5 DUAL HDMI
• Dell 32" Display (UP3216Q )
• 2 - Akitio Thunder3 Quad X 4-Bay Thunderbolt 3 Enclosures
• 4 - Apple Thunderbolt 2 to 3 Adapters
• 2 - StarTech Thunderbolt 2 Cables

Everything works perfectly. For those who are interested, I used the Thunderbolt 2 cables for their length, I couldn't find any Thunderbolt 3 cables over 2m. The Apple adapters are at each end and work flawlessly. I am running SoftRAID for an 8 drive RAID6 array.

Performance details: