Asrock Fatal1ty X370 Gaming K4 - Bios 2.40 vs 3.20 |
Post Reply |
Author | ||
justqw
Newbie Joined: 06 May 2017 Status: Offline Points: 26 |
Post Options
Thanks(0)
Posted: 11 Sep 2017 at 9:41am |
|
Hi,
This is my experience. Maybe it will help somebody. Settings: - Ryzen 1700 - RAM F4-3200C15D-16GVK - Asrock Fatal1ty X370 Gaming K4 2 identical configs on both versions: - Disable core performance boost - CPU Frequency (MHz) - 3800 - CPU Voltage - 1.35V - CPU Vcore Voltage - Fixed 1.35V - VDDCR_SOC Voltage - Fixed 1.1V On 3.20 and others 3.x I got BSOD. Bios 2.40 Everything is stable: - Cpu 3.8GHz - Ram 2993MHz Maybe on 3.20 is a some additional setting needed. I don't know atm. -- Cheers
Edited by justqw - 11 Sep 2017 at 9:42am |
||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
|
Don't you want some advice about your BSOD issue? Does the BSOD occur when Windows (unknown version) boots, or sometime after the Windows desktop is displayed? You can get into the UEFI/BIOS interface when you had the UEFI versions beyond 2.40 installed, correct? Do you get the BSOD if you run your memory at its default speed of 2133? No mention of the DRAM voltage with the memory at 2933, or if you use the XMP profile. What is the BSOD error description in Windows? The UEFI/BIOS versions beyond 2.40 use the newer AGESA processor microcode versions, 1.0.0.6, 6a, and 6b. The new microcode versions include updated memory timing setting not found in earlier UEFI/BIOS versions, like 2.40. Your memory is not listed by G.SKILL as compatible with Ryzen. https://gskill.com/en/product/f4-3200c15d-16gvk As we know, memory like this can work with Ryzen, but will need manual configuration of the memory settings, since the XMP profile is designed more for Intel systems. That is even more important with the newer AGESA versions in the UEFI. Since we don't know the cause of your BSODs, I'm assuming that it is memory related, given in information in your post. We have seen other Ryzen users that have Ripjaws V memory having compatibility problems. |
||
antonio70
Newbie Joined: 09 Sep 2017 Status: Offline Points: 5 |
Post Options
Thanks(0)
|
|
Find me one g.skill memmory on their site that oficially support AM4 motherboard.
|
||
datonyb
Senior Member Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
|
|
well ALL of the flareX memory sticks for starters and then ALL of the fortis range as well ............. but lets not get too angry here ive already asked another member using the ripjaws ram to post his settings he used to get it working stable so maybe we can help you |
||
[url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
||
MisterJ
Senior Member Joined: 19 Apr 2017 Status: Offline Points: 1097 |
Post Options
Thanks(0)
|
|
justqw, if you will upload your compressed minidump folder (in Windows folder), I will see what I can learn. Thanks and enjoy, John.
|
||
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD
|
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
Mmmmm I smell G.Skill goodness being discussed here.
https://www.gskill.com/en/press/view/g-skill-announces-flare-x-series-and-fortis-series-ddr4-memory-for-amd-ryzen |
||
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
|
F4-3200C15D-16GVK
Single Sided, Single Rank Samsung B-die |
||
justqw
Newbie Joined: 06 May 2017 Status: Offline Points: 26 |
Post Options
Thanks(0)
|
|
ket
Senior Member Joined: 13 Jul 2017 Location: UK Status: Offline Points: 1676 |
Post Options
Thanks(0)
|
|
Last I tried getting my RipjawsV to its rated 3200MHz on the X370 K4 the best I managed was 3066MHz @ 14-14-14-25 1T. 3200MHz was just not stable at all despite other X370 test boards running the 3200MHz XMP profile completely fine. Note the stability issue on the K4 has nothing to do with AGESA code version - all test boards were using the same AGESA code, 1.0.0.6. I'm yet to try UEFI 3.2 on the K4. So many things to do, and not enough time to do them all :(
|
||
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |