• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Ryzen Owners Zen Garden

3200MHz & stays there, on both modules. I have 1700 (non-X), in a box, with it's HSF lying on a shelf, gathering dust, but it would be quite a pain in a butt to disassemble LCS, just to replace 1700X with it. Flare X, Samsung b-Die, single rank, mobo has XMP option, set it, got me 3200MHz, CL14, 1.35v, works to this day. :)
 
3200MHz & stays there, on both modules. I have 1700 (non-X), in a box, with it's HSF lying on a shelf, gathering dust, but it would be quite a pain in a butt to disassemble LCS, just to replace 1700X with it. Flare X, Samsung b-Die, single rank, mobo has XMP option, set it, got me 3200MHz, CL14, 1.35v, works to this day. :)

Then i have no idea how an overclocked chip @ 400 MHz higher then stock can perform worse than stock.

Only thing i can think of is it's throttling heavily but, since it passes the torture stability tests, that's not it.
 
Probably throttling. I've yet to figure out the options in "Pstates/Throttling" section of AMD CBS that i got with F22 UEFI update for my mobo (GA-AX370 Gaming K7), but i bet the answer is there. Can't put my finger on it for now, though. I hope 2700X, no - i believe 2700X will put both of my 1700X scores i have (with F4 & F22) right now to shame, 4.3GHz/1.4v vCore with 2000+ cb - that's my goal. If I can squeeze out 4.4GHz stable (doubt it, but one can hope :)) with my LCS + that EK monoblock - pure f*ckin' awesomeness.

P.S. Running Blender Video Editor, it converts MP4 file of my Carmageddon: Max Damage gameplay footage to .blend file, while still keeping my altered MPEG-4 file intact + typing this text here, CPU usage (as reported by HWinfo64) is - 17.x% max, temps - 50-ish.
 
Probably throttling. I've yet to figure out the options in "Pstates/Throttling" section of AMD CBS that i got with F22 UEFI update for my mobo (GA-AX370 Gaming K7), but i bet the answer is there. Can't put my finger on it for now, though. I hope 2700X, no - i believe 2700X will put both of my 1700X scores i have (with F4 & F22) right now to shame, 4.3GHz/1.4v vCore with 2000+ cb - that's my goal. If I can squeeze out 4.4GHz stable (doubt it, but one can hope :)) with my LCS + that EK monoblock - pure f*ckin' awesomeness.

P.S. Running Blender Video Editor, it converts MP4 file of my Carmageddon: Max Damage gameplay footage to .blend file, while still keeping my altered MPEG-4 file intact + typing this text here, CPU usage (as reported by HWinfo64) is - 17.x% max, temps - 50-ish.

Try lowering to 3.6 GHz and reduce the volts a tad bit: if it's throttling, then the scores should return to be higher then @ stock (multi-thread).

Also: you should double check your monoblock to make sure there's nothing wrong with it. Different brand, but you never know.
 
The scores @ 3.8 & 3.9GHz were stable @ R15, but failed Prime95 Small FFTs test miserably. That was under F4 version of BIOS, Small FFTs test couldn't even reach half-an-hour mark. VCore was @ 1.4v though, SoC - 1.1/1.2v. :eek: lol Maybe i'll raise vCore to 1.4v again, SoC - will leave it @ 0.987v for now. LLCs @ High right now. Will do it in 8 or 9 hours from now though, gotta sleep - i do NOT want to pass out from depriving myself from sleep in a middle of a test, now do i? :laugh: jk Cheers.
 
The scores @ 3.8 & 3.9GHz were stable @ R15, but failed Prime95 Small FFTs test miserably. That was under F4 version of BIOS, Small FFTs test couldn't even reach half-an-hour mark. VCore was @ 1.4v though, SoC - 1.1/1.2v. :eek: lol Maybe i'll raise vCore to 1.4v again, SoC - will leave it @ 0.987v for now. LLCs @ High right now. Will do it in 8 or 9 hours from now though, gotta sleep - i do NOT want to pass out from depriving myself from sleep in a middle of a test, now do i? :laugh: jk Cheers.

