Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

[Hacintosh2015]

Is Lightroom an official release or a cracked one? Which version are you using? Are you under Monterey or Ventura? Have you tried to re-install PS & LR ?

The Lightroom is an official release not a cracked version. I'm using the latest version. My computer is on Ventura. I tried to uninstall Ps & LR. Still is the same. So I will reinstall Mac Ventura again. But I don't know my EFI is good or not but everything run fine, only LR is not working. And what did you config your system MacPro 1,1 or MacPro 7,1?

 

[rethua]

Hi there! First of, such a nice build and thanks for all the efforts @CaseySJ. I am willing to build a new hackintosh and have been watching the topic for a while now before buying all the parts and starting.

Since the new generation of the ProArt Creator motherboard is on it's way (ASUS ProArt Z790-CREATOR WIFI), I am thinking if I should go for Z790 + i7 13700K. Not sure if it is worth it, also, if there would be any potential problems with the new generation.

Any thoughts?

Any thoughts about this? Would it worth to wait for Z790 or is this build would be just good as well?

 

[trs96]

Not sure if it is worth it, also, if there would be any potential problems with the new generation.

Z790 is three generations past the last supported Intel chipset that Apple used. Of course there will be potential problems.

 

[Azimuth1]

The Lightroom is an official release not a cracked version. I'm using the latest version. My computer is on Ventura. I tried to uninstall Ps & LR. Still is the same. So I will reinstall Mac Ventura again. But I don't know my EFI is good or not but everything run fine, only LR is not working. And what did you config your system MacPro 1,1 or MacPro 7,1?

Nowadays a new version of LR Classic is out, v. 12.1. Are you using the Classic version or the Cloud version? Can you post the error it gives to you? Including some screenshots ... maybe they can be helpful in better understanding what's happening on your machine.
My system is configured as iMacPro 1,1.

 

[etorix]

Any thoughts about this?

Points to consider:
Is it still worthwhile to build a hackintosh now? Intel support is likely to be dropped two or three releases from now.
Which additional feature of Z790 makes it desirable over Z690?

Would it worth to wait for Z790 or is this build would be just good as well?

Early attempts with Z790 were immediately successful. But what we're seeing, especially with Gigabyte boards, is problems creeping in through BIOS updates (sleep issues, wilful removal of support for Titan Ridge)—and these are propagated back to Z690. Z690 has the benefit that there was a known good working state, whereas Z790 may ship with a "bad BIOS" from day 1.
If you have a use case for Z790, carefully go ahead. But be wary of BIOS updates ("if it ain't broken , don't fix it"). Newer is no longer necessarily better.

 

[etorix]

Mac OS is installed on WD Black SN860 500Gb M.2 NVME

Is this the well-known WD Black SN850, or a whole new model?

I notice another point of interest:

After the restart I get the below report:

panic(cpu 0 caller 0xffffff80115866a2): nvme: "3rd party NVMe controller. Loss of MMIO space. Write. fBuiltIn=1 MODEL=WDS500G1X0E-00AFY0 FW=614600WD CSTS=0xffffffff US[1]=0x0 US[0]=0x20 VID=0x15b7 DID=0x5011 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6090

Is VT-d enabled in BIOS? Does AppleVTD show in IOReg?

 

[Cavid72]

Yes, all similar. One of users said that switching NVMe SSD to slot 1 helped. So I did the same. Mac OS ssd was in slot 2. I will watch Mac OS behavior and get back with the result.

I moved macOS installed NVMe SSD into slot 1 from slot 2. Now testing to see if KP happens. Previously, it happened after about 10-15 minutes.

 

[Cavid72]

I moved macOS installed NVMe SSD into slot 1 from slot 2. Now testing to see if KP happens. Previously, it happened after about 10-15 minutes.

It crashed after about 1hr with the different problem. But I don't know what caused it as I was away from the machine. However, after the below KP, I have been running machine for more then 1hr and no crash yet. Seems moving from slot 2 to slot 1 and moving ethernet cable from 10Gb to 2.5 did some magic trick.
Below is the report:

