Contribute
Register

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

suren6791 said:
Who has managed to run XMP with 4 Ram sticks? What did you do to get this working, I hate to waste two sticks as I cannot get XMP to work with four. I have 4 x 16G Kingston Hyper Fury
Click to expand...
www.tonymacx86.com

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

The Z690 Aero G comes in two forms: DDR4 and DDR5. I've never seen one for sale in the US yet but they must be out in the EU and elsewhere. Had thought only the Aero D has a DDR5 edition.
www.tonymacx86.com www.tonymacx86.com
 
StefanAM said:
www.tonymacx86.com

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

The Z690 Aero G comes in two forms: DDR4 and DDR5. I've never seen one for sale in the US yet but they must be out in the EU and elsewhere. Had thought only the Aero D has a DDR5 edition.
www.tonymacx86.com www.tonymacx86.com
Click to expand...
Today, before I did any changes in BIOS, with XMP 1 enabled, I put back the 2 other RAM cards so now have the 4 x 16GB 3200 RAM installed. I powered up the system with XMP still enabled, and the system powered up and is working with the 4 sticks. I changed nothing else since removing the 2 sticks and putting it back except turn on XMP.
 
StefanAM said:
www.tonymacx86.com

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

The Z690 Aero G comes in two forms: DDR4 and DDR5. I've never seen one for sale in the US yet but they must be out in the EU and elsewhere. Had thought only the Aero D has a DDR5 edition.
www.tonymacx86.com www.tonymacx86.com
Click to expand...
Well it worked with 4 sticks and went to sleep properly, but this morning, when playing a video, it started the rebooting by itself again. Never did that on 2 sticks of RAM. Is there any other way to get XMP to work with 4 sticks? Anything else I can try?
 
When the PC reboots in Big Sur/Monterey, the below is the error report I am getting. Any Help to fix this.

Code: 
panic(cpu 0 caller 0xffffff80173c3356): Kernel trap at 0xffffff801a44ab5b, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffbf8717ee7820, CR3: 0x0000000e2d98c008, CR4: 0x00000000003626e0
RAX: 0xffffffa09b7a9001, RBX: 0xffffbf8717ee77f8, RCX: 0x000000000000fb78, RDX: 0x0fffffff0008fb58
RSP: 0xffffffc1b266aef0, RBP: 0xffffffc1b266af30, RSI: 0x0000000001000020, RDI: 0xffffff93cdce2000
R8:  0xffffff801a37a315, R9:  0x0000000000000000, R10: 0xffffffc1b266b240, R11: 0x0000000f93c920a0
R12: 0x0000000000000003, R13: 0x0fffffff0008fb58, R14: 0x0000000000000001, R15: 0x0000000001000020
RFL: 0x0000000000010202, RIP: 0xffffff801a44ab5b, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffbf8717ee7820, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffffc1b266a910 : 0xffffff801728b26d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffc1b266a960 : 0xffffff80173d2993 mach_kernel : _kdp_i386_trap + 0x143
0xffffffc1b266a9a0 : 0xffffff80173c2f8a mach_kernel : _kernel_trap + 0x55a
0xffffffc1b266a9f0 : 0xffffff801722fa2f mach_kernel : _return_from_trap + 0xff
0xffffffc1b266aa10 : 0xffffff801728aa8d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffc1b266ab30 : 0xffffff801728ad83 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffc1b266aba0 : 0xffffff8017a9c5aa mach_kernel : _panic + 0x54
0xffffffc1b266ac10 : 0xffffff80173c3356 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffc1b266ad90 : 0xffffff80173c303d mach_kernel : _kernel_trap + 0x60d
0xffffffc1b266ade0 : 0xffffff801722fa2f mach_kernel : _return_from_trap + 0xff
0xffffffc1b266ae00 : 0xffffff801a44ab5b com.apple.filesystems.apfs : _object_in_jhash + 0x54
0xffffffc1b266af30 : 0xffffff801a44a9d1 com.apple.filesystems.apfs : _apfs_jhash_getvnode_internal + 0x78
0xffffffc1b266af90 : 0xffffff801a3f1e84 com.apple.filesystems.apfs : _apfs_inode_getxattr + 0x18d
0xffffffc1b266b070 : 0xffffff801a3f1cec com.apple.filesystems.apfs : _apfs_vnop_getxattr + 0xac
0xffffffc1b266b0c0 : 0xffffff8017546f07 mach_kernel : _vn_getxattr + 0x277
0xffffffc1b266b1d0 : 0xffffff8017a8c333 mach_kernel : _mac_vnop_getxattr + 0x123
0xffffffc1b266b280 : 0xffffff801a361efe com.apple.security.sandbox : _derive_vnode_storage_class + 0x39b
0xffffffc1b266b550 : 0xffffff801a35ee1f com.apple.security.sandbox : _eval + 0x1310
0xffffffc1b266b800 : 0xffffff801a35c3a9 com.apple.security.sandbox : _sb_evaluate_internal + 0xc9
0xffffffc1b266b960 : 0xffffff801a3567ef com.apple.security.sandbox : _hook_vnode_check_open + 0xb8
0xffffffc1b266bb50 : 0xffffff8017a8526a mach_kernel : _mac_vnode_check_open + 0x9a
0xffffffc1b266bb90 : 0xffffff801751fd3f mach_kernel : _vn_authorize_open_existing + 0xbf
0xffffffc1b266bbd0 : 0xffffff8017545d78 mach_kernel : _vn_open_auth + 0xa58
0xffffffc1b266bc90 : 0xffffff801752b888 mach_kernel : _fg_vn_data_alloc + 0x178
0xffffffc1b266bee0 : 0xffffff801752c439 mach_kernel : _open_nocancel + 0x139
0xffffffc1b266bf40 : 0xffffff801793e9de mach_kernel : _unix_syscall64 + 0x2ce
0xffffffc1b266bfa0 : 0xffffff80172301f6 mach_kernel : _hndl_unix_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.security.sandbox(300.0)[5E07468E-E3FC-39AB-A09A-8901B48EEADF]@0xffffff801a34a000->0xffffff801a390fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[31810E2C-FD94-31EC-8723-BA1B19DDF0A1]@0xffffff80188c0000->0xffffff80188d5fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[FFF27081-0E9D-3E7F-8807-C018C8E46A09]@0xffffff8019e6e000->0xffffff8019e7ffff
            dependency: com.apple.kext.AppleMatch(1.0.0d1)[D3A3436D-009F-3B59-9127-3C95785935C5]@0xffffff80188bc000->0xffffff80188befff
         com.apple.filesystems.apfs(1677.141.3)[45812160-E4A7-307A-B604-91D6A782126B]@0xffffff801a3aa000->0xffffff801a519fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[A506788E-BC7C-3C87-BD70-376984C225D3]@0xffffff80186fe000->0xffffff8018707fff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[F1C24692-B3A0-3F31-A777-CA17069CD3DD]@0xffffff8018711000->0xffffff8018716fff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[E6C5D15B-3934-3236-932A-1EEF294F5E2B]@0xffffff8018b6d000->0xffffff8018b73fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[FFF27081-0E9D-3E7F-8807-C018C8E46A09]@0xffffff8019e6e000->0xffffff8019e7ffff
            dependency: com.apple.kec.corecrypto(11.1)[17F7A252-0406-3D10-90BD-A51F4394481D]@0xffffff801a547000->0xffffff801a5d8fff
            dependency: com.apple.security.AppleImage4(3.0.0)[BE766F1D-D061-3436-98BA-AF65AD47F2EF]@0xffffff801877d000->0xffffff801878dfff

