Contribute
Register

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

Regarding Thunderbolt, please see Step 10 Installation Verification in Post 1.
Hey Casey, thanks for the reply! If you go back to post 992 you can see I attached a screenshot where I do exactly that. I've studied your first post in depth. I'm not sure why the TB4 driver isn't loading. I have checked my IOReg and it looks like everything lines up but like I've mentioned I'm not a coder or developer... I've tried my best to get everything running without much help and this is the last thing that has me stuck. Four posts back I attached both my EFI and IOReg. Is there any way I can convince you to take a super quick peak? I've been chipping away at everything and TB4 is the last thing I'm concerned about. Any help would be greatly appreciated. Thanks -Danny

EDIT: @gandem got me below! I'm all good! Thanks again for all you've done - can't drive that home enough :D And thank you too @gandem !!
 
Last edited:
Hey Casey, thanks for the reply! If you go back to post 992 you can see I attached a screenshot where I do exactly that. I've studied your first post in depth. I'm not sure why the TB4 driver isn't loading. I have checked my IOReg and it looks like everything lines up but like I've mentioned I'm not a coder or developer... I've tried my best to get everything running without much help and this is the last thing that has me stuck. Four posts back I attached both my EFI and IOReg. Is there any way I can convince you to take a super quick peak? I've been chipping away at everything and TB4 is the last thing I'm concerned about. Any help would be greatly appreciated. Thanks -Danny
Looks like you're using V1B of the hot plug support ssdt. Because there's no device spoofing on V1B, the driver doesn't show loaded. Have you tried V2? You need to turn off 1B as it's either/or. In general, hot plug has not worked well in Monterey since 12.1, although there have been reports that it's working better in the latest 12.4 public betas.
 
Have you tried V2? You need to turn off 1B as it's either/or. In general, hot plug has not worked well in Monterey since 12.1, although there have been reports that it's working better in the latest 12.4 public betas.
No I hadn't actually - not sure why. I just gave it a go and the driver is now reporting as loaded. Thanks again! Twice now you've saved me some headaches! I truly do appreciate the help! Also just realized that SSDT-USBW and UsbWakeUpFix.kext was making all bluetooth devices hang on wake up - disabled them and my Bluetooth woes went away. This concludes the small issue list I had going - everything is working like I wanted! THANK YOU!!!
 
No I hadn't actually - not sure why. I just gave it a go and the driver is now reporting as loaded. Thanks again! Twice now you've saved me some headaches! I truly do appreciate the help! Also just realized that SSDT-USBW and UsbWakeUpFix.kext was making all bluetooth devices hang on wake up - disabled them and my Bluetooth woes went away. This concludes the small issue list I had going - everything is working like I wanted! THANK YOU!!!
Glad to hear the problems have been resolved. Regarding Bluetooth hanging after wake-from-sleep, are you using the Intel WiFi/BT module or a Broadcom BCM94360NG?
 
Okay. I think it looks like maybe you have to use the AppleALCU.kext instead of the AppleALC.kext.
That is only the other thing I could think of that may be causing this issue. So edit the EFI, add in the AppleALCU.kext and disable AppleALC under Kernel > Add, save the file, reboot the system and run the ResetNVRAM tool in the boot menu before booting the main drive.
I tried that but it hung up again and restarted on its own. Sorry to keep bugging you with this but appreciate any help as it is so frustrating, happens at the worst possible.

Code:
panic(cpu 8 caller 0xffffff800b5d38f3): Kernel trap at 0xffffff800b5b273c, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00000002100f2000, CR3: 0x0000000885380029, CR4: 0x00000000003626e0
RAX: 0xffffff8044994ae0, RBX: 0xfffffeb2386093d8, RCX: 0x00000000003bbc75, RDX: 0x80000003bbc75005
RSP: 0xffffffe0e61aba60, RBP: 0xffffffe0e61abae0, RSI: 0xffffffffffffffdf, RDI: 0xffffff99deb3f680
R8:  0x000ffffffffff000, R9:  0xfffffeb2386093d8, R10: 0x0000000002420000, R11: 0x0000000000000000
R12: 0x0000000000000020, R13: 0xffdfff80389c7ea0, R14: 0x00000000003bbc75, R15: 0xffffff80389c7ea0
RFL: 0x0000000000010202, RIP: 0xffffff800b5b273c, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x00000002100f2000, Error code: 0x0000000000000000, Fault CPU: 0x8, PL: 1, VF: 0

