X370 K4 Bios Update Fail to post after

Welcome to the forums.

Hello

I am having the exact same issue with my Fatality X370 Pro
I updated to latest bios and am now getting POST error code 07
I tried removing batt / clear cmos/ just one ram stick/ no HDD's = not working

Can someone please help me..? Any advice |?

Windows98 wrote: 2x8GB G Skill F4-3000C15D-16GVR I want to update to the newest stuff because my memory kit isn't running at its rated speed.

I believe that kit is made of Hynix based ICs.

Read:
http://forum.asrock.com/forum_posts.asp?TID=4807&PID=27011&title=x370-killer-sli-ram-do-not-exceed-2400-mhz#27011

Windows98 wrote: I have also noticed that Cool n Quiet doesn't appear to be working on my particular chip,

Windows98 wrote: wardog wrote: I believe that kit is made of Hynix based ICs. That's fine, but it doesn't run *at all* on BIOS v 2.00. I can run it just fine @ 2666 on 1.64.  I knew my kit wasn't on the QVL, so after I updated my BIOS and it died, I went out and bought the Corsair kit that everyone got with their review samples and it behaved the same exact way. Error 07.  wardog wrote: That concerns me. What have or haven't you done to confirm CnQ is or isn't functioning? My past several builds have been Intel iX builds, so my gut is telling me to look at two things: clock speed and voltage. If Ryzen operates in a different manner (or reports it in a different manner) then that would explain my inability to see it.  I've noticed voltage is kind of a mixed bag with monitoring apps. CPU-Z is constantly reporting my chip @ 0.64V and it never changes even if I throw a load at it. I just chalked this up to CPU-Z being wrong. HWInfo and AIDA64 seem to report it accurately.  However, nearly *every* monitoring app shows my clock speeds at ~3692mhz, which indicates that: 1: My processor has a random ~+100mhz clock over the base clock for some reason. 2: It isn't falling into the lower p-states.  I have been running HWInfo (v5.5) while I've been typing this post. The minimum reported core speed on all cores is 3,692.7mhz, which is approx 100mhz higher than my base clock speed should be (3,600mhz). I can see that one of the cores did kick into XFR, but that state also has a +100mhz bump 4,091mhz instead of ~3,991mhz.  per the latest AMD Ryzen blog post, monitoring apps will evidently show last reported clock the core was on prior to it entering it's low P-state...so even if the apps are misreporting the various P-states on my chip, they should show the last "step" before the core goes into one one of those low-power states. In my case, all of the cores are reporting a minimum clock of 3692.52MHZ ...not the 3200-3400 reported in the post above.  I am also running the latest Ryzen Chipset drivers and the Ryzen power plan (the latter is linked in the blog post above). I've tried toying with the "minimum processor state" options in Power Settings and that makes no difference either (that I can tell). AS SUCH... I have been operating under the assumption that this would all get "fixed" in a microcode update from AMD...hence giving me another reason to update to the latest BIOS.  Edit: I just rebooted my PC and checked out BIOS to make sure I hadn't inadvertently set a custom ratio on the CPU. Everything is on auto except my RAM (I loaded an XMP profile, backed the clock speed from 3000 -> 2666).

Tonight I'll take a see at what you describe. Yet if any app, CPU-z or other, shows 0.64v rest assured it read that voltage from sometime since your last boot into Windows.

I have noticed Ryzen seem to take a longer time than I'm used to in settling down after a (re-)boot. Minutes actually. Sure you're not "waiting long enough' to notice this?

It's much to early to come to conclusions about what is happening with the Ryzen P-States, etc,  for many reasons. One important one is, the monitoring programs don't have Ryzen right yet. Even HWiNFO needs some work. CPU-Z cannot deal with Ryzen's RAID, it locks it up before it's done with its detecting phase.

Plus I've found that the UEFI/BIOS option settings for VCore and multipliers seem to affect what is shown in monitoring programs. I wish HWiNFO could show the P-State levels and percentages like it does with the Intel C-State levels and percentages.

Here's my HWiNFO example:



This is with the core multipliers set to 37, and the VCore set to Offset, and the offset value left on Auto. You can see the CPU frequency never changes, like yours. But the VCore can drop to a super low 0.384V, and yes it is stable, I just took that screenshot a few minutes ago. Also check the minimum core power values, below 0.1W. I'm using the Ryzen power plan, Windows 10. C n Q enabled, C6 enabled, and the P States expanded in their screen in the UEFI.

I have seen the 1.5V+ VIDs, with VCore set to Auto. Get rid of Auto if you want that gone. Just a VID though, so if like an Intel processor, not the true VCore.

With my Intel systems, Z270 and i7-7700K for example, if I used the Windows High Performance plan, the CPU frequency would stay high, and never drop to 800MHz, with all C states down to C7 enabled. But the C State monitoring in HWiNFO would show I was in C7 90+% of the time.

IMO, to early to say exactly what is going on precisely. Our tools are not good enough, and we are still learning Ryzen.