[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
CoUsT
Posts: 2 | Last online: 09.13.2017
Date registered
09.13.2017
Sex
not specified
    • CoUsT has written a new post "[OFFER] Gigabyte GA-AX370-Aorus Gaming 5 BIOS mod" 09.13.2017

      Zitat von ket im Beitrag #50
      I'd start by setting every voltage you aren't adjusting to the "Normal" value. The boards throw an insane amount of voltage at components otherwise when you start overclocking. I don't know if it would help with voltage stability that much but when I took the VRM heatsinks off the Gaming 5 I reviewed I saw that the heatsinks made extremely poor contact with the VRMs, something which I naturally promptly corrected as I didn't want anything melting on the board under high load tests and killing my other hardware. When I corrected the poor contact problem I replaced the plastic standoffs with slitly lower rubber ones and replaced the thermal pads with Laird 6W/mk pads, the very same NASA used to use on the space shuttle. The most stable LLC setting I found was "High", it still wasn't perfect but it kept the voltage stable at the baseline that was needed for 3.82GHz. I wasn't impressed by the voltage bouncing all the way up to 1.39v though. Put bluntly, the VRMs on the Aorus Gaming 5 at least are crap. The kind of voltage stability I saw I would expect to see on a cheaper A320 or B350 board, not an X370. I would say Gigabyte should be ashamed of themselves... but well, look of the state of the UEFI for these boards Gigabyte positively revel in the same company as the word "poor". I wouldn't value Gigabytes boards at anything more than the cost of the box they arrive in, they are junk that looks pretty with their flashing lights and nothing more.


      Yes, the first thing that I ever did was changing voltage. When I saw 1.224V on SOC after flashing new BIOS when I first got it I knew I have to change it. I also noticed that RAM voltage is actually 0.02V higher than you set it in BIOS, so 1.35 is 1.37, 1.36 is 1.38. Perhaps Gigabyte did that to make their motherboard "more stable" than other companies.

      Do you think heatsinks will help with voltage? Temp on my VRM is perefctly fine, usually 50-60 with medium-high load. Getting up to high 60-low 70 during stress tests.

      The only problem for me is that huge vdroop and strange readings on sensors with voltage up to 2.744V and weird 600W power consumption. LLC High still gives me 0.04V vdroop but it's better than Auto.

    • CoUsT has written a new post "[OFFER] Gigabyte GA-AX370-Aorus Gaming 5 BIOS mod" 09.13.2017

      Zitat von ket im Beitrag #41
      Hah! I doubt that would be said if they read the first post here. Gigabyte are slacking, and lazy, compared to the competition. It's that simple. I use an Asrock X370 Gaming K4 that absolutely blows the Gigabyte boards out of the water in both the quality of the UEFI and choice of hardware components the board uses. An example; the Aorus Gaming 5 test board I have to set 1.35v for the CPU to have it stable @ 3.82GHz and the voltage bounces arounnd all over the place ranging from 1.33v - 1.39v. The K4 on the other hand for 3.82GHz I set 1.32v and I actually get 1.32v and it is rock solid.

      Gigabyte are utterly failing. They can't even get the "Auto" voltage settings right. Just look at the SOC voltage, if left on "Auto" when overclocking it will skyrocket to 1.25v! That is absolutely not necessary, 1.1v is more than enough. If you want you can also tell Gigabyte I expect something from them for my time doing what they can't be bothered to do.


      Hello there. Because it seems like you have decent knowledge about MoBo and BIOSes, I would like to ask for your opinion.

      I posted one issue on Gigabyte forum twice and contacted Gigabyte support once about this but can you please take look at this and tell me what you think about this?

      Here is the link to my Gigabyte forum post:

      http://forum.gigabyte.us/thread/1542/ori...&scrollTo=11360

      Basically, what you said is true. Voltage is fine during idle - I set 1.125V with 3.52 GHz and its great. I run stress test and voltage drops hard to 1.075V on LLC Auto. That's 0.05V vdroop! LLC Auto is somewhere between Normal and High. After setting it to High I'm getting about 0.04V vdroop, from 1.125V to about 1.087V. Changing LLC to Turbo (one step higher from High) helped with voltage a lot - I had only 0.02V vdroop but it was overvolting a little bit sometimes up to 1.144V for a split second when going from full load to idle. Not that bad considering better stability and possibility to drop voltage down in idle/low load.

      And here is where the problems start. For some reason after cold boot I got 1.188V once instead of the one that I set (about 0.05V higher). Changing voltage down by 2 steps, rebooting and up by 2 steps fixed it and it was back where it was before. Another issue is sensors going crazy, voltage going up to 2.744V or power usage up to 600W for a split second. Weird. Broken sensors? Or... LLC not working correctly, providing too high voltage/amps to the CPU for a split second?







      During tests it occured when I was @ 1.144V and 3.6 GHz with LLC Turbo and @ 1.3V and 3.8 GHz with LLC Turbo. I tried to stabilize 3.8 GHz as best as possible and started tuning LLC. LLC Auto would give me huuuge about 0.07V vdroop. That's 1.3V -> 1.23V. LLC Turbo helped but these weird issues started happening (mostly during gaming or medum usage).

      The only sensor that picked this up is the main Ryzen 1700 sensor. MoBo didn't pick it up, VRM sensors didn't pick it up. Perhaps an issue directly between VRM and CPU itself (so most likely LLC)?

      Changing LLC down from Turbo to High got rid of all these issues with wrong voltage + weird sensor readings so I'm almost sure LLC Turbo is the culprit here.

      Do you think it is because of not the best VRM or BIOS/LLC issue? Is there anything that you can suggest or do with this?

Recipient
CoUsT
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor