Overclock.net banner
1 - 20 of 23 Posts

Bo55

· Registered
Joined
·
114 Posts
Discussion starter · #1 ·
Hi all, new to the forums, was hoping i could get some help from some of you, as I have just finished building my 1700x system with the Asus x370 Pro. The board overall seems pretty good, stable so far @ 3.8ghz 1.35v, has not crashed once but i cannot for the life of me get my memory to post higher than 2400mhz with whatever timings i use. I purchased the G.Skill F4-3400C16D-16GTZ 2x8gb Trident Z kit because i got them at a discount, i know its not on the QVL however what i find odd is that the Ripjaws V F4-3400C16D-16GVK is on that list, but according to that list will only boot at 2133.

My system specs are

1700x cpu @ 3.9ghz 1.35v
Asus X370 Pro
Trident Z F4-3400C16D-16GTZ
Msi Armor oc gtx 1070
Samsung 500gb 960 Evo
Corsair AX760 psu
Corsair H110i GT
Corsair 750D Air Flow Ed
Fresh Windows 10 64bit install

Things ive tried,

1. Currently running stable at 2400mhz 14-14-14-14-30 1.35v, even at CAS13 with or without CPU overclock.
2. Tested all BIOS versions from 0502-current 0515 and all wont let me boot over 2400mhz.
3. Increasing DRAM Voltage and other memory related voltages with no success.
4. D.O.C.P Profile at rated timings 16-18-18-38 wont post, even tried dropping the frequency down to 2666, does nothing.
5. Swapped the ram sticks around, have them in A2 B2 slots, nothing.

Im not sure what else i can do? Anyone else stuck in a similar position? Im hoping that Asus can fix this issue with future BIOS updates.
 
This question keeps coming up. Right now RyZen and particularly all mobos are suffering from this bug. Mobo manufacturers are releasing Bios to fix this problem. Just keep an eye for new Bios if you have not flashed yours to latest one do so.
 
It's not on the memory QVL I think.

What does it say in hwinfo64 under SDRAM manufactuerer? Does it say Samsung or Hynix?

Have you tried looser timings?
 
Discussion starter · #6 ·
Quote:
Originally Posted by AlphaC View Post

It's not on the memory QVL I think.

What does it say in hwinfo64 under SDRAM manufactuerer? Does it say Samsung or Hynix?

Have you tried looser timings?
Hwinfo says theyre Samsung. Ive tried from stock D.o.c.p timings up to cas20 with no luck even at 2666.
 
I have the TridentZ RGB 3600CL16 working at 3200mhz

Not sure I can help you though since I just set the DOCP profile and it just worked, apparently the 16-18-18-36 RGB doesn't work but the 16-16-16-36 do my previous kit of Corsair Dominator 3200Mhz had those 16-18-18 timings and they didn't work either and I tried everything.
 
Discussion starter · #8 ·
Quote:
Originally Posted by TaCRoT View Post

I have the TridentZ RGB 3600CL16 working at 3200mhz

Not sure I can help you though since I just set the DOCP profile and it just worked, apparently the 16-18-18-36 RGB doesn't work but the 16-16-16-36 do my previous kit of Corsair Dominator 3200Mhz had those 16-18-18 timings and they didn't work either and I tried everything.
Thanks for this, ive also read that people have been having luck with the 3600 kits, having said that, I dont want to go out and buy a 3600 kit though just to get it to work at 3200. It should just work from the get go. I guess i'll have to wait it out for a fix.
 
Quote:
Originally Posted by Bo55 View Post

Thanks for this, ive also read that people have been having luck with the 3600 kits, having said that, I dont want to go out and buy a 3600 kit though just to get it to work at 3200. It should just work from the get go. I guess i'll have to wait it out for a fix.
Yeah it's stable with intel burn test and no errors in windows memory diagnostic or memtest and that tends to do the trick, I notice memory issues straight away over 2400 in my old kit, chrome tabs will crash and windows eventually will BSOD.

I ordered these TridentZ last Friday after I heard similar reports of those kits working they weren't cheap but I luckily I got them $50 off as they were on sale and they cost less than the 3200 kit and they were the last ones in stock.
 
Got a HOF 3600C17 and it's fully stable at 2933C14.
3200C14 (14-14-14-14-36) DOCP runs well but i got some memory erros on memtest.
Losing timings didn't help and 3200 fully stable seems impossible.
At 3200, if i don't use the DOCP mode, the systemn won't even post.
BIOS needs more polish for sure.
 
Discussion starter · #12 ·
Well seems as though youre getting more luck than i am. My system will not post just from changing my frequency 2400-2666. Docp on or off, voltages up or left on auto. Its like it hits a wall at anything over 2400mhz. Im really hoping the next BIOS update will allow me to use the full 3400mhz. Or at the very least, allow me to run my system fine at 3200.
 
I don't see why you would, but you're not loading the profiles from XMP are you?

Also, try bumping the SOC voltage to 1.2-1.25V (should be 1.1V default). Gigabyte suggested this as a way to improve memory stability and people seem to find relatively high levels of success.
 
Discussion starter · #14 ·
Quote:
Originally Posted by Artikbot View Post

I don't see why you would, but you're not loading the profiles from XMP are you?

Also, try bumping the SOC voltage to 1.2-1.25V (should be 1.1V default). Gigabyte suggested this as a way to improve memory stability and people seem to find relatively high levels of success.
Ive tried both on or off and neither seem to do anything. Soc voltage does nothing, had it up to 1.10 didnt change a thing, not game to go higher at this point. Default is .822 with an auto offset of +.100 by the looks of it as ive seen it jump to .922 at most on Auto.

Just saw a post on reddit about a new Bios update for d/l 0604 for this board, havent tried it yet as its most likely a beta. Wonder if anyone has tried it yet?
 
Discussion starter · #17 ·
So ive just updated my bios to 0604 and everything is still very much the same in relation to memory overclocking except now i can POST at 2666 where as before i couldnt, it wont boot it freezes at the windows logo so im forced to restart, and the only way to get back into the bios is pull the cmos battery out then put it back in, then its fine. I tried ryzen master to get my memory clock further than 2400 with better luck surprisingly, it booted at 2666 got to my desktop then froze. So ive gone back to 2400mhz as its too much of a hassle to get it to run at anything faster. Still waiting for it to be fixed though.

On a good note, performance has gone up a little thanks to the updated AGESA code. So im happy about that
thumb.gif
 
Apparently if I use the 3200 DOCP profile the SOC voltage automatically bumps up to 1.1 from 0.9xx
 
Discussion starter · #19 ·
Ok so i managed to get a hold of single rank, Samsung B die based Trident Z sticks specifically F4-3733C17D-16GTZA (2x8gb) and installed them. I can report it worked instantly at 2933mhz timings 14-14-14-14-34, at this point in time it wont post at 3200 with the same or much looser timings (i tried up to CAS18), voltage adjustments make no difference either. Im sure with the upcoming AGESA release that will be fixed. There should actually be more choices in the frequency list in the bios OVER 3200 that people can just select and use instead of having to buy a CH6 and using BCLK to get frequency up. Im hoping that will be addressed in future bios update. Other than that, the system is solid at 2933.
 
1 - 20 of 23 Posts