As mentioned in previous post, the suggestion was to dial down on the overclock to see it it was throttling before the dial down: if so, then a quick R15 multi would show improvements over stock.

Quite possibly, the new BIOS changed some key, "more obscure" settings from previous BIOS which means more voltage may fix it, but do try the other suggestion 1st.
 
VRMs could be throttling, run something like intel burn test on normal for 100 loops and see if the scores suddenly drop as the heat builds up
 
Good news: i got me 1635cb in R15, so 3.8GHz/1.4v vCore is working & i beleive fiddling even a bit more with it & SoC voltages will get me somewhere.
Bad news: i have internet on my phone & not on my rig (ISP done f*cked it up, technician comes this Friday morning) so i will only post a pic of the score this Friday. Cheers.

Small update: ran R15 again few mins ago just for a sake of it ,1639cb but it's still above my F4 EFI 3.4GHz score, 30cb lower than my 3.8GHz F4 score, but why would i give a half of a flying f*ck. lol Cheers again. :toast:
 
Last edited:
Good news: i got me 1635cb in R15, so 3.8GHz/1.4v vCore is working & i beleive fiddling even a bit more with it & SoC voltages will get me somewhere.
Bad news: i have internet on my phone & not on my rig (ISP done f*cked it up, technician comes this Friday morning) so i will only post a pic of the score this Friday. Cheers.

Small update: ran R15 again few mins ago just for a sake of it ,1639cb but it's still above my F4 EFI 3.4GHz score, 30cb lower than my 3.8GHz F4 score, but why would i give a half of a flying f*ck. lol Cheers again. :toast:

Stress test those settings: if it passes, great.

If it fails in any of them, lower your settings a tad bit and repeat the tests, until it succeeds: once it does, lower them just a tad bit more and you should have a rock solid system.

@ least, that's what i would do. Perhaps others more experienced do it in other ways? Dunno, really: i'm not very experienced with this myself.
 
nomnomnnom crunchy numbers

capture115.jpg
 
@HTC: with the 1.38v vCore it passed 2h of Small FFTs test (F22 BIOS/EFI), shouldn't be a prob, i'm the one to raise voltages what can i say, OC needs juice, even 400MHz one. With Ryzen your venture into OC land can go either way, you should know. lol Cheers.

@Mussels: i envy you, but not for long.
 
@HTC: with the 1.38v vCore it passed 2h of Small FFTs test (F22 BIOS/EFI), shouldn't be a prob, i'm the one to raise voltages what can i say, OC needs juice, even 400MHz one. With Ryzen your venture into OC land can go either way, you should know. lol Cheers.

@Mussels: i envy you, but not for long.

Small FFT is OK for testing but because of the way the new Ryzen is built it's not enough and doesn't test any RAM. I usually do custom with 75% of my RAM selected so out of 16 GB I set 13000 MB


nomnomnnom crunchy numbers

capture115.jpg

Right where it should be :toast:
 
  • Like
Reactions: HTC
i just love that its decimating the 12C intel in the list so thoroughly
 
i just love that its decimating the 12C intel in the list so thoroughly

If I'm not mistaken the X5650 is a 6c/12T lga 1366 so that would be two CPUs, wouldn't it? Does that equal three times better ha ha
 
@HTC: with the 1.38v vCore it passed 2h of Small FFTs test (F22 BIOS/EFI), shouldn't be a prob, i'm the one to raise voltages what can i say, OC needs juice, even 400MHz one. With Ryzen your venture into OC land can go either way, you should know. lol Cheers.

@Mussels: i envy you, but not for long.

You're the one using Windows: an unstable system is prone to have errors and BSODs, which could lead to data loss in worst case scenario.

