Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

HI all,

I need some help please..

All of a sudden my hackintosh has become very unstable and will randomly freeze.

I'm not sure what's changed for it behave in such a way but it it has been in the last week or two. The problem I am finding is that every freeze is not repeatable, which is frustrating as I cannot seem to narrow down the cause apart from the fact I am working with audio (Pro Tools & Cubase).

Each time the fault thrown up is different as well and it is a Kernal Trap? Not sure what to do at this point or to just rebuild (which I want to avoid)

I have included the two Crash Reports so far in a zip folder

If somebody could offer up some ideas/suggestions, I'd be very grateful.

System is
Z490 Vision D/ i7 10770k/32gb Ram/ M.2 XDATA 1tb/ Radeon RX580 8gb/ TB3 with UAD Apollo

Some questions:

• If you use only Pro Tools (not Cubase), do the crashes occur?
• If you use Cubase (not Pro Tools), do the crashes occur?
• If you neither Pro Tools nor Cubase, do the crashes occur?
• Do you have a bootable backup? If so, when was that backup made? Was it made before the crashes started?

 

[SpinRD]

Some questions:

• If you use only Pro Tools (not Cubase), do the crashes occur?
• If you use Cubase (not Pro Tools), do the crashes occur?
• If you neither Pro Tools nor Cubase, do the crashes occur?
• Do you have a bootable backup? If so, when was that backup made? Was it made before the crashes started?

Hi Casey,

Thank you for your response.

It's not consistent in terms of when the crashes occur for both Pro Tools or Cubase.

- If I use PT, it can be 5 minutes or a couple of hours.
- I decided to do something in Cubase and all seemed fine initially, then it would crash. Again not at particular fixed time or process?
- It has done once or twice when left on to see what was happening idle, it would go to screensaver and I would come back to find it locked and the the fans on.
- I don't have a bootable back up (n00b error). I do however have another M.2 on order and due today/tomorrow with this possibility in mind of creating a new system and then create a back up.

I have had to system performance on the software and it's very low in usage. I wanted to see whether if anything caused a spike but nothing untoward.

As a different test I fired up Logic and strangely that seemed very happy and I was able to open other software (video editing software) without it crashing.

The only thing I can think of that Pro Tools and Cubase have in common, is that they reach to the Internet and I wonder if there is anything in that which might cause the instability? I don't really know how I would test this?

 

[CaseySJ]

Hi Casey,

Thank you for your response.

It's not consistent in terms of when the crashes occur for both Pro Tools or Cubase.

- If I use PT, it can be 5 minutes or a couple of hours.
- I decided to do something in Cubase and all seemed fine initially, then it would crash. Again not at particular fixed time or process?
- It has done once or twice when left on to see what was happening idle, it would go to screensaver and I would come back to find it locked and the the fans on.
- I don't have a bootable back up (n00b error). I do however have another M.2 on order and due today/tomorrow with this possibility in mind of creating a new system and then create a back up.

I have had to system performance on the software and it's very low in usage. I wanted to see whether if anything caused a spike but nothing untoward.

As a different test I fired up Logic and strangely that seemed very happy and I was able to open other software (video editing software) without it crashing.

The only thing I can think of that Pro Tools and Cubase have in common, is that they reach to the Internet and I wonder if there is anything in that which might cause the instability? I don't really know how I would test this?

Because you don't have a bootable back (normally I would get on a pulpit and preach against the unforgivable sin but I'm just exhausted), just perform a fresh installation on the new drive and make sure it is stable -- without installing Pro Tools or Cubase. Then install just one of these tools at a time and use for several hours. If stable, then install the other tool and use it for a few hours.

Don't use Migration Assistant.

If the new system is stable, use Finder to copy your files to the new drive. And reinstall the applications you use (which also means entering the license codes).

 

[SpinRD]

Because you don't have a bootable back (normally I would get on a pulpit and preach against the unforgivable sin but I'm just exhausted), just perform a fresh installation on the new drive and make sure it is stable -- without installing Pro Tools or Cubase. Then install just one of these tools at a time and use for several hours. If stable, then install the other tool and use it for a few hours.

Don't use Migration Assistant.

If the new system is stable, use Finder to copy your files to the new drive. And reinstall the applications you use (which also means entering the license codes).