Process name corresponding to current thread: ReportCrash
Boot args: -v keepsyms=1 debug=0x100 agdpmod=pikera -wegnoigpu dk.e1000=0

Mac OS version:
20G527

Kernel version:
Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41 PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64
Kernel UUID: 40A47F9A-078F-3F9B-B353-53A194CC6F1D
KernelCache slide: 0x0000000017000000
KernelCache base:  0xffffff8017200000
Kernel slide:      0x0000000017010000
Kernel text base:  0xffffff8017210000
__HIB  text base: 0xffffff8017100000
System model name: MacPro7,1 (Mac-******************)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3616862863054
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000034a1dd38803
  Sleep   : 0x0000027915fcf9c4 0x00000003b3b6d8b5 0x00000263dbae3630
  Wake    : 0x000002791ee96ac4 0x00000003b942debd 0x0000027917b11ae0
 
suren6791 said:
Well it worked with 4 sticks and went to sleep properly, but this morning, when playing a video, it started the rebooting by itself again. Never did that on 2 sticks of RAM. Is there any other way to get XMP to work with 4 sticks? Anything else I can try?
Click to expand...
"I raised VDD and VDDQ to 1.3v and now the rig is perfectly stable.
Update: XMP stable at 1,260 VDD and VDDQ, 0.01 more then default. Maybe future BIOS will fix this."

You need to work on this.
 
StefanAM said:
"I raised VDD and VDDQ to 1.3v and now the rig is perfectly stable.
Update: XMP stable at 1,260 VDD and VDDQ, 0.01 more then default. Maybe future BIOS will fix this."

You need to work on this.
Click to expand...
I tried that and could not even get the system to post. Had to do a CMOS reset to get it to post again.
 
Hello, I have a question, probably stupid, why use in the EFI the kexts like BlueToolFixup.kext, BrcmPatchRAM3.kext, etc., if your hackintosh is equipped with a Fenvi plug and play as in the description of the equipped equipment ?
 
odemolay said:
Hello, I have a question, probably stupid, why use in the EFI the kexts like BlueToolFixup.kext, BrcmPatchRAM3.kext, etc., if your hackintosh is equipped with a Fenvi plug and play as in the description of the equipped equipment ?
Click to expand...
For natively supported Broadcom modules such as the BCM94360-series there is little need for these kexts. For other (older) Broadcom modules these drivers are necessary. Even for BCM94360-series, if you install Windows drivers and dual boot between Windows and macOS, you may (or may not) find these kexts beneficial.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top