I'm not OCing @ all, with the exception of RAM which is @ 3200 CL16 via XMP: everything else @ stock.
 
Yeah that certainly doesn't seem right to me. Here's a comparison with an 8700K, looked for my Ryzen but I haven't done that one I guess
https://www.3dmark.com/compare/spy/4569213/spy/3023757
Found one with a 1700X/RX580 for comparison still outscored your 2990WX by a good margin
https://www.3dmark.com/compare/spy/4569213/spy/3023757/spy/2997029

I'm going to kill it down to 16 cores no SMT and see if it helps. I haven't done research yet, but was hearing that time spy maxes at 18 cores so maybe it was being dumb with core selection.
 
You're the one using Windows: an unstable system is prone to have errors and BSODs, which could lead to data loss in worst case scenario.

I'm not OCing @ all, with the exception of RAM which is @ 3200 CL16 via XMP: everything else @ stock.

Works fine for me, i simply love the way things are with my rig. Actually running Prime95 Small FFTs test right now on my current settings (3.8GHz, 1.4v vCore, 0.987v SoC, etc....), only thing different is i also changed P0 P-State from Auto to Manual but haven't touched anything else there. 46 mins into the test right now, current temp is 65-ish. On all 8 cores/16 threads. 100% CPU usage. Oh & there's a surprise coming this Friday, i got myself some nice score in R15. So i guess nothing wrong right now with my rig & despite being bloatware, Win 10 behaves good on my rig (well actually on my M.2 NVMe SSD, but i digress ). As for making Win 10 behave nice - Google is your friend, so.... Yeah, the force is strong with that one. :laugh: jk Cheers.

@cdawall: 'ssup Carmageddoner. :laugh: I have news for you regarding Carmageddon: Max Damage: i made a gameplay video of me using custom "car" in CarMODgeddon (the part of the game where you play with all custom stuff, cars, etc...) as part of my YT "review" of my monoblock. Wanna join MP? Yeah i'll also record and/or stream it as well if you don't mind. Good to see ya dude.

P. S. Writing from my Galaxy A6, cause ISP got f*cked (Bezeq, quite ancient ISP, they still use ADSL & telephone miniport/filter that goes inside wall socket to get internet signal). They'll fix this connection to their servers issue only this Friday.

*EDIT*

It passed Prime95 Small FFTs 2h+ run @ 3.8GHz/1.4v vCore an hour ago. And i have a shitload of R15 scores in one pic to share here this Friday as well. Aaaaand.... it was throttling but not anymore. I'd love to dig into the AMD CBS thingy this weekend you bet. Cheers.
 
Last edited:
Which kit exactly ? I got something along those lines but mine doesn't want to do shit. Could you post a picture with the timings you use ?

so after messing Im presently at the timings below , all other timings on auto and Tras and tRC were originally auto found , with this CH7 I am having random crashes at the minute if i push higher in game, with those i can use it fine but technically im still getting the odd shutdown ,only when i leave it idly crunching ,odd ,im reinstalling a fresh fresh wiondows , also, I have had most luck on auto settings but upping the current allowance to the memory and Soc and obviously running the memory at 1.35V , I find memory a laborious and individualistic thing to truly optimise these days(ie oc) since integrated memory controller heat is normally imho the weakest link of the effort and finding working settings can take time and a lot of testing but if i advance on these ill let you know..
the kit is corsair VengeanceRGB 16GB ddr4 CMR16GX4M2C3000C15

Also.

i've got protocols missing on boot ,my error thing tells me(mobo bios error lcd not in event viewer), i think its because im not running in full Csm secure boot uefi mode , am i right there?
 

Attachments

  • mem timings.png
    mem timings.png
    137.3 KB · Views: 340