I appreciate the fact you have given a sermon.. its a hard and fast lesson to learn.

I've got an M.2 caddy as well coming, so I should be good to create the new OS Drive from this and then boot from this if the current OS sees this in the sys pref/start up?

Then I will definitely be creating a bootable back up.

Thank you Casey

 

[CaseySJ]

I appreciate the fact you have given a sermon.. its a hard and fast lesson to learn.

I've got an M.2 caddy as well coming, so I should be good to create the new OS Drive from this and then boot from this if the current OS sees this in the sys pref/start up?

Correct. Once the M.2 SSD in the caddy is formatted at APFS and GUID Partition Map, and the EFI folder is copied to the EFI partition, then it will become bootable. Just follow the build guide in Post 1 and you should be okay.

Then I will definitely be creating a bootable back up.
...

Amen.

 

[bricknewer]

The RX 5700 XT is natively supported in macOS, so no drivers are needed. When the installation with IGPU is complete, then you may install the AMD GPU. At that time we will need to change your Platform ID back to 0x3E980003, so let us know when you're ready.

Thank you for your help so far! I was able to successfully install macOS after removing my GPU.

Having not seen your reply until now, I made a fresh EFI folder with OC-063-VISION-D.zip and used config-AMD-GPU.plist this time. I used your notes from the Edits/Updates section of your OP and copied my existing MLB, System Serial Number, and System UUID into the AMD GPU plist. I then tested it by replacing the EFI folder into my installation USB. After that was successful I replaced my Catalina SSD's EFI folder. No problems so far, and I'm seeing my GPU in About My Mac. I hope this was the right thing to do! If not, I have backups of my old EFI folder and system backup on a separate HD using CCC.

Otherwise, I'm excited to get to many of the post-installation tweaks and fix and bugs/issues that arise!

 

[Higgie]

Thanks @CaseySJ. In my case Windows is launching fine from OC Picker, but the RP05 section looks exactly the same.
Just to let you know, I'm running OC 0.6.4 built two weeks ago, but I don't really think that's the reason.

I'm experiencing the same. I downloaded the new ACPI folder Casey uploaded, replaced my original (after backing it up) and edited my config.plist to include the TB3HP-V2.aml - Windows boots fine from the picker, but still no change. I'm still on OC 0.6.3 from your last update Casey.

Edit: 2nd screenshot added showing what comes up in my PCI section of System Info

 

[CaseySJ]

Thank you for your help so far! I was able to successfully install macOS after removing my GPU.

Having not seen your reply until now, I made a fresh EFI folder with OC-063-VISION-D.zip and used config-AMD-GPU.plist this time. I used your notes from the Edits/Updates section of your OP and copied my existing MLB, System Serial Number, and System UUID into the AMD GPU plist. I then tested it by replacing the EFI folder into my installation USB. After that was successful I replaced my Catalina SSD's EFI folder. No problems so far, and I'm seeing my GPU in About My Mac. I hope this was the right thing to do! If not, I have backups of my old EFI folder and system backup on a separate HD using CCC.

Otherwise, I'm excited to get to many of the post-installation tweaks and fix and bugs/issues that arise!

You’re a fast learner! What you did was perfect.

 

[rd3500]

I am done building the flash drive and I notice a little detail that wanted to make you aware.

I am using the EFI meant to be used with the Intel onboard WiFi-Bluetooth and there is a slight difference from the screenshot in the first message of this thread.

This is what I see in OpenCore Configurator when I open the config.php (Intel GPU version) of the OC 6.3 EFI in this post (which is the one for using onboard WiFi-Bluetooth):

This is what's on the first post of this thread for the same screenshot, there is a #device-id in the previous EFT and no "#" in this one:

I am assuming it will make no difference, just wanted to point it out just in case.

I cannot test it yet as I got all the parts but I am waiting on the power supply coming monday. In the meantime I flashed the thunderbolt chip on the motherboard, worked fine on first try without using supplemental procedure (given that I don't have the power supply yet ).

 

[nss]

Hey, I just started the process of creating a bootable backup and I'm a little confused because I don't know which Volume to pick for SOURCE in Carbon Copy Cloner.
Rons is my new Home folder and my old home folder is probably inside Catalina or Catalina - Data.