Contribute
Register

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

Finally! had a working baseline yesterday without any bluetooth or wifi. Did the last step to enable it using Intel AX210. The board I got is rev 1.3 so it contains a newer bluetooth/wifi module which is AX210.

I chose Monterey due to stability. Didn't want to risk it with Ventura and spend too much time troubleshooting.

system-info.png


cinebench_single.png
cinebench_multi.png



Sleep seems to work but it wouldn't wake up after an extended sleep time or entered a second sleep. If I were to put it to sleep and then wake it up a moment later, it would work but not the second time.

Bluetooth works and I can connect my airpod. Airdrop doesn't work. All the other continuity features as mentioned by @CaseySJ probably don't work but I don't normally use all the other features (except for an occasionally transfer of using airdrop -- not a big deal).

Wifi works. Actually, even without it is ok since I usually use my ethernet cable -- just more convenient.

Does the USBWakeFixup.kext fix the sleep issue I mentioned above? for some reasons, this wasn't selected in the Kext when I did step 9. I found out when I followed the steps to enable Wifi/Bluetooth. Also my OCC didn't see the new kext files after I copied the required files to the EFI mount --> EFI/EFI/OC/Kexts directory so I had to click on scan/browse to reload these files. After the reload, the file USBWakeFixup.kext was selected (checked or enabled) and other wifi/BT files were selected. The OCC also kept the old files such as the Airportltlwm-Monterey.kext file in there so it was a bit confusing since I had to sort out which one is old and new (luckily the OCC did it for me). I was using OCC v2.62.0 for OC v 0.8.3 (release).
 
Last edited:
Good afternoon.
I have problems.
Everything worked fine with Ventura 13.4 when upgrading to Ventura 13.4.1 the computer hangs with final Cut pro x with luxmark and in Kext Utiliy I get this "CheckNVRam: Test Write NVRam... Error
And with Cinebench and I have lost bluetooth.
And its performance is not as expected.
I send you config.plist.
Let's see if you can help me
Greetings.
Luisan
 

Attachments

  • Captura de pantalla 2023-07-03 a las 12.42.29.png
    Captura de pantalla 2023-07-03 a las 12.42.29.png
    43.5 KB · Views: 17
  • config.plist
    57.7 KB · Views: 23
After tangling the problem, I solved it was from the RAM memory.
But still no Bluetooth.
I'm still looking for information on the forums.
 
Has anyone updated their BIOS to F24? Did your experience go smoothly?

I thought I brick my motherboard after a failed F23 update but after hours of troubleshooting, it finally booted up and I was able to recover to F23 version (after a successful Q flash plus update). Here is the outline of what happened (from the beginning). Skip to step 9 if you only wanted to know the details of this BIOS update.

My part list available in this post https://www.tonymacx86.com/threads/gigabyte-z690-aero-g-i5-12600k-amd-rx-6800-xt.317179/post-2372060

