Aorus X570 Master

[Cepheiden]

So I just found somebody with a b450 board that was willing to take his stuff apart, update his BIOS etc, so I can test my components.

Turns out I have a defective CPU.

My motherboard and my RAM both work just fine with his 2700x.

What where the odds?
Newest CPU, broken after 2 days / less than 6 hours of regular usage. Didn't even do a benchmark or anything before it stopped working.

 

[jesdals]

So I just found somebody with a b450 board that was willing to take his stuff apart, update his BIOS etc, so I can test my components.

Turns out I have a defective CPU.

My motherboard and my RAM both work just fine with his 2700x.

What where the odds?
Newest CPU, broken after 2 days / less than 6 hours of regular usage. Didn't even do a benchmark or anything before it stopped working.

Glad that you found that out - allways the worst error to detect

Done some testing of the new F7a bios today - and found some interesting sources to error in booting - all the settings shown below will lead to system boot failure and require a resetting of bios via the botton on the io-shield

As standard this is set to auto - disabling the function will cause a boot failure

Trying to set the PCH fan curve manually or to performance will cause a boot failure

I am using Pstates to set my cpu at 4500MHz all core - trying to set the ratio manually to 45x cause boot failure - even at higher Vcore
On a side note - I can boot at 4600Mhz using Pstates settings - but it demands vcore above 1.5 to maintain stanility - so 4500MHz seems to be the sweet spot for my cpu, do notice some vcore drop from the 1.45 setting and might try some additional settings for that

Trying to enable this emulation will also cause boot failure

In general the Gigabyte Aourus Master is a slow starter both normally and when you make changes to your bios settings - it can take as much as 3 minutes before it has run its cyles so patience is needed when making changes.

I found enabling fast boot removes the possibility to gain acces to bios and cant recommend that because you might have to reset bios to gain acces to it

Finally i did not find any noteworthy changes in performance between the F5I and F7a using Pstates setting to ajust cpu to 4500MHz all core. On both versions 4600MHz was possible at 1.5 vcore but both versions needed more vcore to become stable. Could not boot at 4625MHz all core on either version. With some vcore tweaking above 1.5 vcore it might be possible to run 4600MHz - but I prefer the temps at 4500Mhz 1.45 settings

 

[Chomiq]

^Have you contacted GB in regards to these issues?

 

[jesdals]

^Have you contacted GB in regards to these issues?

I have now

 

[Chomiq]

Latest BETA BIOS with AGESA 1003 ABBA (9/19)

Change log:

• We have a temporary work around for slow response when disabling CSM - hit CTRL-F6 in BIOS and select "VGA First". This will lower resolution, but should fix the lag.
• Disappearing SSD/HDD in boot priority should be fixed, let me know.

X570 AORUS Xtreme - F5B
X570 AORUS Master - F7B
X570 AORUS Ultra- F6B
X570 AORUS Pro Wifi - F6B
X570 AORUS Pro - F6B
X570 I AORUS Pro (ITX)- F6B
X570 AORUS Elite - F5B
X570 AORUS Elite Wifi - F3B
X570 Gaming X - F5B

 

[kirazero]

Where do you see F5n ...

X570 AORUS MASTER (rev. 1.0) Support | Motherboard - GIGABYTE U.S.A.

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...

www.gigabyte.com

Last i see is F5I


and look all these

x570 master d7 error | GIGABYTE USA Forum

Hi I have a x570 master with a big problem, it doesn't even come to bios, I tried to unplug all cables, to put another wings, other RAM on every single slot, another vga remains only the master t

forum.gigabyte.us

X570 Aorus master odd bios behavior | GIGABYTE USA Forum

So I got everything installed, was on bios F3. Updated to F5e as it is the latest on the website. Got booted back into Windows, and the firmware update tool popped up. It said I had an update. I let

forum.gigabyte.us

X570 Master - 3900X : Fails on 4x16Gb 3600Mhz XMP | GIGABYTE USA Forum