so after messing Im presently at the timings below , all other timings on auto and Tras and tRC were originally auto found , with this CH7 I am having random crashes at the minute if i push higher in game, with those i can use it fine but technically im still getting the odd shutdown ,only when i leave it idly crunching ,odd ,im reinstalling a fresh fresh wiondows , also, I have had most luck on auto settings but upping the current allowance to the memory and Soc and obviously running the memory at 1.35V , I find memory a laborious and individualistic thing to truly optimise these days(ie oc) since integrated memory controller heat is normally imho the weakest link of the effort and finding working settings can take time and a lot of testing but if i advance on these ill let you know..
the kit is corsair VengeanceRGB 16GB ddr4 CMR16GX4M2C3000C15
Controller temps can be a problem, but I would probably still play around with voltage. You still have some DRAM voltage to spare. It's not uncommon to hit a barrier where 1.35 isn't enough and anywhere from 1.355-1.45 becomes beneficial... ...usually at the point where timings are as tight as you can get them and speed is getting up there (seems speed increases nessesitate voltage increases more than timing decrease do, though.) Varies depending on type, but generally if you're trying to push the limits of your DDR4/mobo combination, there's a good chance you might have to pass 1.35. Really top-binned modules can do it, but you can't always expect it. You may just be hitting that point.

And again, a little goes such a long way. You're right, it's absurdly laborious... ...sometimes .005-.01v is the difference between stable and the occasional crash.

IME SOC voltage can be touchy, too. 1.1 isn't enough for my setup. 1.125 is perfect. 1.13+ and it goes to shit again. LLC can be just as important. I think of it this way... ...SOC needs a specific amount of power. So you can't run it loose and up the voltage so that it droops to the level needed, because then there will be times when it also goes just high enough to throw it off. It's not like a CPU where as long as the droop isn't too low, it'll generally work.

Reminds me, sometimes CPU voltage is a factor, too. In the past, upping it a tick has been the difference between working and not. Try it, if you can with the way you're running your CPU.

I dunno, could be a lot of things in your case, but personally if I have a config that boots and passes basic stress tests, but periodically crashes, then my next step is to see if I can't better balance the power to it. There's probably a specific scenario under which it crashes every time, while staying fine the rest of the time. This can either be a power need/delivery fluctuation or sometimes one particular timing causing it to crash during one specific operation that pops up when doing certain things. Somehow it's stumbling only under certain demands. I'd rather find out it's power first, before bumping timings tediously for nothing. Doesn't take nearly as long to rule-out.

Be interested to know if/how you get it figured out. These days I'm trying to learn as much as I can about RAM overclocking. There is much to learn from the suffering of others, so they say.



I've been playing around more with more modest overclocks on my 2600. Just wanna see how cool and quiet I can get things without taking a big performance hit. Today I managed 4ghz at... 1.13v. Now, I don't know if people are somehow over-volting like crazy with their overclocks or what, because I feel like every time I've read about someone trying to hit 4ghz with a 1600 or 2600, the voltage is anywhere from 1.3v to 1.4+v. 1.13v just seems insanely low. I found the instability line just below it. Low 1.12 is total lock-up on linpack... ...like before completing 1. High 1.12 is borderline... ...passes linpacks 9 times out of 10, but randomly shuts every few hours.

But it really has been completely stable at 1.13, and I don't expect it to fail, based on my experience with this particular chip. I did a couple hours of P95. 30 4gb linpacks. Another hour of RealBench. Obviously, I should do some longer tests - and I will put it through a lot of Realbench and maybe even a long stretch of small FFT's, but that it can pass thses suggests that it's likely going to continue working for me.

Maybe golden chip? I can tell you that going up every 50-100mhz past this point puts voltages closer to what you usually see, but it's still low. 1.23 for 4.1ghz. 1.29 for 4.2ghz. Those two I have already used and stressed enough to know they're completely stable. Only real explanation I see is that my sensors read low... ...but that would be scary low, wouldn't it? I'd hope not, but I can't rule it out unless I take my own readings. Imagine if it was actually .2v higher! o_O geez...