Panicked task 0xffffff90451a0380: 11 threads: pid 156: WindowServer
Backtrace (CPU 8), panicked thread: 0xffffff904aed4550, Frame : Return Address
0xffffff800b310170 : 0xffffff800b483e2d mach_kernel : _handle_debugger_trap + 0x41d
0xffffff800b3101c0 : 0xffffff800b5e3cb6 mach_kernel : _kdp_i386_trap + 0x116
0xffffff800b310200 : 0xffffff800b5d350d mach_kernel : _kernel_trap + 0x51d
0xffffff800b310250 : 0xffffff800b423a60 mach_kernel : _return_from_trap + 0xe0
0xffffff800b310270 : 0xffffff800b4841fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffff800b310390 : 0xffffff800b4839b6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffff800b3103f0 : 0xffffff800bd164bf mach_kernel : _panic + 0x84
0xffffff800b3104e0 : 0xffffff800b5d38f3 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffff800b310660 : 0xffffff800b5d35e2 mach_kernel : _kernel_trap + 0x5f2
0xffffff800b3106b0 : 0xffffff800b423a60 mach_kernel : _return_from_trap + 0xe0
0xffffff800b3106d0 : 0xffffff800b5b273c mach_kernel : _phys_attribute_clear + 0x15c
0xffffffe0e61abae0 : 0xffffff800b52e746 mach_kernel : _vm_fault_cleanup + 0xbd6
0xffffffe0e61abba0 : 0xffffff800b529ad5 mach_kernel : _vm_fault_enter + 0x2b5
0xffffffe0e61abc30 : 0xffffff800b5282aa mach_kernel : _vm_fault$XNU_INTERNAL + 0x21ca
0xffffffe0e61abf00 : 0xffffff800b5d3c50 mach_kernel : _user_trap + 0x2c0
0xffffffe0e61abfa0 : 0xffffff800b42396f mach_kernel : _hndl_alltraps + 0xdf

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

Mac OS version:
21E258

Kernel version:
Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
Kernel UUID:
KernelCache slide: 0x000000000b200000
KernelCache base:  0xffffff800b400000
Kernel slide:      0x000000000b210000
Kernel text base:  0xffffff800b410000
__HIB  text base: 0xffffff800b300000
System model name: MacPro7,1
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1799889082521
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000001a311bfda16
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000108615b593 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Foreign : 0xffffff8013629000 - 0xffffff8013637000
  Native  : 0xffffff8045243000 - 0xffffffa045243000
  Readonly: 0xffffff8511f0f000 - 0xffffff86ab8a8000
  Metadata: 0xffffffe2cbdd6000 - 0xffffffe2ec0f3000
  Bitmaps : 0xffffffe2ec0f3000 - 0xffffffe2f80f3000
 
Your Window server process crashed. And it says ‘fault CPU’ so seems hardware related.

It can be an instability artifact of the beta, or your CPU, or GPU, or your memory. are you overclocking? Do you have stability at stock frequencies on a non-beta release?
 
I tried that but it hung up again and restarted on its own. Sorry to keep bugging you with this but appreciate any help as it is so frustrating, happens at the worst possible.

Code:
panic(cpu 8 caller 0xffffff800b5d38f3): Kernel trap at 0xffffff800b5b273c, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00000002100f2000, CR3: 0x0000000885380029, CR4: 0x00000000003626e0
RAX: 0xffffff8044994ae0, RBX: 0xfffffeb2386093d8, RCX: 0x00000000003bbc75, RDX: 0x80000003bbc75005
RSP: 0xffffffe0e61aba60, RBP: 0xffffffe0e61abae0, RSI: 0xffffffffffffffdf, RDI: 0xffffff99deb3f680
R8:  0x000ffffffffff000, R9:  0xfffffeb2386093d8, R10: 0x0000000002420000, R11: 0x0000000000000000
R12: 0x0000000000000020, R13: 0xffdfff80389c7ea0, R14: 0x00000000003bbc75, R15: 0xffffff80389c7ea0
RFL: 0x0000000000010202, RIP: 0xffffff800b5b273c, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x00000002100f2000, Error code: 0x0000000000000000, Fault CPU: 0x8, PL: 1, VF: 0

