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

CaseySJ said:

Tweaktown is posting a review now? When the Z590 Vision D is coming out and the Z490 Vision D is sunsetting? Ah, such impeccable timing?!!?

Click to expand...

CaseySJ said:

The Hackintool screenshot shows that the USB SSDT for Vision D is in effect. To map USB ports on a new board we must enable all USB ports. In the screenshot we can see that HS01, HS02, HS08, HS13, HS14, SS02, SS08, etc. are missing because the Vision D SSDT removes them.

You must disable the Vision D USB SSDT and reboot. Then proceed with port discovery process.

Click to expand...

ralle12345 said:

Hi @CaseySJ,
I got distracted by other things, but now I have setup my USB properly.

View attachment 510497

I don't know what's behind HS13 and HS14, though.

Still my Hackintosh goes to sleep and stays asleep alright. But, when it should wake, the screen stays dark, and the display goes back to standby-mode.

Click to expand...

• In “Device Properties” section of your config.plist, is “device-id” being injected in the same place where “aapl,ig-platform-id” is injected?
• If so, what value of device ID is being injected?

CaseySJ said:

Others are also reporting this problem when using the iGPU. One more thing to check:

• In “Device Properties” section of your config.plist, is “device-id” being injected in the same place where “aapl,ig-platform-id” is injected?
• If so, what value of device ID is being injected?

Click to expand...

ralle12345 said:

Is this what I should be looking for?

View attachment 510503

Click to expand...

[GUIDE] General Framebuffer Patching Guide (HDMI Black Screen Problem)

Thank you for the guide! I was able to get all three of my connectors working with it. I have an ASUS Prime Z490M-PLUS with an Intel i7-10700K. I am using opecore 66 and WEG 1.4.7, my settings are pasted below. EDIT: Forget the physical connector types, con0 / index 1 is DP, con1 / index 2...

www.tonymacx86.com

hughythomas said:

Hi guys sorry to trouble you.

I'm getting hard freezing in Big Sur (and have been doing for a while now) with no real remedy despite a lot of tweaking my end to try and fix this. Unfortunately, its pretty much gotten to the point where the computer is unusable for work as its hard freezing so often.

This is the error report upon rebooting:

panic(cpu 0 caller 0xffffff80075ee1e6): Kernel trap at 0xffffff80054e2179, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80054e2179, CR3: 0x000000000c634000, CR4: 0x00000000003626e0
RAX: 0x000000000005b416, RBX: 0xffffff8008293de0, RCX: 0x0000000000000005, RDX: 0x00000000000001c8
RSP: 0xffffffc0fcda3f50, RBP: 0xffffffc0fcda3f80, RSI: 0x0000000000000002, RDI: 0xffffff80082050f8
R8: 0x0000000000000000, R9: 0x0000000000000014, R10: 0x0000000000000001, R11: 0x0000000000000001
R12: 0xffffff80082a5300, R13: 0xffffff80082942a8, R14: 0x0000000000000000, R15: 0xffffff80082050f8
RFL: 0x0000000000010202, RIP: 0xffffff80054e2179, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff80054e2179, Error code: 0x0000000000000010, Fault CPU: 0x0, PL: 1, VF: 5

Backtrace (CPU 0), Frame : Return Address
0xffffffc0fcda3970 : 0xffffff80074bab4d mach_kernel : _handle_debugger_trap + 0x3dd
0xffffffc0fcda39c0 : 0xffffff80075fd7e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffc0fcda3a00 : 0xffffff80075ede1a mach_kernel : _kernel_trap + 0x55a
0xffffffc0fcda3a50 : 0xffffff800745fa2f mach_kernel : _return_from_trap + 0xff
0xffffffc0fcda3a70 : 0xffffff80074ba3ed mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffc0fcda3b90 : 0xffffff80074ba6d8 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffffc0fcda3c00 : 0xffffff8007cbef9a mach_kernel : _panic + 0x54
0xffffffc0fcda3c70 : 0xffffff80075ee1e6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffc0fcda3df0 : 0xffffff80075edecd mach_kernel : _kernel_trap + 0x60d
0xffffffc0fcda3e40 : 0xffffff800745fa2f mach_kernel : _return_from_trap + 0xff
0xffffffc0fcda3e60 : 0xffffff80054e2179
0xffffffc0fcda3f80 : 0xffffff80074e2348 mach_kernel : _idle_thread + 0x48
0xffffffc0fcda3fa0 : 0xffffff800745f13e mach_kernel : _call_continuation + 0x2e

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=80

Mac OS version:
20D74

Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x0000000007200000
KernelCache base: 0xffffff8007400000
Kernel slide: 0x0000000007210000
Kernel text base: 0xffffff8007410000
__HIB text base: 0xffffff8007300000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1959961233069
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000001c856cb0ec3
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000012471a33fe 0x0000000000000000


I know this is a bit of a stab in the dark but is there anyone who can help me here with this? I've been loosening ram timings and downclocking in order to try and fix but it still remains.

Strangely enough the computer is stress test stable in Windows (according to Intel Xtreme Tuning Utility & Karhu's RAM tester).

The only thing I can think of now is a problem with my EFI folder as the computer runs perfectly in Windows for hours of gaming. I've attached it herewith ***unsanitised*** in case the EFI truly is to blame.

I use Big Sur however for Logic Pro X for my album work and am stuck with this machine for the time being...

Thank you in advance you wonderful lot!

Click to expand...

• How frequently does this happen?
• When did it first start?
• Does it happen if you don't use Logic Pro?
  • This is a tricky one I know because Logic Pro is the reason for this system's existence
  • But if it's possible to use the system for some hours without using Logic Pro, it might provide helpful information
• Because you can save your BIOS settings to a profile, have you tried F7 (Load Optimized Defaults) to set everything back to default parameters, then just made the BIOS changes necessary for booting macOS?
  • This will undo all overclocking and other mods.
  • But you can load a saved profile to restore those settings later on.

CaseySJ said:

Some questions to help us characterize the problem:

• How frequently does this happen?
• When did it first start?
• Does it happen if you don't use Logic Pro?
  • This is a tricky one I know because Logic Pro is the reason for this system's existence
  • But if it's possible to use the system for some hours without using Logic Pro, it might provide helpful information
• Because you can save your BIOS settings to a profile, have you tried F7 (Load Optimized Defaults) to set everything back to default parameters, then just made the BIOS changes necessary for booting macOS?
  • This will undo all overclocking and other mods.
  • But you can load a saved profile to restore those settings later on.

Click to expand...

hughythomas said:

1. Its happened 4 times today and funnily enough it never happens in Logic! It happens mostly when doing very mundane tasks like web browsing or even just simply in Finder (which made me think it must be the RAM?).
2. It first started about the time of 0.6.5 release
3. I will try loading optimized defaults and see mate thank you for the suggestion

Click to expand...

CaseySJ said:

Another suggestion is to run Activity Monitor and sort the list by % CPU. Then keep the window running while you perform those "mundane tasks"! When a crash occurs, note the names of the top 1 or 2 items in the Activity Monitor list.

Click to expand...