One thing is for sure... ...temperatures line up with the voltage. 64C for burner-type stress tests. 55C max for games, and a rare max at that. 50C is more typical. If I kept my fan curves up at where they were for 4.2ghz, I might see it go down another degree or two. Cooling setup in my specs. Standard air setup.

I might just keep it this way. Benchmark scores suffer marginally, but for my usage, I don't notice a difference at all. What I do notice is how I can't hear my fans at all. I'm not used to that. It's nice. Still performs a lot better than that stock boost, where sometimes it'll hit 3.9 under lesser loads for the faster cores and 3.8 across the board, but all cores average at 3.7 under real loads. Much bigger jump than 4ghz is to 4.2ghz, with the benefit of significantly lower power demands and great thermals.

If this pans out, maybe I'll try RAM overclocking again... ...see if running a little further from this chip's clock speed limit helps improve RAM OC stability a little bit. I have voltage headroom now to lock in stability with a slight overvolt. I can probably even lower CPU LLC and switching freqency... ...take a little noise out of the equation.
 
Last edited:
1.13v just seems insanely low.

It is very low, keep in mind that the actual voltage that some motherboards provide is considerably higher than what the value says. This happens even on high end motherboards, LLC can have the same effect too. Frankly it's unlikely your CPU gets just 1.13 volts in reality.
 
Well, my F@H 24/7 clocks..

CPU-Z is reading wonky on the voltages though.. In BIOS I am giving it 1.3125V.... With the droop it drops to what you see in HWInfo. 1.294V. (Going to try 4.1Ghz later but just inching clocks up and thats with the AIO Pump at 1200 RPM. lol. So pretty slow. I already know it will do 4.3Ghz but trying to keep power usage to a minimum so just inching up till I get to that "wall" @ 1.3125V.

desktopbase.jpg
 
Last edited:
so after messing Im presently at the timings below , all other timings on auto and Tras and tRC were originally auto found , with this CH7 I am having random crashes at the minute if i push higher in game, with those i can use it fine but technically im still getting the odd shutdown ,only when i leave it idly crunching ,odd ,im reinstalling a fresh fresh wiondows , also, I have had most luck on auto settings but upping the current allowance to the memory and Soc and obviously running the memory at 1.35V , I find memory a laborious and individualistic thing to truly optimise these days(ie oc) since integrated memory controller heat is normally imho the weakest link of the effort and finding working settings can take time and a lot of testing but if i advance on these ill let you know..
the kit is corsair VengeanceRGB 16GB ddr4 CMR16GX4M2C3000C15

Also.

i've got protocols missing on boot ,my error thing tells me(mobo bios error lcd not in event viewer), i think its because im not running in full Csm secure boot uefi mode , am i right there?
I had a set of team group with similar timings and never could get them to run stable on a CHVI that was a year ago but either way. I sold them! I still had lots of Samsung kicking around, they were just for testing. Not sure what's going on with your boot but there are two things I do that seem to alleviate a lot of random problems. Disable fast boot in BIOS and I also disable fast startup in Windows. Seems to boot much more consistently since I did that.
 
I had a set of team group with similar timings and never could get them to run stable on a CHVI that was a year ago but either way. I sold them! I still had lots of Samsung kicking around, they were just for testing. Not sure what's going on with your boot but there are two things I do that seem to alleviate a lot of random problems. Disable fast boot in BIOS and I also disable fast startup in Windows. Seems to boot much more consistently since I did that.
I had similar ddr3 from Corsair for my 8350, it too was fiddly but I am ok with that, just want more time with it then i have atm.
Few late nights lately, so i reinstalled the latest win 10 release ,set memory to 2866@16,17,17,17 and it is running better, lasted the whole night and is still crunching now, i also got brave and used my old (10yrs) pciex Ocz Revox2 120 as my boot(until I get an nvme), no issues , amazing and it is still potent compared to a samy 850 basic.
More tweaking to follow.
 
Back
Top