• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AMD Zen 2 (Ryzen 3000) - *** NO COMPETITOR HINTING ***

Got some G.Skill 3200 CL16 Hynix M-Die and it does not like 3200 XMP or even with the calc (did not put much time in it) on both B350 and X470 with a 2700. Have not tried it with the R5 3600. My G.Skill FlareX, otoh, works on both Gens without drama using XMP.
With x470 and 2700x I could never ever get above 3000mhz stable on the memory ever, either the imc or mb or the combination of both
 
I already closed iCue (another compromise made) and on Ryzen balanced it never drops, but if I switch to Windows balanced then it does drop to idle. It's clearly the power plan.

It can't be the power plan else it would do it for everybody, and I'm using the Ryzen balanced and see it drop to as low as 0.2v.

The reason the windows balanced allows it to drop to idle is because it bypasses CPPC2, so all the requests from various things on the system get ignored most of the time. Robert from AMD even explains this;

Robert@AMD said:
Some have noticed that switching to the Windows Balanced plan, instead of the Ryzen Balanced Plan, causes idle voltages to settle. This is because the default Balanced Plan, with 15ms intervals, comparatively instructs the processor to ignore 14 of 15 clock requests relative to the AMD plan.

So, if the monitoring tool is sitting there hammering the cores with boost requests, the default plan is just going to discard most of them. The core frequency and clock will settle to true idle values now and then. But if you run ourperformance-enhancing plan, the CPU is going to act on every single boost request interpreted from the monitoring tool. Voltages and clock, therefore, will go up.

He also mentions a few things to check, In the BIOS, under CPU voltage, what settings do you have? Do you have the option to set between Auto and Normal?

Robert@AMD said:
If your BIOS has the option to set CPU voltage to AUTO or NORMAL, please try setting it to normal

Do you have the Ryzen power saver and High performance power plans available to select? (if so then this generally means the chipset driver installed correctly)

If you haven't already read through the detailed pdf brief he released explaining why these things happen then it's really worth having a good read through

https://community.amd.com/servlet/J...2-124770/Community_Update5_Detailed_Brief.pdf
 
Funny thing is i can play a game for a bit no problem at times, do stuff in windows and it just crashes more easily.

How would b-die fix it? Even G.Skill are selling Hynix kits for the new AMD chips.. This is just stupid though, still not sure what the problem is.

Contacted both G.Skill and Asus support now anyway just to see what they say.

Guess You dont know that reality is or You get Micron E die or samsung B die or you get problems. Been like that since start od Ryzen and it will be like that.

You think why Ryzen specific memory kits got created ??
 
Crashed 2 times in a row just trying to log into windows, like 2-3 times last night in the span of 20 min just watching youtube, crash browsing using edge, crash starting a game.

Guess i will try memory at 2133mhz or whatever, this is just BS.

Did you check they are inserted into the recommended DIMM slots on the motherboard, usually A2 and B2 (check motherboard manual to confirm). Did you run a memory test at default SPD settings i.e. Bios default settings (NOT the XMP overclocked profile).

Looking at the Thaiphoon screenshot it shows they are using 4Gb M-die 29nm Hynix chips dual rank (double sided). I wonder if they are more difficult to drive on AMD platform. I dont know the maximum safe voltage for those 29nm Hynix chips, you could google to see what it shows at your own risk, the 25nm M-Die chips usually have 1.35v for their XMP profile but I dont know the safe voltage for your 29nm chips. You could keep the DRAM voltage at 1.2v, manually set your timings, and lower your RAM speed to see if its stable, maybe it cant drive them at 2800 speed.
 
Did you check they are inserted into the recommended DIMM slots on the motherboard, usually A2 and B2 (check motherboard manual to confirm). Did you run a memory test at default SPD settings i.e. Bios default settings (NOT the XMP overclocked profile).

Looking at the Thaiphoon screenshot it shows they are using 4Gb M-die 29nm Hynix chips dual rank (double sided). I wonder if they are more difficult to drive on AMD platform. I dont know the maximum safe voltage for those 29nm Hynix chips, you could google to see what it shows at your own risk, the 25nm M-Die chips usually have 1.35v for their XMP profile but I dont know the safe voltage for your 29nm chips. You could keep the DRAM voltage at 1.2v, manually set your timings, and lower your RAM speed to see if its stable, maybe it cant drive them at 2800 speed.

Yep, i just checked my Ripjaws V that's full of drama is M-die 25nm, while my B-die kit is 20nm. Rightnow my M-die is paired with the R7 2700 and it only works at 2933 Cl16 DOCP (XMP). Better than 2400MHz.
 
