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

[jerrium]

It should be getting it's power through the PCIe lane then - my wifi card only has two wires, which are the USB data pins. So you may not need to connect it at all.

do you mean the d+ and d- pin are used to transfer data via usb cable?

 

[Ayvan]

Can I ask you which settings do you use in terms of Mhz and timings?
Got the same ram, non-RGB version, and same motherboard.

XMP Profile 1, no any custom settings.

 

[JackGe]

Unfortunately I now have to refer you to the Sleep Aid:

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

@CaseySJ So tried to BOOT using my M2P slotted NVMe Main Clone- Same result as SSD. about 10 mins of idle with no input and computer reboots back to clover menu. Also tried, X.M.P- Disabled which dropped ram from 3200mhz to 2133mhz Still gave me the same result as prior, 10 mins idle, reboot...

www.tonymacx86.com

My Bios version is F7b,SSDT-Disable-CNVW It is not loaded correctly，Can you help me see what wrong?

(AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2020-12-18 17:27:46.205632+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2020-12-18 17:27:46.205898+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [_SB_.PCI0.CNVW._DSM]
2020-12-18 17:27:46.205899+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [_SB_.PCI0.CNVW._DSM]
2020-12-18 17:27:46.206349+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_ALREADY_EXISTS
2020-12-18 17:27:46.206350+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_ALREADY_EXISTS
2020-12-18 17:27:46.207295+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/dswload-462)
2020-12-18 17:27:46.207296+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/dswload-462)
2020-12-18 17:27:46.218717+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Exception: AE_ALREADY_EXISTS,
2020-12-18 17:27:46.218718+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Exception: AE_ALREADY_EXISTS,
2020-12-18 17:27:46.219477+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> During name lookup/catalog
2020-12-18 17:27:46.219477+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> During name lookup/catalog
2020-12-18 17:27:46.220035+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/psobject-310)
2020-12-18 17:27:46.220036+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/psobject-310)
2020-12-18 17:27:46.231577+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Exception: AE_ALREADY_EXISTS,
2020-12-18 17:27:46.231577+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Exception: AE_ALREADY_EXISTS,
2020-12-18 17:27:46.232337+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (SSDT: cnvwoff) while loading table
2020-12-18 17:27:46.232337+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (SSDT: cnvwoff) while loading table
2020-12-18 17:27:46.233088+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/tbxfload-319)
2020-12-18 17:27:46.233089+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/tbxfload-319)
2020-12-18 17:27:46.245240+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2020-12-18 17:27:46.245240+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:
2020-12-18 17:27:46.245506+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 1 table load failures, 20 successful
2020-12-18 17:27:46.245507+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> 1 table load failures, 20 successful
2020-12-18 17:27:46.246282+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/tbxfload-342)
2020-12-18 17:27:46.246283+0800 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20160930/tbxfload-342)

 

[dehjomz]

Gentlemen, apparently Big Sur 11.1 is bugged out for some, including even native users. There are forums on the net about hard crashes on 11.1:
- https://www.imore.com/m1-macbook-air-experiencing-random-reboots-latest-big-sur-update?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+TheIphoneBlog+(iMore)

- https://forums.macrumors.com/threads/big-sur-is-locking-up-my-m1-macbook-air.2270062/

Recently, after installing 11.1, I was having hard errors on my Vision D Z90 with a Thunderbolt dock connected. Really bad errors. The lockups were so bad on the Vision D z490 that at times the system failed to POST upon locking up and the power supply clicking off and on again. Never seen that before. Ever. And I’ve seen a lot being on hackintosh for years. It was so bad that a couple of times, even after disconnecting power for 10 minutes and turning the system back on, it failed to post. The fans would spin up, but nothing would happen, just a reboot loop. This has never happened before, and I've been testing Big Sur since summer. Without the thunderbolt dock connected, the system appeared to be a bit more stable.

Seems to be a Thunderbolt or USB bug in 11.1, or a bug with how macOS handles RAM with the XMP profile turned on. I thought it was a problem with my mobo, but apparently 11.1 is bugged out even for some native users on both Intel and M1 (idk the percentage).

Usually the error occurred after the sleep/wake cycle (sleep for several hours). I was going to get rid of the Vision D, but prior to that drastic action, I clean installed 11.1, updated to 11.2 beta, and gave my RAM a bit more juice, moving from the default 1.35 V on the XMP 3200Mhz profile to 1.392 volts, and so far it’s okay. So far, no more hard crashes after sleep/wake, but I still have a lot more to test.

I don't know if the improved stability comes from 11.2, or giving the RAM a bit more juice, or some combination thereof, but either way, it's good to not have random lockups. I need stability. The system has locked up on me during zoom/webex calls, etc. while I was speaking, which is unacceptable.

 

