<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>ASRock Forums : Will ASRock EVER fix this???</title>
  <link>https://forum.asrock.com/</link>
  <description><![CDATA[This is an XML content feed of; ASRock Forums : AMD Motherboards : Will ASRock EVER fix this???]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Wed, 15 Apr 2026 14:13:13 +0000</pubDate>
  <lastBuildDate>Sun, 06 May 2018 11:44:09 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://forum.asrock.com/RSS_post_feed.asp?TID=8349</WebWizForums:feedURL>
  <image>
   <title><![CDATA[ASRock Forums]]></title>
   <url>https://forum.asrock.com/forum_images/web_wiz_forums_black.png</url>
   <link>https://forum.asrock.com/</link>
  </image>
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : What about VRM settings for mobos...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=51082&amp;title=will-asrock-ever-fix-this#51082</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=5826">Ivan_83</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 06 May 2018 at 11:44am<br /><br /><a href="" target="_blank" rel="nofollow"></a>What about VRM settings for mobos based on ISL95712!?<br><br>http://forum.asrock.com/forum_posts.asp?TID=8594&amp;PID=51080&amp;title=asrock-fatal1ty-x470-gaming-k4-cant-fixed-vcore#51080<br>]]>
   </description>
   <pubDate>Sun, 06 May 2018 11:44:09 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=51082&amp;title=will-asrock-ever-fix-this#51082</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : That&amp;#039;s a useful improvement....]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50380&amp;title=will-asrock-ever-fix-this#50380</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=8771">JohnM</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 24 Apr 2018 at 10:51pm<br /><br />That's a useful improvement. It's a shame BIOS 4.60 doesn't include the latest AGESA as that's what Raven Ridge really needs, and Pinnacle Ridge too. I'll install it anyway to see if it fixes the fan control problem.<div><br></div><div>UPDATE: No, it doesn't. It worked properly on 4.40 though.</div><span style="font-size:10px"><br /><br />Edited by JohnM - 25 Apr 2018 at 3:57am</span>]]>
   </description>
   <pubDate>Tue, 24 Apr 2018 22:51:01 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50380&amp;title=will-asrock-ever-fix-this#50380</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : That BIOS just appeared today.not...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50371&amp;title=will-asrock-ever-fix-this#50371</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=1726">stree</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 24 Apr 2018 at 6:58pm<br /><br />That BIOS just appeared today.not going to bother with it myself,&nbsp; unpacked it to USB just in case, for my X360 ITX and AB350 ITX,but 1.0.0.2a is imminent, already released on some new MBs.<br>Hopefully some all round improvements with it.<br>Have a look at this:<br><br><br><a href="https://www.youtube.com/watch%3cv=dggzOlFvm38" target="_blank" rel="nofollow"><img src="https://i.ytimg.com/vi/dggzOlFvm38/hqdefault.jpg" border="0" alt="AGESA 1002a vs. 1000a.  Ryzen 5 2400G (Ryzen 3 2200G) Asus Prime A320M-K. Bios Update" title="AGESA 1002a vs. 1000a.  Ryzen 5 2400G (Ryzen 3 2200G) Asus Prime A320M-K. Bios Update" /></a><span id=":2e.co" ="tL8wMe EMoHub" style="text-align: left;" dir="ltr"><a href="https://youtu.be/dggzOlFvm38" target="_blank" rel="nofollow">https://youtu.be/dggzOlFvm38</a></span>]]>
   </description>
   <pubDate>Tue, 24 Apr 2018 18:58:07 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50371&amp;title=will-asrock-ever-fix-this#50371</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : Well, ASRock Support contacted...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50339&amp;title=will-asrock-ever-fix-this#50339</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=8933">Thenightstalker</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 24 Apr 2018 at 5:04am<br /><br />Well, ASRock Support contacted me today ...<br><br>The rep said they're digging into that now, at least they tried to work on that cold boot issue. They checked out that HPET Table thing and guess what, they sent me a brand new bios &gt; 4.60<br><br>I just flashed it and tried a bit but can't geht my settings to work right now. Tha HPET Table has now only ACTIVEATED or DISABLED and activated is default. That's at least something ;-)<br><br>AGESA version is still 1.0.0.1a ... :-(<br><br>I now have to go through alot of testing again but not tonight, I'm tired.<br><br>]]>
   </description>
   <pubDate>Tue, 24 Apr 2018 05:04:46 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50339&amp;title=will-asrock-ever-fix-this#50339</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : Yeah ;-)It really seems to work...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50152&amp;title=will-asrock-ever-fix-this#50152</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=8933">Thenightstalker</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 21 Apr 2018 at 1:07am<br /><br /><a href="" target="_blank" rel="nofollow"></a>Yeah ;-)<br><br>It really seems to work now, I was able to reboot today after setting also the frambuffer manually.<br><br>NOW I'm trying to fix the stuttering issue (games stutter heavily when core performance boost is active). I heard using custom pstates would work (for wat reason ever) or at least reduce the problem since you can set the lowest frequency.<br><br>Ok now I'm experimenting with the pstates since about an hour or two but it doesn't work. One thing is, that it sometimes just won't turn on (no post nothing) and when it turns on and boots into windows there's no throttling, it's stuck at 3.9 Ghz (which is max. turbo frequency).<br><br>I tried setting only pstate 0 to 3.9 (I don't need to OC, just max. turbo speed) and leave the others at auto &gt; didn't work. Then I tried setting all manually, didn't worked either. Now I set the first 3 but also no throttling?!<br><br>And I also don't understand why it sometimes won't even post. 3.9 should be no problem, that's the official turbo speed for this CPU so it better run there lol.<br><br>I also set a +50 ofset vor vcore but that didn't changed a thing, Ryzen Master tool always says 1.45 vcore as it is set in the pstate so don't even know why I should set this ofset value there but I read it somewhere and tried it.<br><br><br>]]>
   </description>
   <pubDate>Sat, 21 Apr 2018 01:07:52 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50152&amp;title=will-asrock-ever-fix-this#50152</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? :   Thenightstalker wrote:Yeah,...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50106&amp;title=will-asrock-ever-fix-this#50106</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=6814">cx5</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 20 Apr 2018 at 10:30am<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by Thenightstalker" alt="Originally posted by Thenightstalker" style="vertical-align: text-bottom;" /> <strong>Thenightstalker wrote:</strong><br /><br /><a href="" target="_blank" rel="nofollow"></a>Yeah, looks like I'm going to be happy eventually ... .loool<br><br>And he gave me a tipp also, he said that somtimes LOWERING the ram voltage to 1.25 V could help, I still don't understand how but ok.<br><br></td></tr></table><div><br></div><div>Congratulations on solving.</div><div><br></div><div>Regarding lowering voltage, I recall voltage swing, i.e. how fast the voltage jump from digital 1 to digital 0, theoretically we want instant 90 degrees swing, but that's not in reality, there's a time hence a very steep slope/angle.</div><div><br></div><div>The higher the voltage, the more it has to travel, the longer it takes to complete the change state. That's why we have latency in built, sort of to let it settle clean no bad trailing effects, etc etc jargons I don't know about.&nbsp;</div><div><br></div><div>That's why lower and lower voltages for all sorts of electronics signal processes are exercise.&nbsp;</div><div><br></div><div>A funny rememberance was the AMD Athlon year 2000 ??? there about require overclock the CPU from default voltage 1.5 I think drop to 1.2 and success from 1Ghz to 1.4Ghz crazy concept.</div>]]>
   </description>
   <pubDate>Fri, 20 Apr 2018 10:30:53 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50106&amp;title=will-asrock-ever-fix-this#50106</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : Yeah, looks like I&amp;#039;m going...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50096&amp;title=will-asrock-ever-fix-this#50096</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=8933">Thenightstalker</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 20 Apr 2018 at 6:22am<br /><br /><a href="" target="_blank" rel="nofollow"></a>Yeah, looks like I'm going to be happy eventually ... .loool<br><br>Today it booted up again, no Problem, even at slightly OCed 1630 Mhz :-)<br>Still no idea what's different, maybe the ACPI thing now works, that's the only thing I really changed... oh no, there's one other thing, I haven't manually adressed the frambuffer in my latest attempts because I was too lazy doing it everytime again and again.<br>Maybe that's the reason? If so &gt; no god. I'll test this now, we'll see tomorrow if it still works with framebuffer set to 2 GB.<br><br>ASRock support also answered me, they told me, that they are working on the Uefi setting input (to make it decimal and Volts instead of HEX and VID) for the ITX board. The rep called it "cryptical" and said he'll inform the Bios guys but they are already working. He also told me, that they inform AMD about the RAM issues amd hope they'll fix some of that with a new AGESA release but he couldn't tell me more about... at least he sounded honest.<br><br>And he gave me a tipp also, he said that somtimes LOWERING the ram voltage to 1.25 V could help, I still don't understand how but ok.<br><br>I'll continue testing. I hope they'll also fix the core performance boost thing that causes the stuttering in games. If that's gone and my RAM runs with decent timings I'm happy!<br><br>]]>
   </description>
   <pubDate>Fri, 20 Apr 2018 06:22:06 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50096&amp;title=will-asrock-ever-fix-this#50096</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : Hi @Thenightstalker,These things...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50029&amp;title=will-asrock-ever-fix-this#50029</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=6814">cx5</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 19 Apr 2018 at 11:17am<br /><br />Hi @Thenightstalker,<div><br></div><div>These things a live man......... but congratulations another one going to be very happy customer.</div><div><br></div><div>A few words about re-keying-in the same numbers work in later day..... for my case, I use the calculator then key in everything but fails immediately F9 beep warning. Then I realize don't key in all at once, just use a previously bootable timings, then key in one at a time and reboot, rinse and repeat.&nbsp;</div><div><br></div><div>Along the way I could have swear I used those parameters before, but didn't work, either quick death F9 beep beep, or partial POST Dr.Debug numbers stop half way, but after some time it would accept the new timing, something like that anyway.</div><div><br></div><div><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by Thenightstalker" alt="Originally posted by Thenightstalker" style="vertical-align: text-bottom;" /> <strong>Thenightstalker wrote:</strong><br /><br />Waaait what ... my system just booted up ... cold. OK it wasn't unplugged completely but it was turned off for several hours.&nbsp;<br>.<div>.</div><div>.</div><div>.<br><br>However I still got NO idea what's different this time.<br></td></tr></table></div></div><span style="font-size:10px"><br /><br />Edited by cx5 - 19 Apr 2018 at 11:18am</span>]]>
   </description>
   <pubDate>Thu, 19 Apr 2018 11:17:18 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50029&amp;title=will-asrock-ever-fix-this#50029</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? :   Thenightstalker wrote:Hmm I...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50016&amp;title=will-asrock-ever-fix-this#50016</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=5435">datonyb</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 19 Apr 2018 at 5:06am<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by Thenightstalker" alt="Originally posted by Thenightstalker" style="vertical-align: text-bottom;" /> <strong>Thenightstalker wrote:</strong><br /><br /><a href="" target="_blank" rel="nofollow"></a>Hmm I can't edit the values in the Ryzen Dram calculator tool, I can only read XMP but the values seem to be not right!? <br><br>How can I make sure I really have good settings, it's driving me crazy.<br><br><br></td></tr></table><br><br>...hmmmmmmmmmmm&nbsp; where it says profile version <br><br>change this from v1 to custom and now you can enter your nanoseconds <br>]]>
   </description>
   <pubDate>Thu, 19 Apr 2018 05:06:00 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50016&amp;title=will-asrock-ever-fix-this#50016</guid>
  </item> 
  <item>
   <title><![CDATA[Will ASRock EVER fix this??? : Hmm I can&amp;#039;t edit the values...]]></title>
   <link>https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50011&amp;title=will-asrock-ever-fix-this#50011</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://forum.asrock.com/member_profile.asp?PF=8933">Thenightstalker</a><br /><strong>Subject:</strong> 8349<br /><strong>Posted:</strong> 19 Apr 2018 at 4:50am<br /><br /><a href="" target="_blank" rel="nofollow"></a>Hmm I can't edit the values in the Ryzen Dram calculator tool, I can only read XMP but the values seem to be not right!? <br><br>How can I make sure I really have good settings, it's driving me crazy.<br><br><br>]]>
   </description>
   <pubDate>Thu, 19 Apr 2018 04:50:30 +0000</pubDate>
   <guid isPermaLink="true">https://forum.asrock.com/forum_posts.asp?TID=8349&amp;PID=50011&amp;title=will-asrock-ever-fix-this#50011</guid>
  </item> 
 </channel>
</rss>