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

[CaseySJ]

...
I don't but I have a Windows boot drive... I can run Memtest or ideally something easier
...

Running Windows is actually a good test. During my experience with faulty memory, Memtest did not help, but Windows would routinely crash. This convinced me that a hardware component was at fault. I had another pair of DIMMs on hand so my first thought was to replacement memory -- and that in fact turned out to be the root cause.

So running Windows is a good idea. If Windows is stable for long periods of time (including idle periods), then there is a reduced chance that hardware is at fault.

 

[pierpaolo2395]

Here are two more experiments to try:

Experiment #1:

• Replace SSDT-TbtOnPch-ThinkPad-T480-OC-V2.aml with the new version attached
• This one requires:
  • Find: 5f 4c 36 46
  • Replace: 58 4c 36 46
  • Comment: Replace _L6F with XL6F
• Reboot and test Thunderbolt

Experiment #2:

• Uncheck V2 and install the new V3 attached below: SSDT-TbtOnPch-ThinkPad-T480-OC-V3.aml
  • This means (a) copy file into EFI/OC/ACPI and (b) add new entry to config.plist --> ACPI --> Add
• Uncheck the previous ACPI patch ("Replace _L6F with XL6F") and use this one instead:
  • Find: 54 42 4E 46
  • Replace: 58 42 4E 46
  • Comment: Replace TBNF with XBNF
• Reboot and test Thunderbolt

Hi @CaseySJ

I wanted to inform you that through some changes to the EFI, which probably was not working correctly, everything is now working correctly.
Only thing that doesn't come out is DP video via HDMI, and audio via USBc
Everything else works fine, including Hotplug TB3
AppleVTD it remained disabled, as it was causing problems with the TB3 port

Thanks so much for your invaluable help.

 

[jiffyslot]

Thanks so much @mustang.dvs ! This thread is huge.

I wonder if anyone can help me. So with both @CaseySJ 's Opencore EFI and the one by seven-of-eleven, I'm having the same issue:

Computer is fine when being used, but when left idle for 15mins, it freezes. Then, it either restarts after a minute, or it goes into sleep (display turns off) and then restarts when I try to wake it.

To prevent crashing I have a macro that runs after 3mins of idle, that prevents sleep.

I also tried enabling SSDT-USBW.aml and USBWakeFixup.kext on Casey's build.

Opencore 0.8.3, Monterey 12.5.1, iMac19,1, Gigabyte Z390 Designare, Sapphire Vega 64, 9900k, Kingston HyperX Predator 64 GB (4 x 16 GB) DDR4-3600, no overclocking, BIOS F9i, Crucial MX500

Just for fun, disable all sleep and "energy saver" options in System Preferences and see if that makes any difference. Of course, if you have an external audio interface, don't let your system "save energy" when it is connected and powered on.

 

[Lukey1979]

Hi @CaseySJ

Long time no issues
Until recently. I know you shouldn't be the first point of call for this however my googling has not uncovered any solutions. My issue is with Liquidctl, once upon a time this was running flawlessly with scripts to start it at boot and set my colours and fan speeds, however, recently I have discovered that I am now getting the below:

lukesummerscales@Lukes-iMac ~ % liquidctl status

ERROR: could not open Gigabyte RGB Fusion 2.0 8297 Controller, possibly due to insufficient permissions

ERROR: could not open NZXT Kraken X (X42, X52, X62 or X72), possibly due to insufficient permissions

lukesummerscales@Lukes-iMac ~ %

I am not sure what has happened here but I am no longer able to control these two devices. Have you seen this before and have others possibly found a solution to this? I don't believe I have made any system changes with OC nor have I changed using any of my original KEXTS other than when updates have been released.

 

[CaseySJ]

Hi @CaseySJ

Long time no issues
Until recently. I know you shouldn't be the first point of call for this however my googling has not uncovered any solutions. My issue is with Liquidctl, once upon a time this was running flawlessly with scripts to start it at boot and set my colours and fan speeds, however, recently I have discovered that I am now getting the below:

lukesummerscales@Lukes-iMac ~ % liquidctl status

ERROR: could not open Gigabyte RGB Fusion 2.0 8297 Controller, possibly due to insufficient permissions

ERROR: could not open NZXT Kraken X (X42, X52, X62 or X72), possibly due to insufficient permissions

lukesummerscales@Lukes-iMac ~ %

I am not sure what has happened here but I am no longer able to control these two devices. Have you seen this before and have others possibly found a solution to this? I don't believe I have made any system changes with OC nor have I changed using any of my original KEXTS other than when updates have been released.

This sounds like an Accessibility denial. Some basic questions:

• Which version of macOS?
• Which version of Liquidctl?
• Have you attempted to update homebrew?

 

[Lukey1979]

This sounds like an Accessibility denial. Some basic questions:

• Which version of macOS?
• Which version of Liquidctl?
• Have you attempted to update homebrew?

Hi @CaseySJ

Im using macOS Monterey 12.5.1 with Liquidctl v1.10.0 (I had the same issue with the previous version and then updated to the current version which produces the same error)
I have also updated Homebrew to the latest version.

 

[MusicMan]

Running Windows is actually a good test. During my experience with faulty memory, Memtest did not help, but Windows would routinely crash. This convinced me that a hardware component was at fault. I had another pair of DIMMs on hand so my first thought was to replacement memory -- and that in fact turned out to be the root cause.

So running Windows is a good idea. If Windows is stable for long periods of time (including idle periods), then there is a reduced chance that hardware is at fault.

I've actually spent a couple weeks running Windows (cumulatively... most sessions are a few hours but some are a few days) and haven't had a single crash.

Edit: I just let Windows run idle for 80 minutes and no crash. Then I realized Sleep was off, so I turned it on and it woke from sleep just fine after 20mins. On macOS it happens consistently after 10-15 minutes (sometimes it goes into sleep, sometimes it just crashes and eventually restarts).

Just for fun, disable all sleep and "energy saver" options in System Preferences and see if that makes any difference. Of course, if you have an external audio interface, don't let your system "save energy" when it is connected and powered on.

(see attached) I actually have them all off already and I do have an external audio interface (just added to signature) but I didn't realize that's something to consider here? Could you explain that to me?

 

[CaseySJ]

Hi @CaseySJ

Im using macOS Monterey 12.5.1 with Liquidctl v1.10.0 (I had the same issue with the previous version and then updated to the current version which produces the same error)
I have also updated Homebrew to the latest version.

I’ll run some tests in the morning on the same version of macOS.

 

[jiffyslot]

I've actually spent a couple weeks running Windows (cumulatively... most sessions are a few hours but some are a few days) and haven't had a single crash.

Edit: I just let Windows run idle for 80 minutes and no crash. Then I realized Sleep was off, so I turned it on and it woke from sleep just fine after 20mins. On macOS it happens consistently after 10-15 minutes (sometimes it goes into sleep, sometimes it just crashes and eventually restarts).


(see attached) I actually have them all off already and I do have an external audio interface (just added to signature) but I didn't realize that's something to consider here? Could you explain that to me?

Sure, depending on the audio device and your various software, there's often the issue of drivers and/or playback engines going bonkers when the device that's connected to them "sleeps" or is otherwise disconnected or shut off. Sometimes there can be issues with iLoks and other dongles getting ejected during sleep. As a Pro Tools user, I never let my machine sleep. It's either On or Off.

 

[zipb]

Read/write speed with Sonnet M2 4x4 with 4 x 2TB Samsung 980 Pro in Raid-0. Using 8 PCIe lanes.

Testing for a client. In Windows, read/write is twice as slow even with 16 lanes?