OC:ing my RAM + Weird issues when OCing CPU

Laith · 02 Nov 2017

Hi SevenForums, long time no see. :)

So I got around to building my new PC in Monday which is serving me really well. There is two issues though.

The first issue, the major issue is that I can't OC my RAM even the slightest without it refusing to boot even when I have RAM specifically made for overclocking, granted I haven't touched the timings because I'm too afraid too but bumping it to 2666MHz shouldn't be an issue whatsoever. I still don't know if this is a BIOS-related issue or if it's just because I haven't touched the timings.

The second problem is one that is really weird. When I try to OC my CPU from stock to something like 3.7GHz it works just fine, normal temperatures, nothing weird. But when I hop into any game for example CS:GO, I average 100FPS, which is NOT normal. On stock I average ~350 so it really doesn't make sense why I get MUCH less performance when I do an action that's really beneficial for performance.

Specs:
AMD Ryzen 5 1600
G.Skill Flare X 16GB (2x8GB) DDR4-2400
ASUS PRIME B350-PLUS
ASUS GTX 1060 3GB
Corsair VS550
Corsair Crystal 460X RGB

Thank you sincerely for your help.
Laith

EDIT: The smallest OC I can do on the CPU is 0.025GHz, which gives me the same results as I described.

gldndragn · 02 Nov 2017

Hello Laith,

I Think I can Help you out some with these issues as i have had to deal this the same problems on my build using the same mobo.

As ffor the first problem with your RAM, I have had more success on this board bby manually setting the CLK timing to stock for your RAM. To do this you will need to enter BIOS, go to Advanced Menu (F7), go to the AI Tweaker tab, and select DRAM Timing control.
Once there you will need to set the CLK times to the factory values usually listed as 4 numbbers on the RAM packaging. the first number is what you will set the CAS Latency to. Set BOTH the Trcdrd & Trcdwr to the second number. Set your RAS Pre time to the third and the RAS ACT time to the last.

EXAMPLE!
If your CLK times are 16-16-16-39, you will set them as follows:
CAS Latency = 16
Trcdrd = 16
Trcdwr = 16
RAS Pre = 16
RAS ACT = 39
Leave ALL other options at AUTO.

After you have done this, try incramentally increasing your RAM clock incramentally until you find the optimum performance.

gldndragn · 02 Nov 2017

For the second issue of your FPS dropping while OC'd, that is the result of thermal throttle on the VRM. this board has a weak VRM design as well as insufficient cooling on the VRM. I have seen the best results from relying more on the LLC (load Line Calibration) to handle the additional power to the CPU rather than a straight Overvolt of the Vcore. My advise would be to by setting your VDDCR CPU offset Voltage to +0.1625, then under the DIGI+ VRM section, Set your VDDCR CPU Load Line Calibration to HIGH. this will allow your VRM to adjust the Overvolt on the CPU as needed for the specific load placed on it.

After setting voltages, test the system and continue to incramentally lower the VDDCR CPU offset Voltage until you find the lowest point that you are stable. DO NOT TEST WITH AIDA64 as it does not play nice with ASUS motherboards.

Finally, if all else fails, place a fan blowing DIRECTLY on the VRM heatsink. That is what I had to do until I can afford to replace the board.

Specs:
AMD Ryzen 7 1700 (OC'd @ 3.9Ghz)
Asus Prime B350 Plus
G.Skill Trident Z RGB 2x8Gb 3200 (Clocked @ 2800)
Asus Strix RX 470 8gb Gaming
Corsair H100i
Rosewill Photon 650
Corsair Air 540

Laith · 03 Nov 2017

Hey, thank you so much for your response! Turns out this board isn't worth the money, unfortunately. :/

As for the RAM, the timings were already correct, 15-15-15-39, maybe that's because I had D.O.C.P enabled? I'll try to disable it and try with it afterwards.

As for the CPU, I changed the offset to +0.1625 and I'm running 3.8GHz right now, I'll test further to see the minimum voltage that's stable with my OC.

Anyways, thank you so much for your response! :)

Laith · 03 Nov 2017

Update: I'm hitting 80FPS in CS:GO with 0.1625, 3.8GHz and CPU LLC on high. I'm gonna try to lower the OC. :/

Update 2: The RAM OC:ing works with the manual values and D.O.C.P disabled!

Going to experiment further with the CPU.

Update 3: I can only go to 2666MHz on the RAM, anything higher will refuse to boot. As for the CPU, even with the slightest overclock and just a bit of a bump on the voltage yields the same result as in the original post. 80FPS or so in CS:GO(which has been my goto "benchmark" tool for all of this)

gldndragn · 03 Nov 2017

I believe the board is running into thermal throttling. I would still put a small (80 mm) fan above the VRM heatsink. This will probably help alot. Also, what version bios do you have on the board? Try the latest version, if you haven't already.

PS, The two posts "I" made, were actually my roommate who has the same board as you, and these were the things he did to correct these issues. You are correct that this board is not worth the money at all. LOL

Laith · 03 Nov 2017

To be honest, I don't know how I would put a fan over it without it looking really crappy. Also I'm running the latest.

gldndragn · 03 Nov 2017

I know the fan will be unsightly, but.....operational and ugly or pretty and flaky. I would take ugly and working the way I want it to. Just my personal thoughts. It is after all, your rig. :)

Laith · 03 Nov 2017

The thing is, I wouldn't really mind it THAT much, but there are no mounting holes for the fan so that's another issue.

gldndragn · 03 Nov 2017

Hello again (roommate speaking),
I'm glad I could help somewhat. Sorry I couldn't be more helpful with your issues. I completely agree that this board is not worth the money. I do have a 90mm fan hanging over the VRM on mine right now. It is ugly but it keeps everything working until I can afford a new board. I'm looking at the MSI X370 Gaming Pro Carbon. Personally I would avoid ASUS as they have had nothing but problems across their entire AM4 lineup.
I will keep monitoring this post so if there is any more assistance I can provide, please don't hesitate to ask.