[CaseySJ]

The USB is commonly used for bluetooth data as well, so it's probably best to not, unless it's a weird wifi card which doesn't use USB for bluetooth

if the usb cable of wifi&bt card is connected to f_usb on mainboard, 99% of hackintosh will have sleep/wake issue. So I think if we can use SYS-FAN to provide power to wifi&bt card instead of f_usb that cause sleep/wake issue.

If you have a WiFi/BT card, please note:

• WiFi is powered by PCIe slot and its data is transferred over PCIe slot.
• Bluetooth is powered by USB port and its data is transferred over USB port.
  • In some cases, Bluetooth might be powered by PCIe slot, but data is always transferred over USB.
• 99% of Hackintoshes with WiFi/BT cards do not have sleep issues.
• Corsair H80i and a few other Corsair products are not recommended on Hackintosh because they cause sleep issues. Corsair Commander Pro definitely needs to be avoided at all costs.

 

[CaseySJ]

My Bios version is F7b,SSDT-Disable-CNVW It is not loaded correctly，Can you help me see what wrong?

We should not use SSDT-Disable-CNVW on Z490 Vision D. But your sleep issue is not due to this. It may be due to a USB device. Please follow the Sleep Aid.

 

[CaseySJ]

do you mean the d+ and d- pin are used to transfer data via usb cable?

Correct.

 

[m4rk0]

XMP Profile 1, no any custom settings.

Cool, so it's stable running at 3600Mhz 16-18-18-38. Thanks!

Get values from ram manual.

Thanks for nothing. Maybe you should have guessed that people can get that kind of information. Maybe there was a specific reason why I asked. Just saying.

 

[hughythomas]

Gentlemen, apparently Big Sur 11.1 is bugged out for some, including even native users. There are forums on the net about hard crashes on 11.1:
- https://www.imore.com/m1-macbook-air-experiencing-random-reboots-latest-big-sur-update?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+TheIphoneBlog+(iMore)

- https://forums.macrumors.com/threads/big-sur-is-locking-up-my-m1-macbook-air.2270062/

Recently, after installing 11.1, I was having hard errors on my Vision D Z90 with a Thunderbolt dock connected. Really bad errors. The lockups were so bad on the Vision D z490 that at times the system failed to POST upon locking up and the power supply clicking off and on again. Never seen that before. Ever. And I’ve seen a lot being on hackintosh for years. It was so bad that a couple of times, even after disconnecting power for 10 minutes and turning the system back on, it failed to post. The fans would spin up, but nothing would happen, just a reboot loop. This has never happened before, and I've been testing Big Sur since summer. Without the thunderbolt dock connected, the system appeared to be a bit more stable.

Seems to be a Thunderbolt or USB bug in 11.1, or a bug with how macOS handles RAM with the XMP profile turned on. I thought it was a problem with my mobo, but apparently 11.1 is bugged out even for some native users on both Intel and M1 (idk the percentage).

Usually the error occurred after the sleep/wake cycle (sleep for several hours). I was going to get rid of the Vision D, but prior to that drastic action, I clean installed 11.1, updated to 11.2 beta, and gave my RAM a bit more juice, moving from the default 1.35 V on the XMP 3200Mhz profile to 1.392 volts, and so far it’s okay. So far, no more hard crashes after sleep/wake, but I still have a lot more to test.

I don't know if the improved stability comes from 11.2, or giving the RAM a bit more juice, or some combination thereof, but either way, it's good to not have random lockups. I need stability. The system has locked up on me during zoom/webex calls, etc. while I was speaking, which is unacceptable.

Hey dehjomz thanks for the update on that. Always useful to know.

With regards to your issues I usually find hard crashes like this, on my setup at least is due to RAM instability.

I've been tweaking my rig during lockdown and it exhibits similiar behaviour to what you described when RAM is not happy.

OS X Catalina seems to be more sensitive to memory instability than Win 10 in this regard.

But I am, still on Catalina 15.5.7 (0.6.4 Opencore Casey config as per guide) so obviously YMMV depending on your setup I guess?

 

[dehjomz]

Hey dehjomz thanks for the update on that. Always useful to know.

With regards to your issues I usually find hard crashes like this, on my setup at least is due to RAM instability.

I've been tweaking my rig during lockdown and it exhibits similiar behaviour to what you described when RAM is not happy.

OS X Catalina seems to be more sensitive to memory instability than Win 10 in this regard.

But I am, still on Catalina 15.5.7 (0.6.4 Opencore Casey config as per guide) so obviously YMMV depending on your setup I guess?

Happy to help the community.

And yeah macOS is seemingly more sensitive to memory stability than windows, although even windows at times has its own problems with memory.