Asrock X370 Fatal1ty Gaming K4 Review

[Ket]

Thanks for the review Ket

I've looked @ this particular board but unfortunately I need @ least 8 SATA and I'm too tight to buy the X370 Taichi that sells @ $110 more than the reviewed board

Making use of those M2 slots isn't a option I take it then? If not thats unfortunate The board performs very well I'm still using it now testing out the memory capabilities of the board.

Unfortunately, I still can't run my Flare X 3200 MHz @ Cl14 as intended. What made me further pessimistic was ASRock's reply saying 3200 Mhz "may" never work with K4. Perhaps that's why they're releasing an almost identical board called X370 Gaming X.

https://www.reddit.com/r/Amd/comment..._and_gaming_x/

Credit to ASRock for at least being honest. Although if true, it kind of sucks.


Right. The issue appears randomly and I can't replicate it. Currently it's fine. I've experienced this with SteelSeries Arctis 3 plugged into 3.5 mm front jack.

I the issue may have started with 2.40 BIOS. To quote some users @ Reddit:




It could be the Realtek driver, yeah. Perhaps Windows 10 incompatibility? Maybe the very new ALC1220 chip. Although some user are running the older ALC892. Hard to say.

https://www.reddit.com/r/Amd/comment..._messing_with/

Roccat Kulo 7.1 headsets have a not unrelated issue the driver will not always initialise properly if they are left plugged in and the system powered on. The Asrock board is not the first X370 I've experienced this issue with so you adding that Arctis to the list it can at least be confirmed headsets with both 3.5mm and USB connections experience problems. I would hazard guesses at the Asmedia and Realtek drivers need some tweaking so for the time being try finding the newest possible versions you can of those drivers and see if it makes a difference.

Leave the G.Skill issue with me, my testing is showing that my RipjawsV 3200MHz kit throwing out errors after around 7 hours despite running 14-14-14-14-25 1T timings @ 3066MHz for a 17 hours HCI memtest run absolutely fine. I'm currently 1 hour in to a HCI test run @ 3066MHz with 14-13-13-13-25 1T timings also absolutely fine so far.

What I can suggest trying at this time though is change tRC to 75, tMAW.MAC to 1, and try the Flares in both sets of DIMM banks. If that doesn't work out you can try disabling Gear Down Mode and Advanced Boot Training, as well as experimenting with Enabling / Disabling either of those settings. I haven't added them yet to my testing but they could make a difference. As a last resort you can also try setting a command rate of 2T then tightening up the timings manually as much as you can, I don't know what impact switching to 2T will have as I'm still on 1T testing but switching to 2T with a tRC of 75 should show a significant improvement in compatibility.

I can also say that one of my contacts has said to me that memory compatibility is something they are working on a solution for but thats all I know.