SOME RYZEN 7 1700 OVERCLOCKING!

haszek · 3 Jul 2017 at 19:55

Yeah but what chips they have matters...you can confirm in thaiphoon, aida 64, version on the memory sticker.

You are being over optimistic with your settings anyway. You have to consider that all the record memory speeds are only for 2x8gb. For 32gb with good chips, cpu motherboard it is more difficult to have stable anything above 3200

chroniclard · 3 Jul 2017 at 19:57

Been told its samsung b die. Also it's only 2x 8, half the memory kit. Member I got it from did have it running at 3200 but that was a different board.

haszek · 3 Jul 2017 at 19:59

Ah ok

I thought you have two sticks 16gb each.

LtMatt · 3 Jul 2017 at 20:00

chroniclard said:
Been told its samsung b die. Also it's only 2x 8, half the memory kit. Member I got it from did have it running at 3200 but that was a different board.

Try 60ohms, that works well for my b die.

Start with 3200Mhz and aim for CL14-14-14-43-1 Geardown and all Bankswap disabled. If you get that stable, work on a CPU overclock and take it from there.

BRIGGBOY81 · 3 Jul 2017 at 20:34

ok seems 3.925 is the limit of my 1700, no matter how many volts i throw at her she wont run occt for than a couple of minutes. 3.925 @ 1.4v is where i'm staying for now but i have a sneaky feeling that for everday use i could squeeze 4.0 out of it and it still be stable. want to do some gaming now so leaving it there.

chroniclard · 3 Jul 2017 at 21:44

Hmm, I cant find Bank GRoup Swap, there is one something like interleaving with Auto, Channel, Die, Socket.....

Ste · 3 Jul 2017 at 22:09

AMDMatt said:
Try 60ohms, that works well for my b die.

Start with 3200Mhz and aim for CL14-14-14-43-1 Geardown and all Bankswap disabled. If you get that stable, work on a CPU overclock and take it from there.

Hi Matt

I am 1000% ish stable on HCI at 3333c14-14-14-36, 1.45v DRAM and 1.1875v SOC. However this is with geardown at auto and 2T

Do you think those two points are important enough to drop to 3200? Or should I drop the 36 to 43 first?

Going to leave the memory for now and focus on the core but be good to know where to go next on the RAM.

Edit - or maybe procODT 60 is worth a retest first...

Thanks mate

SupraWez · 3 Jul 2017 at 22:33

AMDMatt said:
Try 60ohms, that works well for my b die.

Start with 3200Mhz and aim for CL14-14-14-43-1 Geardown and all Bankswap disabled. If you get that stable, work on a CPU overclock and take it from there.

Agreed, I also had to switch to 60ohms, 53ohms or auto was not stable, with GD and BS disabled too, in case others havent seen it here are some timings recommended by The Stilt on OC.NET :-

3200MHz LL = 12-12-12-28-54-140ns-9-8-12-2-2-GDME-1T
3466MHz LL = 14-14-14-28-54-192ns-14-8-12-2-2-GDMD-1T

tCL-tRCDR/W-tRP-tRAS-tRC-tRFC-tCWL-tRTP-tWR-tWRWRSCL-tRDRDSCL

140ns = 224 tRFC
192ns = 333 tRFC

I started with 3466 settings, got that stable then increased my FSB a little to get 3500 with same settings and a little more volts on the dram

LtMatt · 4 Jul 2017 at 07:32

Ste said:
Hi Matt

I am 1000% ish stable on HCI at 3333c14-14-14-36, 1.45v DRAM and 1.1875v SOC. However this is with geardown at auto and 2T

Do you think those two points are important enough to drop to 3200? Or should I drop the 36 to 43 first?

Going to leave the memory for now and focus on the core but be good to know where to go next on the RAM.

Edit - or maybe procODT 60 is worth a retest first...

Thanks mate

You'll need to test both, but I'd have though faster memory would be better. If you using a high CPU frequency then you may need to lower memory speed. CPU frequency still trumps memory, as long as the memory is nicely tuned.

Ste · 4 Jul 2017 at 07:34

AMDMatt said:
You'll need to test both, but I'd have though faster memory would be better. If you using a high CPU frequency then you may need to lower memory speed. CPU frequency still trumps memory, as long as the memory is nicely tuned.