3900X X570 Master with F5g bios 4 x 16 Gb GSkill Trident Royal 3600 Mhz 19-20-20 1.35v Won't post when XMP is enabled. Entering manually the same spec result in the Bios or Windows fre

forum.gigabyte.us

their are A ton more .. but all basicly the same issue when you read them.



Its also not just the master .. the elite is having the same issue

Hello here I am, one of those who have encountered d7 I continue to experience the above problem, resolution only via q flash plus (only possible with usb 8gb maximum) meanwhile from the post I made on the gigabyte website, I tried three different x570 master, three different PSU, three different VGA, one 3700x, one 3900x, one 3600, one 3800x, eight different ram kit, various mice and keyboard, obviously uses various flashes of bios from F3 to the last f7b. ... Learn the pronunciation after a week or other after a simple reboot, absurd ....

 

[oxrufiioxo]

What I am seeing on the latest bios.

 

[Divide Overflow]

F7b bios now out. Not much info on the changes.

X570 AORUS MASTER (rev. 1.0) Support | Motherboard - GIGABYTE Global

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...

www.gigabyte.com

 

[Isturiel]

Hi guys,

I also had the 07 error on an Aorus Master with a 3700X and 2x 8GB G.Skill 1800Mhz CL15 (not explicitly on the compatibility list).

After building the PC and manually optimizing the RAM settings a bit (DRAM Calculator for Ryzen), my system run absolutely stable for 4 days. Suddenly the system went dark while I was playing a game. It was the 07 error and there was no way to get the PC back to life. Not with resetting or using QFlash. Not with the second BIOS or anything else mentioned in this thread (or at other locations).

After reading what a lot of you already went through, I decided to replace the CPU first. And it actually worked out. PC is running smooth again since a week now. I also updated BIOS to F7a (F7b is out now - wish the was a changelog...), but I doubt that has any influence on the 07 error chance. However I only did load the XMP settings for the RAM, no manual changes.

So my guess is there are really some 'bad charges' of CPUs out there (Europe/Germany here), maybe having issues with the Infinity fabric running at max speeds (what would still allow overclocking the RAM and much higher speeds than my 3600 since the infinity fabric speed is lowered). Or maybe it is possible to permanently wear out the CPUs RAM controller with tight settings somehow. Even without rising any voltage above the default.

However I do not fully trust Gigabyte yet. I will post again if there are any changes to my systems stability.

 

[TheLostSwede]

All the UEFI's from Gigabyte with a letter after the digit are beta releases and they might not have release notes.

However I do not fully trust Gigabyte yet. I will post again if there are any changes to my systems stability.

People have had this happening on MSI boards as well. Not sure about Asus or other brands, but it's not exclusive to Gigabyte.

 

[Chomiq]

Knock on wood, I've been running my rig for nearly a month now and it's doing fine. Doubt it's manufacturer's specific, might be a case of a bad CPU.

 

[nangu]

Hi, I found this thread just now so I didn't know the problems some people have with the Aorus Master.

I have the mobo since launch and didn't have any post problem at all. My build was just amazing from start. To add something to the table, I always had my mouse and keyboard plugged in the USB 2 ports, Bios versions F4 onwards, and didn't have any problems.

My ram kit is Gskill F4-3600C18D GTZRX (Hynix CJR), running at 3733MTs CL16 - 1866 Mhz IF and UMC.

For those having the D7 debug led code and unable to post until reflash, what are your VDDP and VDDG voltages? DRAM and SoC voltages?

Your problem seems dram related to me, either the ram sticks, or the associated voltages (SoC and/or UMC, dram vtt, etc), which in some time fails training and stuck the uefi code somehow.

I'm speculating here because I didn't have those problems at all, but I faced instability when those voltages are a little off range. Also, try without setting XMP, enter the timings and voltage for your kit manually, and set infinity fabric frequencies accordingly, and set UMCLK=MEMCLK. In later Bios versions, the motherboard set vSoC at 1.2v when XMP was selected, which is too high, try 1.1v by hand instead. DDRVTT can be left at auto, the motherboard sets it right, at half your memory voltage.