panic(cpu 8 caller 0xffffff8011bced33): Kernel trap at 0xffffff8012195bd5, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000038, CR3: 0x0000000019276000, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0xffffff801615f000, RCX: 0x0000000000000000, RDX: 0x00000000e00002eb
RSP: 0xffffffffdcd2ba50, RBP: 0xffffffffdcd2ba60, RSI: 0xffffff801615f000, RDI: 0xffffff86a4f93d20
R8: 0xffffff80161750f0, R9: 0x00000000fffeffff, R10: 0x0000000000000004, R11: 0xffffff8b6cedc000
R12: 0x00000000e00002eb, R13: 0xaaaaaaaaaaaaaaaa, R14: 0xffffff86a4f93d20, R15: 0x0000000000000000
RFL: 0x0000000000010282, RIP: 0xffffff8012195bd5, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000038, Error code: 0x0000000000000000, Fault CPU: 0x8, PL: 0, VF: 1

Panicked task 0xffffff90395ff670: 317 threads: pid 0: kernel_task
Backtrace (CPU 8), panicked thread: 0xffffff8b6cedc000, Frame : Return Address
0xffffffffdcd2b400 : 0xffffff8011a7cead mach_kernel : _handle_debugger_trap + 0x41d
0xffffffffdcd2b450 : 0xffffff8011bdf5d6 mach_kernel : _kdp_i386_trap + 0x116
0xffffffffdcd2b490 : 0xffffff8011bce943 mach_kernel : _kernel_trap + 0x4d3
0xffffffffdcd2b4e0 : 0xffffff8011a1ca70 mach_kernel : _return_from_trap + 0xe0
0xffffffffdcd2b500 : 0xffffff8011a7d27d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffffdcd2b620 : 0xffffff8011a7ca36 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffffdcd2b680 : 0xffffff8012314ed3 mach_kernel : _panic + 0x84
0xffffffffdcd2b770 : 0xffffff8011bced33 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffffffdcd2b8f0 : 0xffffff8011bcea16 mach_kernel : _kernel_trap + 0x5a6
0xffffffffdcd2b940 : 0xffffff8011a1ca70 mach_kernel : _return_from_trap + 0xe0
0xffffffffdcd2b960 : 0xffffff8012195bd5 mach_kernel : __ZN15OSMetaClassBase12safeMetaCastEPKS_PK11OSMetaClass + 0x15
0xffffffffdcd2ba60 : 0xffffff8015aa2332 com.zxystd.IntelBluetoothFirmware : __ZN19USBDeviceController16interruptHandlerEPvS0_ij + 0x20
0xffffffffdcd2ba90 : 0xffffff80161752f7 com.zxystd.IntelBTPatcher : __ZL17asyncIOCompletionPvS_ij + 0x207
0xffffffffdcd2bb00 : 0xffffff8014a29296 com.apple.iokit.IOUSBHostFamily : __ZN17AppleUSBIORequest8completeEv + 0x1048
0xffffffffdcd2bcd0 : 0xffffff80133e5aef com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter20completeRequestQueueEP11queue_entry + 0x2d1
0xffffffffdcd2bee0 : 0xffffff80133e5801 com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter12checkForWorkEv + 0x1ed
0xffffffffdcd2bf20 : 0xffffff80122437be mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x13e
0xffffffffdcd2bf60 : 0xffffff8012242de7 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x37
0xffffffffdcd2bfa0 : 0xffffff8011a1c19e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.driver.usb.AppleUSBCommon(1.0)[36ECFA56-AD39-3679-9D90-87D5E6709ABE]@0xffffff80133e3000->0xffffff80133e6fff
com.apple.iokit.IOUSBHostFamily(1.2)[20EC3681-15C9-332F-98E7-941C5AEA0253]@0xffffff80149bb000->0xffffff8014a4cfff
dependency: com.apple.driver.AppleBusPowerController(1.0)[74EBB4E2-C8DF-35C9-BB37-3DFEA2DAA365]@0xffffff8012ed9000->0xffffff8012edcfff
dependency: com.apple.driver.AppleSMC(3.1.9)[3E24C8F5-E515-3955-B6EB-95524FC73108]@0xffffff801326f000->0xffffff8013287fff
dependency: com.apple.driver.usb.AppleUSBCommon(1.0)[36ECFA56-AD39-3679-9D90-87D5E6709ABE]@0xffffff80133e3000->0xffffff80133e6fff
dependency: com.apple.driver.AppleUSBHostMergeProperties(1.2)[1E520B11-4136-3A2B-A26B-8FAE38E8EBD5]@0xffffff8014ac0000->0xffffff8014ac0fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[EEC3F9EF-E1A2-3873-B975-337FF0B193EE]@0xffffff801418d000->0xffffff801418efff
com.zxystd.IntelBTPatcher(2.2)[D6ECDF75-02E8-3BFF-91E8-B93D309C35FA]@0xffffff8016172000->0xffffff8016180fff
dependency: as.vit9696.Lilu(1.6.2)[264B15BE-8923-3A33-A9F5-8F0FFBB80595]@0xffffff8015a68000->0xffffff8015a93fff
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[20EC3681-15C9-332F-98E7-941C5AEA0253]@0xffffff80149bb000->0xffffff8014a4cfff
com.zxystd.IntelBluetoothFirmware(2.2)[CCEF82EE-1335-391C-8AA5-3B2A564B84EE]@0xffffff8015aa1000->0xffffff801616ffff
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[20EC3681-15C9-332F-98E7-941C5AEA0253]@0xffffff80149bb000->0xffffff8014a4cfff