Thanks Matt. I have 3.9 and 4.0 stable in realbench 1 hour and 2 hours p95 but not tuned with OCCT AVX which is my next step. Suspect 4.0 will be off the table and hope to get a stable 3.9.

Does 1T make much difference?

LtMatt · 4 Jul 2017 at 07:38

Ste said:
Thanks Matt. I have 3.9 and 4.0 stable in realbench 1 hour and 2 hours p95 but not tuned with OCCT AVX which is my next step. Suspect 4.0 will be off the table and hope to get a stable 3.9.

Does 1T make much difference?

I don't think so, just lowers latency a little bit.

chroniclard · 4 Jul 2017 at 09:39

Given up again, dont know what I am doing.

2933 for now.

BRIGGBOY81 · 4 Jul 2017 at 13:26

Ste said:
Thanks Matt. I have 3.9 and 4.0 stable in realbench 1 hour and 2 hours p95 but not tuned with OCCT AVX which is my next step. Suspect 4.0 will be off the table and hope to get a stable 3.9.

Does 1T make much difference?

Same here Ste, 4.0 would run everything else ok but occt with avx. Even going up to 1.55 didn't get anything over 3.925 stable in occt

BRIGGBOY81 · 4 Jul 2017 at 15:14

Looks like ive got 3.95 stable @ 1.425. seems it might of been vcore soc that was holding me back, as I've upped it from 1.1 to 1.15

Ste · 4 Jul 2017 at 21:08

Nice. When you set that in the BIOS what does it drop to under heavy load?

BRIGGBOY81 · 4 Jul 2017 at 21:53

That was in occt with avx, so gonna try and get the core voltage down with realbench and then I'm done.

What drops to what under heavy load?

gavinh87 · 4 Jul 2017 at 22:22

AMDMatt said:
You'll need to test both, but I'd have though faster memory would be better. If you using a high CPU frequency then you may need to lower memory speed. CPU frequency still trumps memory, as long as the memory is nicely tuned.

From what it looks like from our discord group testing (lol) CPU bound scenarios prefer raw speed. GPU bound scenarios prefer latency. These are at above 3200, until then speed wins.

SwatKat · 5 Jul 2017 at 21:04

I have a 1600 and CH6 on 1403
I upped the RAM to 3200 and running at 3.85ghz at 0.13125 offset, 1.8 pll and 1.1 SOC.
Tested the RAM with HCI for 500%
The started testing OCCT AVX and it started stuttering, getting pauses of 10 second or so but AVX for 2 hours was stable.

Ended clearing the BIOS and going back to defaults and still had the issue.

Found i had google photo backup running in the background, found if i kill that off and run OCCT the stuttering is gone.
I have 2 SSDs connected to port 0,1 and a 2TB disk i assume in port 2. OS on the SSD, not much else other than photos on HDD.

Google Photos was hitting the HDD for 80% usage even when paused, so for those with stuttering it could be related to high disk access while running bench tests. Could make sense if the CPU deals with this now. If i killed off google backup and searched through the disk it was fine with no stuttering so the low usage caused no issues.

gavinh87 · 5 Jul 2017 at 21:19

SwatKat said:
I have a 1600 and CH6 on 1403
I upped the RAM to 3200 and running at 3.85ghz at 0.13125 offset, 1.8 pll and 1.1 SOC.
Tested the RAM with HCI for 500%
The started testing OCCT AVX and it started stuttering, getting pauses of 10 second or so but AVX for 2 hours was stable.

Ended clearing the BIOS and going back to defaults and still had the issue.

Found i had google photo backup running in the background, found if i kill that off and run OCCT the stuttering is gone.
I have 2 SSDs connected to port 0,1 and a 2TB disk i assume in port 2. OS on the SSD, not much else other than photos on HDD.

Google Photos was hitting the HDD for 80% usage even when paused, so for those with stuttering it could be related to high disk access while running bench tests. Could make sense if the CPU deals with this now. If i killed off google backup and searched through the disk it was fine with no stuttering so the low usage caused no issues.

A lot of stuttering seems to be disk related. I would suggest anyone having issues should look at the drives first.

Journey · 5 Jul 2017 at 23:18

chroniclard said:
Given up again, dont know what I am doing.

2933 for now.

I must say, using the ASRock boards is much easier for over clocking the RAM, give it another go once you've read up a bit more.