Maybe this could help someone else in the future? Gigabyte BIOS update is dangerous!
  1. I have a PCB Rev 1.3 Motherboard. MOBO came with F6 version.
  2. After assembled I installed Windows 10 without a BIOS update. I wanted to confirm everything worked first before tinkering with the BIOS (since it can be fatal if not done right -- while it's easy, it can fail)
  3. After installing drivers, benchmarking, and even playing some games, I confirmed the build was really good.
  4. I updated BIOS to F23 using the Q Flash method. It wasn't smooth but it worked eventually. See this post above https://www.tonymacx86.com/threads/gigabyte-z690-aero-g-i5-12600k-amd-rx-6800-xt.317179/post-2374395
    1. This will be relevant later. I used a 64GB Samsung Flash Drive but I had to reduce it to around 32GB so I could reformat it to FAT32 so the MOBO could read it for BIOS update.
  5. Enabled XMP, the MOBO took its time to bootup. Also see post above as well.
  6. In the end, everything worked. BIOS F23 was good.
  7. I followed @CaseySJ guide to install MacOS Montery (really appreciate your detailed post but this is worth a separate appreciation comment). I chose Monterey due to stability vs Ventura. I am using OC 0.8.3. No mini guide for newest OC update. There was a generic guide but didn't have time to play around with that so I went with what seemed to be more stable.
  8. Install went smoothly. Didn't experience any issues during the install.
  9. On Monday, I attempted to update my BIOS to F24 (from F23). The problem started from this BIO update.
  10. The BIOS somehow froze at the verification step. In previous update, I would see a message saying that the BIOS was updating but I didn't see that. I only saw "verifying File..." and then it froze at 79%. I waited over 10 minutes without any progress so I probably rebooted my PC around 15-min mark.
  11. After the restart, I think I pressed "Del" to go to the BIOS but when I got there, my BIOS alerted me that the firmware was being updated. See image below.
    1. I'm not sure if a firmware needed to be update. I thought it was updating the BIOS?
  12. The firmware update finished successfully but the BIOS never POSTed (or I would think after the firmware update, it would continue with the BIOS update but that never happened). I think the CPU LED light on the MOBO was red the whole time. I waited a while but eventually rebooted the machine. Each reboot never reach the BIOS screen.
  13. I tried to use another monitor with HDMI (the one dedicated to this PC has DVI with an adapter to displayport so I connect it to my GPU displayport) but that didn't work.
  14. Here is the fun part:
    1. After a while, the RGB lights on my front fans stopped working. The RGB fans were connected to the ARGB hubs (from bequiet)
    2. Eventually my computer shut down by itself
    3. My case power button stopped working
    4. thought my hacking life was OVER before it even started :lol:
  15. I tried clearing the CMOS but that didn't work either. I even took out the MOBO battery and re-inserted but nothing worked. The power button wasn't working.
    1. I thought the power supply went bad
    2. I thought I shorted the power switch button when I shorted the CLR_CMOS
  16. I wasn't too sure anymore and thought about returning this MOBO since I'm still within the return period but wanted to try the Q-Flash plus method.
  17. I used the same USB flash drive I mentioned in 4.1 above. Of course, I had to update the file to comply with the Q-Flash plus method (download the BIOS and rename it to gigabyte.bin).
  18. After I plugged this flash drive in the right port and pressed the Q flash plus button, the motherboard booted up and the LED was flashing orange (I think the CPU LED was red -- I can't remember if it was VGA or CPU)
    1. I had everything plugged in (CPU, CPU cooler, GPU, etc), so I was worry it could short something. Does it?
  19. Based on docs (and some youtubes), it should be flashing for about 6-8 minutes. Mine flashed for 1.5 mins and stopped.
  20. So I unplugged the CPU power cable and GPU power cables and then tried again. This time, I think it flashed a bit longer and then there was a solid orange light so wasn't sure what happened. It shut down the machine after 8 minutes (actually I can't remember the exact detail here).
  21. After some more troubleshooting and some Googling, I thought the BIOS couldn't take the large flash drive (even though it's FAT32 and under 32GB).
  22. I looked around the house and luckily found an ancient flash drive that was probably around 4 GB in size. I reformatted it to FAT 32 and added the F24 BIOS file.
  23. Tried the Q flash plus again and BOOOOM, the orange LED flashed for 6 minutes and 15 seconds (I timed it).
    1. Note, I tried this with the CPU and GPU power cables unplugged.
  24. Now that didn't really resolved the power button and RGB lights on my fans not working but it gave me some hope.
    1. I was tinkering with the power switch on the case and also the RST_SW. That didn't really work.
    2. I tried shorting the RST pins but it didn't boot up the system as well.
    3. FINALLY, I just unplugged the ARGB from the BeQuiet ARGB hub and replugged it back in.
      1. I think this did the trick. My PC finally booted up using the power button.
  25. The BIOS was able to POST and back to version F23. The BIOS threw a BIOS reset info message.
  26. I was able to boot into Windows without much reconfiguration in BIOS (I avoided MacOS due to the setting wasn't optimal for MacOS setting). I verified a few things to ensure everything was operating as normal.
  27. I think I updated the F23 BIOS so that MacOS could boot but can't recall.
  28. After that I retried F24 update using the Q-Flash method (and 4 GB flash drive).
  29. This time it only took around 6 minutes and was able to boot successfully.
  30. I updated all configuration and turn back on the XMP.
  31. MacOS Monterey is running like normal now and I did some benchmarking to ensure it was performing like before the BIOS update (and hopefully I didn't short anything during this entire ordeal)
Based on this, does anyone think my motherboard is still fine? I am still within the return period. A bit concern I could short one or more components (CPU, GPU) even though everything seems to work now (Cinebench shows a score of 23,100 multi core and close to 2,000 for single core).

bio-update-freeze-verify.jpg

bios-update-progress.jpg
 
Last edited:
I am using bios F24 and everything is working except Bluetooth.
The Cinebench results are these.
 

Attachments

  • Captura de pantalla 2023-07-06 a las 10.28.33.png
    Captura de pantalla 2023-07-06 a las 10.28.33.png
    76.7 KB · Views: 15
statusquo said:
Has anyone updated their BIOS to F24? Did your experience go smoothly?

I thought I brick my motherboard after a failed F23 update but after hours of troubleshooting, it finally booted up and I was able to recover to F23 version (after a successful Q flash plus update). Here is the outline of what happened (from the beginning). Skip to step 9 if you only wanted to know the details of this BIOS update.

My part list available in this post https://www.tonymacx86.com/threads/gigabyte-z690-aero-g-i5-12600k-amd-rx-6800-xt.317179/post-2372060

Maybe this could help someone else in the future? Gigabyte BIOS update is dangerous!
  1. I have a PCB Rev 1.3 Motherboard. MOBO came with F6 version.
  2. After assembled I installed Windows 10 without a BIOS update. I wanted to confirm everything worked first before tinkering with the BIOS (since it can be fatal if not done right -- while it's easy, it can fail)
  3. After installing drivers, benchmarking, and even playing some games, I confirmed the build was really good.
  4. I updated BIOS to F23 using the Q Flash method. It wasn't smooth but it worked eventually. See this post above https://www.tonymacx86.com/threads/gigabyte-z690-aero-g-i5-12600k-amd-rx-6800-xt.317179/post-2374395
    1. This will be relevant later. I used a 64GB Samsung Flash Drive but I had to reduce it to around 32GB so I could reformat it to FAT32 so the MOBO could read it for BIOS update.
  5. Enabled XMP, the MOBO took its time to bootup. Also see post above as well.
  6. In the end, everything worked. BIOS F23 was good.
  7. I followed @CaseySJ guide to install MacOS Montery (really appreciate your detailed post but this is worth a separate appreciation comment). I chose Monterey due to stability vs Ventura. I am using OC 0.8.3. No mini guide for newest OC update. There was a generic guide but didn't have time to play around with that so I went with what seemed to be more stable.
  8. Install went smoothly. Didn't experience any issues during the install.
  9. On Monday, I attempted to update my BIOS to F24 (from F23). The problem started from this BIO update.
  10. The BIOS somehow froze at the verification step. In previous update, I would see a message saying that the BIOS was updating but I didn't see that. I only saw "verifying File..." and then it froze at 79%. I waited over 10 minutes without any progress so I probably rebooted my PC around 15-min mark.
  11. After the restart, I think I pressed "Del" to go to the BIOS but when I got there, my BIOS alerted me that the firmware was being updated. See image below.
    1. I'm not sure if a firmware needed to be update. I thought it was updating the BIOS?
  12. The firmware update finished successfully but the BIOS never POSTed (or I would think after the firmware update, it would continue with the BIOS update but that never happened). I think the CPU LED light on the MOBO was red the whole time. I waited a while but eventually rebooted the machine. Each reboot never reach the BIOS screen.
  13. I tried to use another monitor with HDMI (the one dedicated to this PC has DVI with an adapter to displayport so I connect it to my GPU displayport) but that didn't work.
  14. Here is the fun part:
    1. After a while, the RGB lights on my front fans stopped working. The RGB fans were connected to the ARGB hubs (from bequiet)
    2. Eventually my computer shut down by itself
    3. My case power button stopped working
    4. thought my hacking life was OVER before it even started :lol:
  15. I tried clearing the CMOS but that didn't work either. I even took out the MOBO battery and re-inserted but nothing worked. The power button wasn't working.
    1. I thought the power supply went bad
    2. I thought I shorted the power switch button when I shorted the CLR_CMOS
  16. I wasn't too sure anymore and thought about returning this MOBO since I'm still within the return period but wanted to try the Q-Flash plus method.
  17. I used the same USB flash drive I mentioned in 4.1 above. Of course, I had to update the file to comply with the Q-Flash plus method (download the BIOS and rename it to gigabyte.bin).
  18. After I plugged this flash drive in the right port and pressed the Q flash plus button, the motherboard booted up and the LED was flashing orange (I think the CPU LED was red -- I can't remember if it was VGA or CPU)
    1. I had everything plugged in (CPU, CPU cooler, GPU, etc), so I was worry it could short something. Does it?
  19. Based on docs (and some youtubes), it should be flashing for about 6-8 minutes. Mine flashed for 1.5 mins and stopped.
  20. So I unplugged the CPU power cable and GPU power cables and then tried again. This time, I think it flashed a bit longer and then there was a solid orange light so wasn't sure what happened. It shut down the machine after 8 minutes (actually I can't remember the exact detail here).
  21. After some more troubleshooting and some Googling, I thought the BIOS couldn't take the large flash drive (even though it's FAT32 and under 32GB).
  22. I looked around the house and luckily found an ancient flash drive that was probably around 4 GB in size. I reformatted it to FAT 32 and added the F24 BIOS file.
  23. Tried the Q flash plus again and BOOOOM, the orange LED flashed for 6 minutes and 15 seconds (I timed it).
    1. Note, I tried this with the CPU and GPU power cables unplugged.
  24. Now that didn't really resolved the power button and RGB lights on my fans not working but it gave me some hope.
    1. I was tinkering with the power switch on the case and also the RST_SW. That didn't really work.
    2. I tried shorting the RST pins but it didn't boot up the system as well.
    3. FINALLY, I just unplugged the ARGB from the BeQuiet ARGB hub and replugged it back in.
      1. I think this did the trick. My PC finally booted up using the power button.
  25. The BIOS was able to POST and back to version F23. The BIOS threw a BIOS reset info message.
  26. I was able to boot into Windows without much reconfiguration in BIOS (I avoided MacOS due to the setting wasn't optimal for MacOS setting). I verified a few things to ensure everything was operating as normal.
  27. I think I updated the F23 BIOS so that MacOS could boot but can't recall.
  28. After that I retried F24 update using the Q-Flash method (and 4 GB flash drive).
  29. This time it only took around 6 minutes and was able to boot successfully.
  30. I updated all configuration and turn back on the XMP.
  31. MacOS Monterey is running like normal now and I did some benchmarking to ensure it was performing like before the BIOS update (and hopefully I didn't short anything during this entire ordeal)
Based on this, does anyone think my motherboard is still fine? I am still within the return period. A bit concern I could short one or more components (CPU, GPU) even though everything seems to work now (Cinebench shows a score of 23,100 multi core and close to 2,000 for single core).

View attachment 568756
View attachment 568757
Click to expand...
On my DDR4 version, the update went smoothly. Casey's build is the DDR4 version. Looks like you're on the DDR5 version? If that's the case, you're post is slightly off topic.
 
ASUS P55 Series
P7P55D |  i5 750 |  Radeon HD 5570
ASUS Z170 Series
Z170-Deluxe |  i7 6700K |  Radeon HD 5770
GIGABYTE 6-Series
GA-H67N-USB3-B3 |  i3 2125 |  HD 3000
GIGABYTE 7-Series
GA-Z77X-UP5-TH |  i5 3570K |  HD 4000
GIGABYTE 9-Series
GA-Z97X-UD5H |  i7 4770K |  HD 4600
beelzebozo said:
On my DDR4 version, the update went smoothly. Casey's build is the DDR4 version. Looks like you're on the DDR5 version? If that's the case, you're post is slightly off topic.
Click to expand...

yeah I'm aware his build is DDR4, but the DDR5 version is very similar. The layout of the components are very identical.
 
statusquo said:
yeah I'm aware his build is DDR4, but the DDR5 version is very similar. The layout of the components are very identical.
Click to expand...
You should do a BIOS update on optimized settings first, then tweak your BIOS settings - for example XMP.
 
ASUS P55 Series
P7P55D |  i5 750 |  Radeon HD 5570
ASUS Z170 Series
Z170-Deluxe |  i7 6700K |  Radeon HD 5770
GIGABYTE 6-Series
GA-H67N-USB3-B3 |  i3 2125 |  HD 3000
GIGABYTE 7-Series
GA-Z77X-UP5-TH |  i5 3570K |  HD 4000
GIGABYTE 9-Series
GA-Z97X-UD5H |  i7 4770K |  HD 4600
Luisan said:
I am using bios F24 and everything is working except Bluetooth.
The Cinebench results are these.
Click to expand...
My Bluetooth works on F24.
 
ASUS P55 Series
P7P55D |  i5 750 |  Radeon HD 5570
ASUS Z170 Series
Z170-Deluxe |  i7 6700K |  Radeon HD 5770
GIGABYTE 6-Series
GA-H67N-USB3-B3 |  i3 2125 |  HD 3000
GIGABYTE 7-Series
GA-Z77X-UP5-TH |  i5 3570K |  HD 4000
GIGABYTE 9-Series
GA-Z97X-UD5H |  i7 4770K |  HD 4600
beelzebozo said:
You should do a BIOS update on optimized settings first, then tweak your BIOS settings - for example XMP.
Click to expand...
yeah, I had it on in optimized setting except for the XMP. It had issue restarting BIOS before so I wanted to make sure that wouldn't happen after a BIOS update.

My current BIOS is F24 after a long battle as described in the post above. The fact that it went to the firmware update screen instead of the BIOS update is weird (or even suspicious) to me but perhaps it required a firmware update before a BIOS update (based on Eclypsium's blog). The first attempt failed to go back to the BIOS update screen after the firmware update.

From the blog:
This backdoor appears to be implementing intentional functionality and would require a firmware update to completely remove it from affected systems.
Click to expand...

When you update your BIOS to F24, was there a firmware update before the BIOS update? (see my second image in the post above)
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top