Also, I saw some people having trouble with Corsair memory kits on XMP, which are even in the QVL, hence why I reccomend to enter the values by hand. Try to avoid Hynix MFR kits on this board because it seems to not play well with it.

Try a lower frequency for the ram kit XMP rated value, at XMP timings.

I hope you can solve the problem.

 

[TheLostSwede]

New Gigabyte beta UEFI's are out for some of their X570 boards, F7c in case of the Aorus Master.

GIGABYTE Latest Beta BIOS

Warning Some of beta BIOSes are still undergoing compatibility testing. GIGABYTE is sharing these BIOSes for testing purposes only and are not meant f

forums.tweaktown.com

So far, so good.

It's not possible to load settings saved from an older UEFI version, as someone suggested somewhere.

I might've missed this before, but there appears to be a setting for NVMe drives under IO settings now.
Interestingly, my WD Black drive has some self test options, that my Patriot Viper drive doesn't have.
I guess this might be one bonus you get with "big brand" SSDs.

 

[laxsar]

Happened to me a while ago, stuck on D7. Just some rudimentary PBO OC, nothing extreme.

Cleared CMOS (jumper and back button), resat RAM, moped.
Reflashed the BIOS (F7b) using the back Q-Flash+ button and it booted up. Peculiar.
I think the BIOS got corrupted when I fiddled with EasyTune.

Also, the reason why I was messing with EasyTune was my system was randomly rebooting while idle. Can't shutdown windows normally, had to use shutdown /s or the system will just restart. Temps were around 40c-50c idle and 60-65c load.

Otherwise, it has been running smoothly so far.

 

[Zach_01]

If anyone remembers I was having the same D7 like issue with the X570 Aorus Pro board. The board doent really have code display but have the 4 led and stuck many, many times at DRAM led, on a boot loop with CPU led quick flash. Every new BIOS release I was hoping for the fix. Last version F6b (Sept 17) and ~10 days after was giving me the same every now and then (once a day or once every other). Flashback and go on.
At some point 10 days ago I decided to mess with BCLK oc. The reason I wanted to start raise BCLK is that I wanted some CPU OC but not having the chip fixed on a certain speed/voltage. I wanted base clocks and boosting. I did try it in the past but was having some issues (even with 101MHz) with storage devices (HWiNFO stuck at ATA/SCSI scan) and chipset sensors (sometimes HWiNFO not report anything about chipset), and went back to 100. My main fear was data corruption if not somthing even worst than that.
This time I decide to raise chipset voltages to see if that would fix those issues. There are 3 voltages in BIOS regarding chipset.

1. PM_1VSOC (chipset core): 1000mV
2. PM_CLDO12: 1200mV
3. PM_1V8: 1800mV

I raise them to 1030, 1240 and 1840 and raise BCLK to 101MHz. I also put DRAM multi to AUTO with XMP on (3466, 16-18-18-18-36, 1.35) MCLK:UCLK:FCLK and keep CPU VSOC AUTO. All LLC was AUTO too.
After first reboot into Win all went well and I opened HWiNFO with no issues. Test the system and it was all fine.
What I noticed is that the board was giving the CPU VSOC 1.220V. Before that the CPU VSOC was at AUTO 1.080V and when I was doing 1800~1900MHz (MCLK:UCLK:FCLK) I was setting it to 1.100~1.125V. So after a couple of hours I set the DRAM to 1766 and kept the 1:1:1 ratio and 101 BCLK. After a day I set it to 1800, 1:1:1, 101. The board then changed by itself the CPU VSOC back to 1.080V. So I manually set it to 1.160 with CPU VSOC LLC to medium.

Ever since, and for about 9 days now the system is very solid, doing all kinds of stuff, with not 1 issue what so ever, and I never got stuck again on a bootloop with DRAM led on. I haven't tested yet to see if the raised CPU VSOC voltage or the PM chipset voltages is preventing the system to stuck at DRAM led (too lazy... sorry)

It would be very interesting to see if anyone else could replicate the same.

I will keep it this way for a few days more and I will go for 1833, 1:1:1, 101, CPU VSOC 1.180V

 