Process name corresponding to current thread (0xffffff8b6cedc000): kernel_task
Boot args: keepsyms=1 debug=0x100 alcid=13 -wegnoigpu agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G320

Kernel version:
Darwin Kernel Version 21.6.0: Sun Nov 6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64
Kernel UUID: F831C932-31CA-3F2C-9E4C-2304C5641587
KernelCache slide: 0x0000000011800000
KernelCache base: 0xffffff8011a00000
Kernel slide: 0x0000000011810000
Kernel text base: 0xffffff8011a10000
__HIB text base: 0xffffff8011900000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 4834459854131
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000004659c4326bb
Sleep : 0x000004657d7f8daf 0x00000006349bda69 0x000004585c056b92
Wake : 0x000004659b2ba3f0 0x00000006352526e7 0x0000046591446c21
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff8037673000 - 0xffffffa037673000
. PGZ : 0xffffff8037673000 - 0xffffff803b674000
. VM : 0xffffff803b674000 - 0xffffff85079a7000
. RO : 0xffffff85079a7000 - 0xffffff86a100d000
. GEN0 : 0xffffff86a100d000 - 0xffffff8b6d340000
. GEN1 : 0xffffff8b6d340000 - 0xffffff9039673000
. GEN2 : 0xffffff9039673000 - 0xffffff95059a6000
. GEN3 : 0xffffff95059a6000 - 0xffffff99d1cd9000
. DATA : 0xffffff99d1cd9000 - 0xffffffa037673000
Metadata: 0xffffffc0bcf15000 - 0xffffffc0dcf15000
Bitmaps : 0xffffffc0dcf15000 - 0xffffffc0e8f15000

 

[Cavid72]

And I noticed, that Sleep stopped working properly: first screen turns off, machine turns off and then machine instantly wakes while screen remains turned off, and the screen wakes to keyboard or mouse.
EDIT: Unchecking -wake for network access in Energy Saver did NOT solve sleep issue.
EDiT: Sleep issue. I can confirm what Kalypso478 found in post 2250:

"If I operate the network cable on the Aquantia AQC113 10GBit port, MacOS wakes up immediately after standby.
It works without problems on the Intel I225-V 2.5GBit connection."

 

[CaseySJ]

And I noticed, that Sleep stopped working properly: first screen turns off, machine turns off and then instantly starts while screen remains turned off, and the screen wakes to keyboard or mouse.

This time the problem seems to be here:

0xffffffffdcd2ba60 : 0xffffff8015aa2332 com.zxystd.IntelBluetoothFirmware : __ZN19USBDeviceController16interruptHandlerEPvS0_ij + 0x20
0xffffffffdcd2ba90 : 0xffffff80161752f7 com.zxystd.IntelBTPatcher : __ZL17asyncIOCompletionPvS_ij + 0x207
0xffffffffdcd2bb00 : 0xffffff8014a29296 com.apple.iokit.IOUSBHostFamily : __ZN17AppleUSBIORequest8completeEv + 0x1048
0xffffffffdcd2bcd0 : 0xffffff80133e5aef com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter20completeRequestQueueEP11queue_entry + 0x2d1
0xffffffffdcd2bee0 : 0xffffff80133e5801 com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter12checkForWorkEv + 0x1ed
0xffffffffdcd2bf20 : 0xffffff80122437be mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x13e
0xffffffffdcd2bf60 : 0xffffff8012242de7 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x37
0xffffffffdcd2bfa0 : 0xffffff8011a1c19e mach_kernel : _call_continuation + 0x2e

Some questions:

• You stated earlier that Monterey 12.6.x had been running smoothly for a couple of months, but after a BIOS upgrade to 2004 these crashes started occurring. Is that correct?
• Are you sure you installed BIOS 2004 and not 2204?