Panicked task 0xffffff90451a0380: 11 threads: pid 156: WindowServer
Backtrace (CPU 8), panicked thread: 0xffffff904aed4550, Frame : Return Address
0xffffff800b310170 : 0xffffff800b483e2d mach_kernel : _handle_debugger_trap + 0x41d
0xffffff800b3101c0 : 0xffffff800b5e3cb6 mach_kernel : _kdp_i386_trap + 0x116
0xffffff800b310200 : 0xffffff800b5d350d mach_kernel : _kernel_trap + 0x51d
0xffffff800b310250 : 0xffffff800b423a60 mach_kernel : _return_from_trap + 0xe0
0xffffff800b310270 : 0xffffff800b4841fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffff800b310390 : 0xffffff800b4839b6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffff800b3103f0 : 0xffffff800bd164bf mach_kernel : _panic + 0x84
0xffffff800b3104e0 : 0xffffff800b5d38f3 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffff800b310660 : 0xffffff800b5d35e2 mach_kernel : _kernel_trap + 0x5f2
0xffffff800b3106b0 : 0xffffff800b423a60 mach_kernel : _return_from_trap + 0xe0
0xffffff800b3106d0 : 0xffffff800b5b273c mach_kernel : _phys_attribute_clear + 0x15c
0xffffffe0e61abae0 : 0xffffff800b52e746 mach_kernel : _vm_fault_cleanup + 0xbd6
0xffffffe0e61abba0 : 0xffffff800b529ad5 mach_kernel : _vm_fault_enter + 0x2b5
0xffffffe0e61abc30 : 0xffffff800b5282aa mach_kernel : _vm_fault$XNU_INTERNAL + 0x21ca
0xffffffe0e61abf00 : 0xffffff800b5d3c50 mach_kernel : _user_trap + 0x2c0
0xffffffe0e61abfa0 : 0xffffff800b42396f mach_kernel : _hndl_alltraps + 0xdf

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

Mac OS version:
21E258

Kernel version:
Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
Kernel UUID:
KernelCache slide: 0x000000000b200000
KernelCache base:  0xffffff800b400000
Kernel slide:      0x000000000b210000
Kernel text base:  0xffffff800b410000
__HIB  text base: 0xffffff800b300000
System model name: MacPro7,1
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1799889082521
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000001a311bfda16
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000108615b593 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Foreign : 0xffffff8013629000 - 0xffffff8013637000
  Native  : 0xffffff8045243000 - 0xffffffa045243000
  Readonly: 0xffffff8511f0f000 - 0xffffff86ab8a8000
  Metadata: 0xffffffe2cbdd6000 - 0xffffffe2ec0f3000
  Bitmaps : 0xffffffe2ec0f3000 - 0xffffffe2f80f3000
Have you tried to enable DisableRtcChecksum?
 
Your Window server process crashed. And it says ‘fault CPU’ so seems hardware related.

It can be an instability artifact of the beta, or your CPU, or GPU, or your memory. are you overclocking? Do you have stability at stock frequencies on a non-beta release?
No overclocking, just stock. Also I am not running Beta OS. The only other thing I did was to update BIOS from 0811 to 1403. Its only during zoom the system acts funny, other than that all is well. The computer is on for 4 hours straight with no issue.
 
No overclocking, just stock. Also I am not running Beta OS. The only other thing I did was to update BIOS from 0811 to 1403. Its only during zoom the system acts funny, other than that all is well. The computer is on for 4 hours straight with no issue.
So the memory is stock speed, too, or XMP? It might the issue be Zoom or might it be the webcam or microphone? Perhaps test those devices with another app like QuickTime for example and see if the system crashes, too. Maybe Zoom has an updated version? Can you use Zoom in the browser vs using their app?
 
Last edited:
Back
Top