Overclock.net banner
5,081 - 5,100 of 20,108 Posts
Thanks for your tips mate. I had power down already disabled. I traced it back down to VSOC. I compared the following settings and was able to reproduce the instability.

VSOC 1.1v VDDG 1050mv LLC VSOC extreme = stable
VSOC 1.1v VDDG 1050mv LLC VSOC low = unstable
VSOC 1.05v VDDG 950mv LLC VSOC extreme = unstable

Which is interesting since my $75 costing Mortar MAX. Is just plug and play setting timings for memory and all other settings auto and I can even put VSOC on 1.05v and VDDG on 950mv. No need to fiddle with LLC or voltages at all. Gigabyte really needs to work on the auto settings in bios and improve stability for these expensive boards. If MSI can do it for a $75 dollar board, I'm sure a board costing 3-5 times as much costing board should be able to do that. It's a bit shameful.

I do realise the Mortar is something special for it's price but still.
Nice to see you having found the issue. But as soon as your memory goes higher than 2933MHz the default SOC should be 1100mV, CLDO VDDG 1150mV & CLDO VDDP 1100mV.


CLDO VDDG is always 50mV higher than what it actually draws. Also, both, VDDG & VDDP can never exceed SOC voltage. Just something to keep in mind.
 
I have 4x8GB Trident Z Cl14 3200Mhz, (F4-3200C14D-16GTZ)

Aorus Elite(F11) and ryzen 5 3600

right now I use 3200 14-14-14-14-28 , DRAM Calculator for timings, 1.38V

what can I expect about it? 3600Mhz CL16 is doable with 4 slots?

I can't disable Gear Down Mode without W10 BSOD
Well 4 Sticks is harder on the Memory Controller – your mileage may vary… ;-) – I can only go up to 3580 MHz…with 4x16GB G.Skill TridentZ rated CL14@3200.

DRAM calc says Gear down enable and Power down disable - at least for my set up…

Greetings,
Medizinmann
 
Hello,

BCLK 102, 1usmus Powerplan, Offset for Vcore -0,075V, TDC 700A, PPT 1300W, EDC 0, Scalar Auto, Overboost 0Mhz, VRM LLC Vcore Extreme, CPU-VRM High or Turbo...

Unicorn is also caught with BOOST up to 4,69GHz on two cores…

I get Z-CPU SC 555 and 8550 Multi - which is a little less than before (564/8660) but with 126W instead of 150W.

Got also my highest Timespy ever with 16080...CPU-Score 13736

Greetings,
Medizinmann
Looks kinda similar to my settings. I'm glad my hint for -0,075 has helped you reach stability :p

I have been testing all settings between -0,075 and -0,050 , and setting -0,033 today and there is variation between all of them but -0,075 is still the best stability/performance ratio.

Setting a higher BCLK without using PBO is useless in my tests, PBO will make higher clocks possible with higher BCLK.

Cheers.
 
Well 4 Sticks is harder on the Memory Controller – your mileage may vary… ;-) – I can only go up to 3580 MHz…with 4x16GB G.Skill TridentZ rated CL14@3200.

DRAM calc says Gear down enable and Power down disable - at least for my set up…

Greetings,
Medizinmann

thanks you for the answer, maybe I try later, what are your timings?
 
Well 4 Sticks is harder on the Memory Controller – your mileage may vary… ;-) – I can only go up to 3580 MHz…with 4x16GB G.Skill TridentZ rated CL14@3200.

DRAM calc says Gear down enable and Power down disable - at least for my set up…

Greetings,
Medizinmann
Yes latest 1.6.2 says gear down enabled but it's practically impossible to run it like that. Trust me I've tried. Need to lower clockspeeds or raise voltage insanely high with almost no benefit. It's just not worth it. 1.5T is fine.
 
Nice to see you having found the issue. But as soon as your memory goes higher than 2933MHz the default SOC should be 1100mV, CLDO VDDG 1150mV & CLDO VDDP 1100mV.


CLDO VDDG is always 50mV higher than what it actually draws. Also, both, VDDG & VDDP can never exceed SOC voltage. Just something to keep in mind.
VDDP is 900mv on auto. Which is fine.

I ran 3800 CL16 on my Mortar with VSOC 1.05v VDDG 950mv VDDP 900mv with the same processors. NO PROBLEMS WHATSOEVER. This board and bios is just super picky. Anyway. Stable is stable. Just ran another Karhu memtest together with Heaven loop. 5000% stable. Last night was 10000% just Karhu. No crashes. And then I left the PC to idle for a couple of hours and no issues either. But it's a curious thing why the VSOC LLC needs to be on High or Turbo to be stable.
 