Guess You dont know that reality is or You get Micron E die or samsung B die or you get problems. Been like that since start od Ryzen and it will be like that.

You think why Ryzen specific memory kits got created ??
I know it was picky with RAM but i thought the new chips supposed to have fixed that, look at the new Neo G.Skill kits, one of those is supposed to be Hynix and those kits are made for new Ryzen chips.

Did you check they are inserted into the recommended DIMM slots on the motherboard, usually A2 and B2 (check motherboard manual to confirm). Did you run a memory test at default SPD settings i.e. Bios default settings (NOT the XMP overclocked profile).

Looking at the Thaiphoon screenshot it shows they are using 4Gb M-die 29nm Hynix chips dual rank (double sided). I wonder if they are more difficult to drive on AMD platform. I dont know the maximum safe voltage for those 29nm Hynix chips, you could google to see what it shows at your own risk, the 25nm M-Die chips usually have 1.35v for their XMP profile but I dont know the safe voltage for your 29nm chips. You could keep the DRAM voltage at 1.2v, manually set your timings, and lower your RAM speed to see if its stable, maybe it cant drive them at 2800 speed.
IMG-20190818-183707-1.jpg

CPUZ shows them running 1032Mhz so it looks like it's correct? I mean 1064, my mistake.
 
@Perfect_Chaos
It was fixed on Zen+ more or less zen 3 is new so here we go again :D
GAs you say ONE ot all them kits are Hynix rest will be B die. Bet that the crappiest kit is hynix and its using best hynix bins and specific pcb/xmp design to make it work with no problems.
 
X470-i on 2501, latest AMD chipset drivers

I am on the same Board and Processor! There is a new BIOS on the ASUS website (2606) plus there is also a beta BIOS on the support forums (2701)

I have the same issue as you! I noticed that my CPU never went below 1.45V even when just sitting idle on the desktop. So I updated to the 2701 beta BIOS and just left everything at default and have noticed that CPU volts does dip under 1.0v but it's for like 2 seconds at a time.

Problem is my memory doesn't seem to run at the full rated speed when the setting in the BIOS is set to AUTO. So I changed my memory to run at 3600mhz which it should be able to just fine (Trident Z). But when I manually changed the memory frequency I have now noticed that my CPU volts don't go under 1.45v again. So I put the memory frequency back to auto in the BIOS and it dips as low as 0.95v once again.
 
The 26xx and 27xx bioses dont work any good on Auto settings from what I see. As soon as I went full on Manual even weird booting up got fixed.



Manual in everything i could find what Standard setting should be.

Its so annoying that bioses dont display what Auto does actually set... Cant even compare settings bios to bios cause of that.
 
Everything seems to be working fine for me now. Keep as many variables auto and only fiddle with a a few. Makes it easier to debug.

Keeping all my voltages on auto but simply upping the dram voltage and now I am looking good at 3600MHz.

You cannot dial in all those values and expect things to remain the same as they change from BIOS to BIOS.

Hence auto is better and only change the key values.
 
Everything seems to be working fine for me now. Keep as many variables auto and only fiddle with a a few. Makes it easier to debug.

Keeping all my voltages on auto but simply upping the dram voltage and now I am looking good at 3600MHz.

You cannot dial in all those values and expect things to remain the same as they change from BIOS to BIOS.

Hence auto is better and only change the key values.
Tell that to chaps that cant even boot up on this bios and stay anywhere near stable cause they are on auto. And auto values on 2701 are ****** up
 
Last edited:
I ran AIDA64 for nearly 3 hours last night with YT videos running, came back to PC all still going fine. Stopped the test and went to play another video in YT and straight to blue screen. Then i had 4-5 crashes in a row quickly after restarting each time. Makes no sense at all
 
@opethdisciple to be fair, my system is performing brilliantly. I'm not hitting advertised clocks, I'm having to do without some functionality and I'm reluctant to change anything in BIOS else I'll have to clear CMOS yet again... But at this moment, it's performing brilliantly.

That's probably the most frustrating thing; I know it's an awesome chip, I just don't think I should be Beta testing for AMD. That's not what I paid my money for.

Hopefully bug fixes will come soon because for a lot of people this is more than an inconvenience, and they've paid a lot of cash for broken systems.

I didn't buy my 2700x until over 6 months after release, and if I've learned anything from this recent purchase, it's not to buy AMD kit too soon (if at all, obviously).
 
Back
Top Bottom