Overclock.net › Forums › AMD › AMD Motherboards › Gigabyte GA-AX370-Gaming K7 Discussion
New Posts  All Forums:Forum Nav:

Gigabyte GA-AX370-Gaming K7 Discussion - Page 35

post #341 of 1630
Quote:
Originally Posted by mus1mus View Post



@colorfuel

I repeated the F9 issue. biggrin.gif
If you get into a bootloop of F9, hitting the CMOS SW on the board (beside Reset SW) you will go into issues like 0d or 07. BUMMER!

thumb.gif


So what does that mean. I'm stuck at 2933Mhz?

I have a feeling, the Ram speeds are more dependent on the CPU than the board, since many people achieve better Ram speeds with the same board on the same Dimms. This is a bummer, since you cant fix the CPU with a bios update.
Hope (for AMD)
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD 1700X Gigabyte AX-370X-Gaming K7 Sapphire Tri-X 290X new edition G.SKILL Flare X Series 16GB - F4-3200C14D-16GFX 
Hard DriveHard DriveHard DriveHard Drive
SAMSUNG SSD 960 EVO 250GB Crucial M4 CT256M4 Crucial CT500BX Western Digital WD10EZEX 
CoolingOSMonitorPower
Thermalright HR-02 Macho Rev.A (BW) Windows 10 Fujitsu P24W-6 IPS be quiet! Straight Power E9 CM 80+Gold 580W 
CaseMouse
Fractal R4 Logitech Performance MX 
  hide details  
Reply
Hope (for AMD)
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD 1700X Gigabyte AX-370X-Gaming K7 Sapphire Tri-X 290X new edition G.SKILL Flare X Series 16GB - F4-3200C14D-16GFX 
Hard DriveHard DriveHard DriveHard Drive
SAMSUNG SSD 960 EVO 250GB Crucial M4 CT256M4 Crucial CT500BX Western Digital WD10EZEX 
CoolingOSMonitorPower
Thermalright HR-02 Macho Rev.A (BW) Windows 10 Fujitsu P24W-6 IPS be quiet! Straight Power E9 CM 80+Gold 580W 
CaseMouse
Fractal R4 Logitech Performance MX 
  hide details  
Reply
post #342 of 1630
Does the K7 have a CMOS reset button or do you have to use a CMOS jumper after a bad OC?
Gaming PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
AMD RYZEN R7 1800X @4Ghz Asrock x370 Fatal1ty Professional Nvidia GTX 1080 G.SKILL TridentZ RGB Series 16GB (2 x 8GB) 3200... 
Hard DriveHard DriveHard DriveCooling
Samsung 840 Pro 256GB SSD Samsung 850 Pro 512GB SSD Samsung 850 EVO 1TB SSD Corsair H100i 
OSMonitorKeyboardPower
Microsoft Windows 10 Pro 64-bit Samsung 49KS8000 Corsair K70 RGB Corsair AX1200i 
CaseMouseMouse PadAudio
Cooler Master Mastercase Maker 5  Corsair M65 RGB Custom SF 49ERS mouse pad Philips X1 headphones with V-MODA BoomPro mic 
Audio
Sound BlasterX Katana 
  hide details  
Reply
Gaming PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
AMD RYZEN R7 1800X @4Ghz Asrock x370 Fatal1ty Professional Nvidia GTX 1080 G.SKILL TridentZ RGB Series 16GB (2 x 8GB) 3200... 
Hard DriveHard DriveHard DriveCooling
Samsung 840 Pro 256GB SSD Samsung 850 Pro 512GB SSD Samsung 850 EVO 1TB SSD Corsair H100i 
OSMonitorKeyboardPower
Microsoft Windows 10 Pro 64-bit Samsung 49KS8000 Corsair K70 RGB Corsair AX1200i 
CaseMouseMouse PadAudio
Cooler Master Mastercase Maker 5  Corsair M65 RGB Custom SF 49ERS mouse pad Philips X1 headphones with V-MODA BoomPro mic 
Audio
Sound BlasterX Katana 
  hide details  
Reply
post #343 of 1630
MBO is here,
RAM is ordered Flare-X 3200, pricy but i managed to get without VAT(25% in my country) that brings price to more normal levels but IMHO its still overpriced

Now only question is CPU:

r5 1600 with cooler
r5 1600x + cooler