Yes latest 1.6.2 says gear down enabled but it's practically impossible to run it like that. Trust me I've tried. Need to lower clockspeeds or raise voltage insanely high with almost no benefit. It's just not worth it. 1.5T is fine.
Well - works for me...but this could really depend on the RAM itself (I use Samsung B-die), the board etc...

Greetings,
Medizinmann
 
Well - works for me...but this could really depend on the RAM itself (I use Samsung B-die), the board etc...

Greetings,
Medizinmann
I tried with both my B-die 3200C14 kits and my E-die kit. Both kits did not like it. Both on my MSI Mortar MAX, non-MAX and just tested it on my Pro Wifi, same story. it starts out spewing errors straight away the moment I turn off GD and barely any improvement in AIDA bandwidth 200MB/s on read and 300MB/s on copy, no improvement in latency. Seems not worth it to me at all.

Any steps you take to run it with gear down disabled other than the calculator settings?
 
I tried with both my B-die 3200C14 kits and my E-die kit. Both kits did not like it. Both on my MSI Mortar MAX, non-MAX and just tested it on my Pro Wifi, same story. it starts out spewing errors straight away the moment I turn off GD and barely any improvement in AIDA bandwidth 200MB/s on read and 300MB/s on copy, no improvement in latency. Seems not worth it to me at all.

Any steps you take to run it with gear down disabled other than the calculator settings?
Well besides ramping up VRM Settings for Vcore - no…actually never thought much about it - just putting in the settings from DRAM Calc...:D

Greetings,
Medizinmann
 
Well besides ramping up VRM Settings for Vcore - no…actually never thought much about it - just putting in the settings from DRAM Calc...:D

Greetings,
Medizinmann

Thanks Medizinmann! All your responses today have been helpful. I'll give it another shot and come back with my results. My B-die isn't as high-quality as yours (3200 CL15), but I'm convinced I can at least reach the 3200 mark, instead of 3133.
 
Yes latest 1.6.2 says gear down enabled but it's practically impossible to run it like that. Trust me I've tried. Need to lower clockspeeds or raise voltage insanely high with almost no benefit. It's just not worth it. 1.5T is fine.
THIS. 1T really is very difficult to get anywhere stable. 2T is silly, gear down is the way to go. Agree 100%
 
Yes latest 1.6.2 says gear down enabled but it's practically impossible to run it like that. Trust me I've tried. Need to lower clockspeeds or raise voltage insanely high with almost no benefit. It's just not worth it. 1.5T is fine.
THIS. 1T really is very difficult to get anywhere stable. 2T is silly, gear down is the way to go. Agree 100%
Yeah even buldzoid mentioned it in his videos. He said it's a free easy stabilizer allowing for much higher clocks and tighter timings for free without much performance loss compared to it off. I can run Aida with it off but it doesn't make any relevant difference in performance at 3800Mhz cl16 and running a memtest will spew put errors straight away.
 
In the DRAM Calculator, I've heard that the "Frequency (MT/s)" section should be set on what the ram is rated for. Some have said "start with the rated timings", which means (to me) that you use this field to calculate higher timings if you choose to go higher.

Is this true, or do you use that field to calculate higher speed? (i.e. - I have 3200 ram, but want to hit 3800, so I put 3800 in the field)
Or do you set your stock value, use the values the calculator gives you, and manually increase the speed?
 
I tried with both my B-die 3200C14 kits and my E-die kit. Both kits did not like it. Both on my MSI Mortar MAX, non-MAX and just tested it on my Pro Wifi, same story. it starts out spewing errors straight away the moment I turn off GD and barely any improvement in AIDA bandwidth 200MB/s on read and 300MB/s on copy, no improvement in latency. Seems not worth it to me at all.

Any steps you take to run it with gear down disabled other than the calculator settings?

Sorry for the misunderstanding - but I wrote "Gear down enabled" and "Power down enabled" - see Port #5082 - that is what DRAM Calc says...


Greetings,
Medizinmann
 
In the DRAM Calculator, I've heard that the "Frequency (MT/s)" section should be set on what the ram is rated for. Some have said "start with the rated timings", which means (to me) that you use this field to calculate higher timings if you choose to go higher.

Is this true, or do you use that field to calculate higher speed? (i.e. - I have 3200 ram, but want to hit 3800, so I put 3800 in the field)
Or do you set your stock value, use the values the calculator gives you, and manually increase the speed?

You need to read out XMP first...


Either use Thaiphoon burner or try the R-XMP button in DRAM Calc (which didn't work for me - the R-XMP button I mean ;) ...)


Then you can use any speed you want do calculate your settings. It is a good start to start at rated or a little above to get a starting point.



Greetings,
Medizinmann
 
5,081 - 5,100 of 20,108 Posts