Ryzen 7 2700x Memory OC/XMP Profile

[LadderOfChaos]

So i have Ryzen 7 2700x cpu with AsRock b450m Pro4 MB and Kingston HyperX 3200 mHz Ram. 
I have 0 knowledge on how to setup this xmp profile so i am looking fo a simple solution to set it up on 3200 mHz if possible

[nick name]

Shouldn't be hard.  Go into BIOS and look for XMP/DOCP and select a profile.  Save and exit.  

[LadderOfChaos]

1 minute ago, nick name said:

Shouldn't be hard.  Go into BIOS and look for XMP/DOCP and select a profile.  Save and exit.  

Hm i selected a 3200 mhz one and when i reboot it doesnt start

[nick name]

Which RAM slots did you use?  It should be A2 and B2 for a two stick kit.  

[LadderOfChaos]

I am using the correct ones, i checked the MB manual but still rip on 3200

[rares495]

Do not use DOCP then. It's similar to XMP. (it almost never works)

 

Set the frequency to 3200mhz, set the DRAM voltage to 1,35V and leave everything else on auto.

[LadderOfChaos]

3 minutes ago, nick name said:

Which RAM slots did you use?  It should be A2 and B2 for a two stick kit.  

I am using the correct ones, i checked the MB manual but still rip on 3200

[LadderOfChaos]

1 minute ago, rares495 said:

Do not use DOCP then. It's similar to XMP. (it almost never works)

 

Set the frequency to 3200mhz, set the DRAM voltage to 1,35V and leave everything else on auto.

i think i tried that but i will do it 1 more time just in case 

[LadderOfChaos]

21 minutes ago, rares495 said:

Do not use DOCP then. It's similar to XMP. (it almost never works)

 

Set the frequency to 3200mhz, set the DRAM voltage to 1,35V and leave everything else on auto.

I guess i didnt tried 1.35V. It did work  Thanks a lot mate, you have a beer from me if you ever visit Sofia, Bulgaria

[rares495]

Just now, LadderOfChaos said:

I guess i didnt tried 1.35V. It did work  Thanks a lot mate, you have a beer from me if you ever visit Sofia, Bulgaria

Glad I could help. Hope it's stable during daily use.

[nick name]

35 minutes ago, rares495 said:

Do not use DOCP then. It's similar to XMP. (it almost never works)

 

Set the frequency to 3200mhz, set the DRAM voltage to 1,35V and leave everything else on auto.

Waaaaait.  Doing this can be bad.  If you leave everything on Auto then the board is gonna set everything to whatever it wants and that might be worse than running 2133MHz.  So if you're doing this then check what the motherboard is setting everything to so you don't end up with absurdly high timings.  To do this you can use Ryzen Timing Checker in Windows.  

 

https://www.techpowerup.com/download/ryzen-timing-checker/

[rares495]

Just now, nick name said:

Waaaaait.  Doing this can be bad.  If you leave everything on Auto then the board is gonna set everything to whatever it wants and that might be worse than running 2133MHz.  So if you're doing this then check what the motherboard is setting everything to so you don't end up with absurdly high timings.  To do this you can use Ryzen Timing Checker in Windows.  

 

https://www.techpowerup.com/download/ryzen-timing-checker/

The modules probably run stock at something ridiculous like 2133 CL21. Can't be much worse than that.

[nick name]

14 minutes ago, rares495 said:

The modules probably run stock at something ridiculous like 2133 CL21. Can't be much worse than that.

That's not the JEDEC standard at 2133MHz.  It's likely 15-15-15, but can also be 14-14-14 or 16-16-16.

[rares495]

4 minutes ago, nick name said:

That's not the JEDEC standard at 2133MHz.  It's likely 15-15-15, but can also be 14-14-14 or 16-16-16.

That does not matter. There are many different types of memory modules and motherboards will never run them at JEDEC timings.

 

[nick name]

1 minute ago, rares495 said:

That does not matter. There are many different types of memory modules.

 

You're not showing me anything at 2133MHz.  

[rares495]

2 minutes ago, nick name said:

You're not showing me anything at 2133MHz.  

That's because my memory does not run lower than 2666.

[nick name]

1 minute ago, rares495 said:

That's because my memory does not run lower than 2666.

And what does that have to do with the JEDEC standard for 2133MHz?

 

You're not proving your point here.  

[rares495]

1 minute ago, nick name said:

And what does that have to do with the JEDEC standard for 2133MHz?

 

You're not proving your point here.  

Nothing. Just like the JEDEC standard has nothing to do with his RAM situation. You're just posting to argue.

[nick name]

3 minutes ago, rares495 said:

Nothing. Just like the JEDEC standard has nothing to do with his RAM situation. You're just posting to argue.

It is absolutely relevant to the concerns I stated above. 

 

It appears to me that you're arguing because I shared concerns with your approach to solving OP's problem.  

 

I'm posting to correct your statements that are incorrect.

[rares495]

Just now, nick name said:

It is absolutely relevant to the concerns I stated above. 

 

It appears to me that you're arguing because I shared concerns with your approach to solving OP's problem.  

Your concerns aren't valid at all. Not everyone needs to have the tightest timings possible. His board is bad, so is his memory and he was happy to just reach his desired frequency. So there's no need to go manual here. There will not be any perceivable benefit to the marginally better timings we could get on his modules. Do you get it or do you still want to go full OC on the guy? Leave it alone, man. The problem is solved.

[nick name]

6 minutes ago, rares495 said:

Your concerns aren't valid at all. Not everyone needs to have the tightest timings possible. His board is bad, so is his memory and he was happy to just reach his desired frequency. So there's no need to go manual here. There will not be any perceivable benefit to the marginally better timings we could get on his modules. Do you get it or do you still want to go full OC on the guy? Leave it alone, man. The problem is solved.

If you don't think timings would matter to him then why would speed matter?  Of course I nor you know what matters to him, but I think my assumption is valid.  And you went "manual" when you gave the instruction to "manually" set the speed and "manually" set the DRAM voltage.  And a bad motherboard setting Auto timings could produce perceivable changes in performance.    

 

And I saw the edit you made to your earlier post stating: 

Quote

motherboards will never run them at JEDEC timings

What do you think motherboards do when you don't apply XMP/DOCP?

 

I'm trying to offer him a better solution.  

[Tristerin]

@nick name is a very informed person with Ryzen and DDR4.  While your solution is one of many available, it doesn't mean its the best solution @rares495.  Just because I can take a Windows 10 HDD from an intel system and slap that HDD into a completely new AMD build and it will "work" doesn't mean its working optimally or as intended.  While I agree with your approach - set manual frequency and voltage, let the system figure out what timings it needs to post (so we can even figure out if the memory controller on his CPU which IS NOT MEANT for 3200mhz can handle it) - it shouldn't end there as you are leaving performance on the table...and I cant disagree with @nick name at all in trying to get this user the most out of what he paid for.

 

 

[WkdPaul]

* thread cleaned *

 

If the OP needs further help with memory timings, let him reply. Until then, there's no need to argue.

[LadderOfChaos]

Can someone explain how this timing affect the performance and what they actually do?

[Guest]

18 minutes ago, LadderOfChaos said:

Can someone explain how this timing affect the performance and what they actually do?

In short

Timings are just about exactly what they do in the definition of the word it'self, Timing.

So with 14ms is faster than 16ms and so forth. 

When you decrease the timing sets, it decreases latency or the time needed for reads, writes, and copies. 

 

Processor frequency plays a role also. You can increase read and write, copy times just by overclocking the processor for example. The latency will also decrease.

This is because the processor gets it's information directly from the Random access memory, both have effect on each other.