Exciting times smile.gif
Old chap...
(14 items)
 
  
CPUMotherboardGraphicsRAM
Xeon E5450 GA-P35-DS3L MSI 750ti Patriot 
Hard DriveHard DriveHard DriveCooling
Samsung 850 Pro Samsung 850 Evo WD Blue Arctic Freezer 13 
OSMonitorKeyboardPower
Windows 10 64bit Phillips 1680x1050 Logitech Antec Edge 750w 
CaseMouse
Fractal Design R5 Black Edition Logitech 
  hide details  
Reply
Old chap...
(14 items)
 
  
CPUMotherboardGraphicsRAM
Xeon E5450 GA-P35-DS3L MSI 750ti Patriot 
Hard DriveHard DriveHard DriveCooling
Samsung 850 Pro Samsung 850 Evo WD Blue Arctic Freezer 13 
OSMonitorKeyboardPower
Windows 10 64bit Phillips 1680x1050 Logitech Antec Edge 750w 
CaseMouse
Fractal Design R5 Black Edition Logitech 
  hide details  
Reply
post #344 of 1630
Overclock your way thru the K7or any Gigabytes? biggrin.gif
Quote:
Originally Posted by Oceaon View Post

Mus1mus since you seem to be at the forefront of this board do you think you could write a Overclockers Guide like the Asus version?

Okay, so here's how I am doing it.


But first up, BIOS is F3D. Yours might be a little different.
Warning: Spoiler! (Click to show)



So let's begin. The BIOS is quite plain and pretty simple with fairly limited options to tweak.
Focus on the M.I.T Tab. All OC related stuff should be here.
Warning: Spoiler! (Click to show)



Power Saving options
You will need OFFSET Voltages if you want to keep the downclocking scheme during IDLE. I am not doing that and you will see why.
Warning: Spoiler! (Click to show)



Memory Related stuff.
Notice the DDR Compatibility Mode? More of that later.
Warning: Spoiler! (Click to show)




Voltage
You will need to use Offset if you want to use power saving stuff.
I don't do that as well, I don't like it. And on this board, we'll try to see how the Voltage reflects the given offset values. Warning: Spoiler! (Click to show)


Interesting part here.
PCIE Mode should be set to 2.0 or 1.0 if you are pushing BCLK past 107MHz. Warning: Spoiler! (Click to show)


Fan related optimisations. Warning: Spoiler! (Click to show)





To get a good grasp of things, here are the stock Benchmarks results.
For the GPU it's a GTX 1060 6GB OC'ed to +175/700. Hovers around 2100MHz Core and 4700Mem.

Warning: Spoiler! (Click to show)









With a baseline in set, let's go for the awaited part: biggrin.gif

Everyone has their own way of doing things. I would simply ask you to start Low. And note of the Voltage requirement your chip needs per 100MHz step.

Let's Begin.

I already knew that I can run 3.6GHz at 1.1 but since I wanted to make this mini guide, I just fired it up and try Offset Voltages.

Warning: Spoiler! (Click to show)