[oxrufiioxo]

Forgot to post this... Fastest Speed I could get with standard 1.35v

My 3200 Corsair kit is pretty crappy in comparison. They also will not boot properly on the Aorus Master even though they're on the QVL

 

[TheLostSwede]

I went an ordered another 2x 8GB sticks of the same RAM, popped them in and...
That's really insane, four sticks of 8GB at 3800MHz 1:1...

 

[Yasser.AK]

I have tried many types of memory and seen others use other brands I have not tried with the same issue ... I really dont think , its the memory at this point. As far as CPUs ... I have seen it on 3700,3800 and 3900... inless AMD has A huge issue with only the gigabyte boards ... ( i dont see anything like this with non-gigbyte). That leaves gigabyte .. some of us have the issue amd some dont ... I think their is A bad batch ..

and this is one of the worst experiences I have had building computers .. Have been doing this 1997 .. I have had issues, have done more then my fair share of RMAs ... but this is something else ... Like .. I feel bad in a few ways ... feel dumb that i cant solve it , feel bad having to call up newegg and RMA almost everything .. feel so confused ... and ripped off . I have to call Newegg again for another RMA .. this will be the 3rd in like 2- 3 weeks time .. however 2 were motherboard .. should not of RMAed the RAM ...

The gigabyte support was so bad, A few years back I had to use them for another motherboard .. and it was not bad at all .. And i know the guy back then was in the USA ... when you call now .. they are somewhere in Asia ... very rude and just want to get the call over with. ( i assume they are gettn alot of calls about this )

as far as this motherboard goes ... I do plan on exchanging it for something else .. going too wait till I have a few days left .. just to see and use that time to pick something else ... sucks cause this really looked to be the best of all the boards

Hi,

I have the same problem D7 and I have tried everything to fix this and followed every single step but still no post

My PC Specs:

CPU: 3700x
GPU: 2070 Super
PSU: Evga 850w
MOBO: Gigabyte Aorus Master
RAM: G-Skill 3600mhz

And yes Gigabyte customer service is garbage.

I don't know what should I do? Replace my MOBO to a new one or replace the RAMs or CPU or buy Asus MOBO?

 

[Calmmo]

Pretty sure this is meant to be a cpu issue (memory controller).

In other news I sent back mine, doa, master wouldn't power on out of the box. It would start in flashback mode but that's about it.
My zen2 saga continues, ordered everything in july, i've yet to manage to put together the build due to several different issues

 

[TheLostSwede]

Hi,

I have the same problem D7 and I have tried everything to fix this and followed every single step but still no post

My PC Specs:

CPU: 3700x
GPU: 2070 Super
PSU: Evga 850w
MOBO: Gigabyte Aorus Master
RAM: G-Skill 3600mhz

And yes Gigabyte customer service is garbage.

I don't know what should I do? Replace my MOBO to a new one or replace the RAMs or CPU or buy Asus MOBO?

Judging by how others have solved this, CPU RMA, unless UEFI F7b/c solves it.

 

[Yasser.AK]

Judging by how others have solved this, CPU RMA, unless UEFI F7b/c solves it.

nope. I tried F7b still getting D7

 

[TheLostSwede]

nope. I tried F7b still getting D7

It's 07, but yeah, try a CPU RMA.

 

[Zach_01]

I solve it by giving CPU SOC 1.2V
Since this (almost a month) never had it stuck again at boot loop and DRAM led on. Never had to flashback it again.
And I’m running 1900MHz 1:1:1
Previously it was very common to get boot loop and forced to flash it. Every day or every 2-3 days at best.

Has anyone tried that?

 

[TheLostSwede]

F7e beta UEFI is out.

GIGABYTE Latest Beta BIOS

Warning Some of beta BIOSes are still undergoing compatibility testing. GIGABYTE is sharing these BIOSes for testing purposes only and are not meant f

forums.tweaktown.com

 

[jesdals]

got some new ram and is going for the 1900MHz mem and infinity setting.

No luck with 1900MHz so far only