Adventures in 1700 Overclocking. Somewhat success
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=5507
Printed Date: 23 Dec 2024 at 10:32pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Adventures in 1700 Overclocking. Somewhat success
Posted By: CocoaThumper
Subject: Adventures in 1700 Overclocking. Somewhat success
Date Posted: 04 Jul 2017 at 1:37pm
|
Preface: I'm writing this in a way that new overclockers can understand. Which would have helped me last week as I'm still learning this myself. My CPU is a Ryzen 1700 with an AsRock x370 Killer SLI/ac motherboard. I personally define a successful overclock as one that is stable through numerous benchmarks, and allows for auto downclocking and downvolting when the CPU is not in use Note the following before reading on: Pstates - Think of them as power states that allow for more customizable overclocks. If I used the simpler "OC Tweaker" menu in my BIOS, and made a simple two-click change of my CPU frequency and voltage...Ill end up with a Ryzen CPU that ran my overclock at its highest frequency all the time. Pstates allow for control of downclock on your CPU, thus increasing energy savings and CPU life span. You will see several Pstates in your advanced settings. FID - Frequency value in each of your Pstate settings (uses hex values) DID - Divider value in each of your Pstate settings (uses hex values) VID - Voltage value in each of your Pstate settings (uses hex values) For a little help with these hex values, check out the description of the Ryzen overclocking guide that Youtuber Tech City did a few months ago. The video can be helpful too...although its fairly dated now given the numerous BIOS updates we've had since. https://www.youtube.com/watch%3cv=52Tw-wcT7o4" rel="nofollow - https://www.youtube.com/watch?v=52Tw-wcT7o4 ------------------------------------------------------ Here are my findings: 3.7ghz @ ~1.3v was a success I get a 3.7ghz stable and stress tested overclock with proper downclocking to 2.7ghz and 1.5ghz by doing the following: -when going into Pstates, I change Pstate P0 to Custom, and ONLY change the FID value in order to up my frequency to 3700mhz. If I touch the DID or VID values at all, I end up with Windows getting stuck at 1.5ghz downclock, and a max 2.7ghz boost. Since I don't change DID or VID, the voltage in P0 gives me 1.1875 volts. In order to get the voltage I need, I go to OC tweaker and set the Vcore offset to +130mV (BIOS HW Monitor will now see total CPU Vcore around 1.3v) -ALL OTHER Pstates are left at AUTO. Changing the other Pstates (usually P1 and P2) never got my overclock to be recognized properly, with correct downclocking. I would either get stuck at 1.5ghz, stuck at 3.7 ghz, or get 1.5ghz downclock with a 2.7ghz boost. So for now its best to only edit Pstate P0 and leave the rest on Auto I can run Cinebench multiple times with no issues and temps in the 40s or 50s. I max out at 60 degrees Celsius in AIDA64 stress test, about 70 or slightly less in prime95, and about the same in Intel Burn Test. ---------------------------------------------------- 3.8ghz and up was a failure I am unable to test 3.8ghz or higher overclocks due to what I believe is currently a BIOS limitation as I don't get close to a chance of getting proper voltage or even stressing high temps. -If I try the same method as above, but simply change my FID in Pstate P0 to 3800mhz, my system crashes during my second Cinebench test. At 45 Celsius, temps aren't the issue and clearly I need more voltage, as HWiNFO monitor shows me getting the same 1.3v or less of juice, which I set for my 3.7ghz overclock. And here's where things start to suck. -If I instead set my Vcore offset in BIOS to +200mV, in order to give myself the extra needed voltage for my 3.8ghz overclock....the system will not load Windows. It will POST, show the AsRock logo, and then the monitor goes off, my CPU fan ramps up, and Windows never loads. -I can get back into BIOS if I reset, and check to see that my Vcore has indeed increased to 1.35 or so thanks to the increased offset. But I cannot load Windows. VERY STRANGE, considering I could load Windows just fine with the lower offset, and thus lower voltage. -So I figured, let me try setting the Vcore offset back to Auto, and instead trying to set the voltage in my P0 pstate. Once I changed the VID to allow for me to have 1.35v or 1.36volts, I can load Windows. Remember, I am still leaving my other Pstates at Auto. Windows and Cinebench list a 3.8ghz CPU in my specs, however, Ryzen Master, HWiNFO, and other monitoring programs read my Max CPU frequency as 2.7ghz. When I run benches, this is exactly what I max out at. And thus all my scores go down compared to my earlier successful 3.7ghz overclock. -Finally I decided to set my Pstates manually. Changing the FID(frequency), DID(divider), and VID(voltage) values for Pstates P0, P1, and P2. I set P0 to 3.8ghz with 1.35v, P1 to 2.7 with 1.2v, and P2 to 1.5ghz with 0.875v. And guess what? YET AGAIN, my PC gets either stuck at 1.5ghz, or only boosts to 2.7ghz. Make what you will of my findings and please chime in. |
Replies:
Posted By: wardog
Date Posted: 04 Jul 2017 at 1:42pm
|
Upped and Thanks given. Great post. |
Posted By: CocoaThumper
Date Posted: 04 Jul 2017 at 1:45pm
|
I love how much Ive learned, and have gotten good guidance from this forum, YouTube, and elsewhere. I'm thinking I simply have a BIOS limitation at the moment...rather than a chip that cant overclock higher. But I'm hopeful for whatever AsRock has in store for us soon in terms of BIOS Updates |
Posted By: wardog
Date Posted: 04 Jul 2017 at 2:13pm
|
" rel="nofollow - P-state OC'ing isn't easy and has its particular limitations. What can it do GHz wise when OC'd on a fixed voltage? Thanks for the nice words. The Users here are knowledgeable, you included. |
Posted By: Xaltar
Date Posted: 04 Jul 2017 at 2:32pm
|
The UEFI definitely plays a role, I could get 4.05 stable on my 1600x with 2.3 on my Taichi but 2.4 will only just net me 4.0. At the moment I think UEFI updates are more tailored toward RAM frequency, once that is more or less sorted we should see other things take focus and improve. Obviously different CPUs will still behave differently, the silicon lottery still plays a role but I do think we will be able to squeeze more out of our CPUs down the line. ------------- 
|
Posted By: wavetactic
Date Posted: 05 Jul 2017 at 4:10am
|
" rel="nofollow - This post was extremely informative. So I assume I am not the only one who isnt able to stress test their overclocks due to not posting? I thought it was extremely weird coming from a haswell, where I would set the voltage and clock and stress test it. I thought there was something wrong with my motherboard. It's weird because sometimes it allows me to get into the OS with a 3.8 or 3.9 overclock and passing all the stress test, but if I restart my computer or restart, it just won't post again. Just feels off. if anyone has had a different experience please let me know!
|
Posted By: jj22ee
Date Posted: 06 Jul 2017 at 11:54pm
| I have the same problem. If I change the voltage in pstate0 to anything besides stock. It defaults to pstate1 freq. So I am limited in my overclocking to stock voltage and 3.7 ghz. If I overclock the non pstate method it works. But it will not throttle down. 3.7 is plenty fast right now. Overall I am loving ryzen and my asrock board. Just ready for some of these bugs to be worked out. |
Posted By: nangu
Date Posted: 07 Jul 2017 at 2:38am
|
@CocoaThumper: Thank you, very informative post. I managed to pstate0 overclock my R7 1700 to 3.8 Ghz this way. It only needed one "click" to the CPU offset voltage to reach it, really easy to do. I have to do more testing, and I hope these bugs will be ironed out so we can set P1 and P2 with custom voltages too.
|
Posted By: CocoaThumper
Date Posted: 07 Jul 2017 at 8:59am
" rel="nofollow - [URL=][/URL]
Hopefully we get a new BIOS update soon. I'm enjoying Ryzen and my Asrock board despite the kinks.
Which voltage value did you set for your offset? Unfortunately for me I can only offset voltage for a 3.7ghz overclock. If I use an offset higher than +130mV, I cant load Windows, even though the motherboard Posts. Hopefully sometime soon we get a new BIOS so I can use the higher offsets properly so I can go higher than 3.7ghz |
jj22ee wrote:Posted By: parsec
Date Posted: 07 Jul 2017 at 10:43am
I know you are using PStates, but in the OC Tweaker screen, is the CPU Frequency and Voltage Change option still set to Auto? If you set it to Manual, you can then enter a VCore value, which will be reflected in PState 0. I use Offset voltage greater than +130mv (+300mv), and Windows starts fine. That you cannot does not make sense, not sure what is happening. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: CocoaThumper
Date Posted: 07 Jul 2017 at 9:46pm
I still have my OC Tweaker CPU values set to AUTO. If I set it to manual, then both Pstates P0 and P1 will change to whatever is in OC tweaker. And then I lose my 2.7ghz middle downclock. Right now I have OC Tweaker on Auto, and set my overclock using P0 manually, with P1 and P2 on Auto. This lets me downclock properly to P1 @ 2.7ghz and P2 @ 1.55Ghz My goal is not just simply getting a higher overclock. I can get to 3.8ghz by using OC tweaker, or further messing around in the Pstates. However, my overclock ends up running 24/7 and never downclocks. Plus there's the fact that my system will not load Windows if I use a VCore offset higher than +130mV The problems I highlighted in this post and in my OP are something Asrock need to address so we can all properly use several manual Pstates, proper voltages, and have custom downclocks work. PS - Based on a couple responses in this thread, and from talking to folks on reddit, these problems are pretty common. |
Posted By: nangu
Date Posted: 08 Jul 2017 at 12:23am
|
I 've set the offset vcore in the main OC page only by pressing the "+" key one time. I'm not on my PC at this moment, at night I'm be able to post the exact value added. On Windows, the max vcore shown by HWInfo is 1.16v at 3.7Ghz max load (1.18mv low load at same speed), but I'll check it later again and post the exact values. |
Posted By: ShampooCA
Date Posted: 18 Jul 2017 at 4:56am
|
Watching this thread....haven't attempted offset overclocking yet. I don't see a problem with leaving the computer at a fixed voltage & clockspeed, but ideally it'd be nice to setup the offsets to conserve power, temperatures etc. Less is more. :) Loving this platform, because we're all getting to tinker a bit, compared to set it and forget it Intel platforms of the past decade or so. #fun
|
Posted By: Drain_Bamaged
Date Posted: 18 Jul 2017 at 4:14pm
I've seen this too. Perfectly stable overclock boot loops till finally loading windows at default ingoring my preset. Usually it boots fine though. Makes me want a better board with Post indicator LED. I have successfully overclocked my 1600 with my x370 Killer SLI 3.7ghz at stock voltage, 3.8 with 1.25 and 3.9ghz with 1.37v. I've done it fixed ( causes 1500mhz bug), offset, and I've used Pstate 0. Everything can be perfectly fine but if I reset...all bets are off as to if it boots with what I set. I believe it's memory related. I'm using Corsair LPX 3000mhz @ 2933.
|
Posted By: ket
Date Posted: 18 Jul 2017 at 10:08pm
|
I don't get any downclocking issues when OCing with OC Tweaker so haven't tried pstates yet, thats with a Fatal1ty Gaming K4 Asrock sent me. I wouldn't necessarily hold out hope that newer AGESA code will improve overclocks all that much as the biggest limitation is the lithography used with Zen. Long story short, the lithography has 2 "critical" points (when things start to stop scaling linearly) The first critical point is right at 3.8GHz, the second at 4GHz. Newer CPU revisions might extend these critical points as new CPU revisions / steppings often use tweaked lithography techniques but don't be surprised if you have to wait until Zen 2 / 3 before overclocks of 4.5GHz or more become common place. One area you can hold some hope for though is regards SMT. With some testing I did the 1700 I have would run and be semi-stable @ 4GHz with only 1.3v but that was with SMT off. With SMT on 1.42v+ was need for 4GHz to be about as stable as it was with SMT off. Heres a copy / paste of part of the results I noted down post K4 review when I had more time for some testing; 3.7GHz - Stable @ 1.25v SMT on (might of been stable on lower voltage I was aiming for maximum frequency without crazy voltage) 3.82GHz - Stable @ 1.32v SMT on (you'll notice the non-linear voltage bump for 3.8GHz as "critical 1" is hit) 3.9GHz - Stable @ 1.38v SMT on (done post review of the K4) 4.016GHz - Semi-stable @ 1.45v+ SMT on Needless to say, the 14nm lithography really doesn't scale well once you hit 3.8GHz+ and even then it's debatable if the voltage increase is worth it for a extra 50-100MHz but even at that speed by comparison the Zen 1700 stomped all over the old i5 3570k @ 4.5GHz with 2133MHz RAM test system in every scenario, gaming included. At the end of all this testing one stark thing that can be taken away is that while Zen may not have huge scope for overclocking ("huge" being relative of course, in my case the 1700 when left to its own devices will boost to 3.2GHz, where a manual OC can take that all the way up to 3.9GHz.. so a 700MHz OC certainly isn't what I would call bad by any means) memory speed for 1080p gaming at least can have a large impact on performance. I gained more FPS with memory speed increases than I did overclocking the CPU itself. You can take a gander at the review I did for more details http://www.xtremesystems.org/forums/showthread.php%3c294233-Asrock-X370-Fatal1ty-Gaming-K4-Review" rel="nofollow - HERE |
Posted By: ShampooCA
Date Posted: 18 Jul 2017 at 11:25pm
|
I've experienced similar resistance once getting to those clockspeeds above. My wall was 3.85GHz, which is great @1.3375v which ended up actually being 1.34v with LLC@3. Anything above that and I have to start pumping the voltage up beyond 1.4v, and even then it's not really stable. Would've been nice to hit that 4.0GHz magic number, but whatever, it's not a huge performance loss, just sucks to see 3.83xx-3.84xxGHz in CPUz and any other program that displays CPU clockspeeds. :(
|