Enabled XMP Profile,
Multi to 36
BCLK to 100.1 ( I don't want to see it like 3598MHz you know)
Went into the Memory Options.

Warning: Spoiler! (Click to show)


Enabled DDR Compatibility Selection
Memory Timing Mode to Advanced Manual. This allows you to get overall control to the Memory Timings. A handful tongue.gif
Next went into Memory Subtiming settings.

Warning: Spoiler! (Click to show)


Manual Input. tRCDWR allows that without an impact to Stability witha tiny bit improvement in Performance. 8 is the lowest I have seen the gains.
Went into the Voltage Options and tried using Offset.
1.45V on the Dimms. (Note I am using 4 sticks here. 2 sticks requires less than that.)
0.755V on DRAM Termination (I'd like to just give it a tiny bit more) Supposedly Half of VDIMM.

Warning: Spoiler! (Click to show)


Rebooted back into the BIOS.
Simply to verify if the Changes made will pass Post Tests. Especially on the Memory.
And to verify the Voltages as well.

Warning: Spoiler! (Click to show)


Passed! wew. BUT,
Opps, VCore is around 1.35 whistle.gif
To verify the Voltages and Frequency, you can just hover the Mouse pointer to the Right-side of the screen and that will show the semi-pull-up display screen.
Went back into the Voltage settings again to change the Offset.

Warning: Spoiler! (Click to show)


So, at +0.0000 Vcore = 1.344 mad.gif
Tried -0.100

Warning: Spoiler! (Click to show)


1.25V Perfect!
But then it's still quite HIGH for my 3.6GHz.
Back to Voltage Settings again. Then, opps! Another surprise!
Offset only goes down to -0.150 V; That equates to the lowest VCore I can DIAL using OFFSET is 1.200V!

Warning: Spoiler! (Click to show)


Every chip will likely have different values for these so verify yours.

Warning: Spoiler! (Click to show)


PC Health Status confirms that as well.
While VSOC at +0.000 = 1.116V.

Warning: Spoiler! (Click to show)


Since I knew that 1.2 is too much for my 3.6GHz OC, I decided to just go for 3.8GHz and test it in Windows but that failed IBT at Regular.
I wanted to at least run it 20X at Very High. So went back to the Voltage Settings and went -0.13750V.
Also did change VSOC to -0.100
I love this Voltage Granularity! thumb.gif

Warning: Spoiler! (Click to show)


IBT Very failed at 23rd iteration.
Usually, I could just maintained that Vcore as IBT Very High is pretty much as heavy as you can go with these chips.
But since we also wanna test the Memory and the Data Fabric due to running 32GB of 3200MHz RAM, we want to get rid of that minute possibility of failure induced from Core instability.
Went back and added a tiny bit more Voltage there as well.

Warning: Spoiler! (Click to show)



Overclock results.

3800 CPU / 3200 RAM
Cinebench (Click to show)
X265 BEnchmark 1080P (Click to show)
X265 Benchmark 4K (Click to show)
CPU-Z Benchmark (Click to show)
Firestrike Physics (Click to show)
Temps and Stability (Click to show)


3900 CPU / 3200 RAM
Cinebench (Click to show)
X265 BEnchmark 1080P (Click to show)
X265 BEnchmark 4K (Click to show)
CPU-Z Benchmark (Click to show)
Firestrike Physics (Click to show)


ISSUE:
Can't get my RAM to post to 3200MHz.
Q-Code F9.

Warning: Spoiler! (Click to show)
This has been a known issue. And I think I may have found the cure.
It involves patience at the moment so guess, you'll find virtue in it. biggrin.gif

Let's begin.

Q-Code F9 is described as a Recovery Capsule not found issue. Not sure what that is. But it is a continuous boot loop for these boards.

Remedy? Here are just the steps I have taken.

Test set-up:
Gigabyte K7 board.
G.Skill Ripjaws4 F4-2400C15Q-32GRK 15-15-15-35-2T 2400MHz
I choose this kit as I haven't been able to successfully use this past 2400 on any platform! X99, Z170 etc.

Needed - Debug speaker.
This is important for my diagnostic and technique later.

Step 1.
A CMOS clear is needed - pull the battery out for 10 minutes with the PSU Turned Off or disconnected from the mains.

Step 2.
Proper knowledge of your kit - be sure to know default Timings and Voltages to use. Use timings like 16-18-18-18-36 to start with.

Step 3.
Debug speaker will beep on faults the motherboard encounters on Post. F9 is a 3-beep-sequence.

Step 4.
Insert your sticks on the Slots nearest the CPU.
Install the CMOS battery.

Step 5.
Upon entering the BIOS after the CMOS clear method in step 1, Press F7 to restore default settings.
F10 and reboot to BIOS.

Step 6.
Enter your usual CPU OC settings with DRAM Profile enabled.
Compatibility Mode enabled.
Expert Manual and use timings like 16-18-18-18-36 for 3200 TridentZ kits.
Use your OC Voltages with DRAM Voltage set to 1.45 for TridentZ kits, DRAM Termination to 0.75. - I found that boosting it a little from the half DRAM Voltage value helps a bit.

Step 7.
Before saving the setting and trying to post, save it as a Profile first. Easy way to come back to where you left at when things go awry.
Try to reboot to BIOS.

My settings for Micron chips after I have successfully booted them.







Step 8.
Here we are at the exciting part. If you don't get this far, you might have made it with F9 debug halt. biggrin.gif

F9 like I said, sends a 3-beep - reboot - 3-beeps - reboot loop on the debug speakers.

The technique is Long Pressing the Power Button at the sign of the first 3-beeps to force a shut down, release and hold again as described.
3-beeps > hold power button > shutdown > release > Press to power up again.
3-beeps > hold power button > shutdown > release > Press to power up again.
3-beeps > hold power button > shutdown > release > Press to power up again.

After the 3rd cycle (assuming you did it right), the debug speaker will beep for about 2 seconds.
That's your que, stop pressing the Power Button as the board will reboot into the BIOS without clearing it up.
The CPU clock will stick as per your settings. But the memory will go back to 2133 15-15-15-15.

Step 9.
Adjust your timings to make it looser like 18-18-18-18 or adjust the Vdimm and DDR VTT accordingly til the board boots normally.
Repeat step 8 if you continue to encounter Q-Code F9 loop.


It may come as a annoying as you might have the TridentZ 3200C14 or any other sticks for that matter. But there are things you just can't deny with these chips. redface.gif
Once you have successfully booted with the intended RAM clock, try to go back to DRAM timings and tighten up the CAS Latency Timing. And try to reboot to BIOS and Windows.
Verify stability and or go back to the Timings section to adjust another timing to pinpoint which one prevents you from booting into your desired DRAM clock.

Proof:



UPDATE: F9 issues smile.gif

For those who have no access to a debug speaker, but are keen enough to observe the board behaviour relating to F9 boot loop issue, I have found 2 distinct characteristics of the mentioned fault.

1. F9 (3 beeps) > board restart > F9 > board restart loop.
This is the loop I have mentioned in the guide above.

Assumption: CAS Latency too low.

Fix: Increase CAS Latency value in the Memory Settings a step.

So uf your previous setting as 3200-14-14-14-14-34 fails with the loop described, try to set it to 3200-15-15-15-15-35 and try to reboot. It will likely default to 16-15-15-15 anyway. smile.gif

2. F9 (continues 3-beep sequence) > Q-Code shuffle > F9 > Q-Code Shuffle loop

This one differs from the issue mentioned above as this doesn't force a board restart.

Assumption: TRCD and/or TRP too low. Usually, TRCD.

Now this is the tricky part as it is not shown as TRCD in the BIOS. But rather, TRCDRD.

This became apparent when I am tweaking my timings for the Micron Kit I have posted.

The said kit accepts (boots normally) with timings 16-20-20-20-36. But fails to boot into Windows with 18-18-18-18-38, but works okay again with 16-19-8-16-36.

See the pattern?

Hopefully this helps.
Memory OC end Result using Micron chips (Click to show)

Edited by mus1mus - 4/9/17 at 5:52pm
post #345 of 1630
Quote:
Originally Posted by colorfuel View Post

So what does that mean. I'm stuck at 2933Mhz?

I have a feeling, the Ram speeds are more dependent on the CPU than the board, since many people achieve better Ram speeds with the same board on the same Dimms. This is a bummer, since you cant fix the CPU with a bios update.

I would try it again if it's me. thumb.gif

I posted my mini-guide. Try to do that on a very clean BIOS. Pull the CMOS Battery before you sleep later. So in the morning or before you go back to the system, it's surely is pretty drained of any thing. biggrin.gif
post #346 of 1630
Quote:
Originally Posted by Scottland View Post

I thought most of Corsair used Hynix?
I was basing it off of this
https://www.techpowerup.com/231518/amd-shares-details-on-ryzen-ddr4-memory-support-and-upcoming-am4-updates
Edited by THUMPer1 - 4/7/17 at 5:32am
My System
(11 items)
 
  
Reply
My System
(11 items)
 
  
Reply
post #347 of 1630
Quote:
Originally Posted by mus1mus View Post

Overclock your way thru the K7or any Gigabytes? biggrin.gif
Okay, so here's how I am doing it.


SNIP


I will edit this post later to show my test results. thumb.gif
Benchies too at 3.8GHz.
And probably further guide for max OC. tongue.gif

So you aren't using offset voltage...Right?I can't even change that option (DVID), it's grayed out. Did I miss something?
Edited by THUMPer1 - 4/7/17 at 6:05am
My System
(11 items)
 
  
Reply
My System
(11 items)
 
  
Reply
post #348 of 1630
You first need to set the VCore or VSOC to Normal. That way, the offset is enabled.
post #349 of 1630
Quote:
Originally Posted by mus1mus View Post

You first need to set the VCore or VSOC to Normal. That way, the offset is enabled.

People are lucky they have someone posting this info. When I got my Gigabyte G1 there wasn't a lot of info about this. Took google and a lot of trial and error to figure out DVID. Even then the guides I found weren't accurate when compared to my personal experience. The actual voltage I would end up at was the part that took a while (lol).

I have a K7 coming early next week so catching up on things. My Gigabyte Z170 G1 found a new home long enough ago that I'm kind of rusty.
post #350 of 1630
Being a tweaker doesn't hurt eh? Wallet doesn't think so. tongue.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › Gigabyte GA-AX370-Gaming K7 Discussion