CLOVER-Z370-AORUS-Gaming-7 icon indicating copy to clipboard operation
CLOVER-Z370-AORUS-Gaming-7 copied to clipboard

Published 20 hours ago • verified publisher icon korzhyk

Gigabyte Z370 Aorus Gaming 7 - Problems after BIOS update

Open alex-munteanu opened this issue 5 years ago • 5 comments

I have the following configuration:

  • MB - Gigabyte Z370 Aorus Gaming 7 (non OP version)
  • CPU - i7 8700K
  • GPU - Sapphire Radeon RX 580 Pulse 8 GB
  • RAM - 16 GB G.Skill with code F4-3200C16D-16GVKB
  • SSD - Samsung 960 EVO M2 NVME 512 GB
  • SSD - Intel 180 GB SATA

I tried some time before to install mac on it, but back then had a Radeon R9 390 GPU and couldn't get that to work. Now I just got the 580 so wanted to try again.

First thing I did was to flash the BIOS in this repository. I was previously on the F11 version of the BIOS on the official Gigabyte website. Now I used the BIOS found in the Z370AOG7_F13RB.zip file and flashed using @BIOS in Windows. Flash went successfully, but when it restarted the PC, it went into a boot loop and never started again. It doesn't get to the point where it shows any image on the screen, and it stops and restarts continuously. The codes that the motherboard shows are different when shutting down, but only one of them is shown in the manual as an error code, and that is 62 ("Installation of PCH runtime services"). I tried with the RX 580, with the integrated GPU and with the old R9 390, but none of them works.

Has that ever happened to you guys? Is there any chance to recover the motherboard, or is it bricked?

alex-munteanu avatar Dec 15 '19 01:12 alex-munteanu

@aaxelm so sad to hear this, but I try to help you. The first of all Z370AOG7_F13RB.zip contain official bios firmware from Gigabyte support and signed by Gigabyte aswell.

To recover you mobo from boot loop follow this spets:

  1. Turn off PSU and unplug power cord
  2. Remove battery from the mobo
  3. Push power button for 5 seconds and follow this steps in back order.

korzhyk avatar Dec 15 '19 10:12 korzhyk

Thank you @korzhyk but unfortunately this didn’t work. Still the same outcome. :(

alex-munteanu avatar Dec 15 '19 13:12 alex-munteanu

I think the problem with corrupted firmware but with correct CRC. In this case Gigabyte Dual Bios can't start recover process. There a trick to start recovering BIOS but this is not related to this project and I can't garant is this safe enough to not brick your mobo.

korzhyk avatar Dec 15 '19 13:12 korzhyk

Since the mobo doesn't work currently and I am not sure I can RMA it, can you tell me about the trick you know of to start recovering the BIOS? In case it is not ok to write it here because it is not related to this project, you can indicate a different project where to write about this or you can email me at [email protected]

Thanks, @korzhyk !

alex-munteanu avatar Dec 15 '19 18:12 alex-munteanu

@aaxelm just google it «How to force Gigabyte motherboard to boot in the backup bios»

korzhyk avatar Dec 16 '19 21:12 korzhyk