How would I know what timing and speed to set for my ram kit? Does the numbers xx-xx-xx-xx on the sticker on the ram helps?
PCB isn't going into the extender? I don't think so, I have tested on other graphics card, functioning the same way (Correct me if I'm wrong in understanding what PCB is)
Do I like the case? Absolutely, just a bit time consuming when taking parts in & out, but i guess most ITXs are like that.. haha
Sorry everyone for not replying sooner. @juvenchan, I sent you a message offering to replace your PCIe extender if it's not working. I also offered to send you a new button if you discovered the switch was bad. After reading your messages, it does seem like the extender is the problem. I had a few extras for just such an occasion so let me know what you'd like to do and I can ship one out to you ASAP.
My kit set is stated 3000mhz, that means i should be able to run at 2933 without issue? what timings should i set? (hynix chips)If you know what speed your ram doesn't boot at, id start from the step below that.
Once you find the speed your system will boot at, then start stress testing.
If you get crashes/blue screens, drop you ram to the next level and repeat until you can both boot and run intensive programs.
Personally if i'd paid for a fast kit of ram that ended up not working as advertised id either try to get a refund, or sell it on second hand and source a kit with better ryzen compatibility.
It has been running great for 2 day straight now with the GPU plug directly into my motherboard.Gotcha, yeah if you tested on other cards then it's the extender. Yeah, building in the case is a challenge, but well worth it!
You're good @grsychckn! I figured he just got a dud or something. In his video as soon as he pulled the GPU out of the case (still attached to the extender), it started working. Very weird!
Mine is SKILL Ripjaws V DDR4 3000 F4-3000C15D-16GVKB, may I ask how you set up on the BIOS (timing) ?I'm using G.SKILL Ripjaws V F4-3200C14D-16GVR @ XMP setting w/o issue.
Those are DDR4-3000 spec RAM modules with CAS Latency of 15, meaning they're SK Hynix chips, you should aim for DDR4-2933 spec but not expect to achieve it with 100% success rate. I've seen some people only getting DDR4-2666 with those SK-Hynix chips. ChinStrap has DDR4-3200 spec RAM modules with CAS Latency of 14, meaning they're Samsung B-die chips, able to achieve the DDR4-3200 spec without problem in most cases.Mine is SKILL Ripjaws V DDR4 3000 F4-3000C15D-16GVKB, may I ask how you set up on the BIOS (timing) ?
Mind you, DDR4-3200 and higher is only possible on RAM modules that are using Samsung's B-die chips. I've read only a few (out of hundreds) of users that managed DDR4-3200 with SK-Hynix chips. One can often spot these as they generally have CAS latencies of 14ns for DDR4-3200 spec and up, while SK-Hynix' current chips sit at 16ns or above.
The FlareX set you have happens to be using those Samsung B-dies, but my Corsair Vengeance LPX CMK16GX4M2B3200C16 doesn't even run stably at DDR4-3066 spec on either my ASRock AB350-ITX/ac or Asus Prime X370-Pro. Chipset doesn't really matter it seems what overclock you can achieve on the memory, BIOS and CPU do.
Mine is SKILL Ripjaws V DDR4 3000 F4-3000C15D-16GVKB, may I ask how you set up on the BIOS (timing) ?
Those are DDR4-3000 spec RAM modules with CAS Latency of 15, meaning they're SK Hynix chips, you should aim for DDR4-2933 spec but not expect to achieve it with 100% success rate. I've seen some people only getting DDR4-2666 with those SK-Hynix chips. ChinStrap has DDR4-3200 spec RAM modules with CAS Latency of 14, meaning they're Samsung B-die chips, able to achieve the DDR4-3200 spec without problem in most cases.
From another X370 thead:
Did anyone try this new BIOS?
Did not and will not. Bad reports over at reddit... CPU OC seems to be resolved (since the retracted 4.20) but DIMM voltage stuck at 1.35V (like in 4.20) and some people with multi-bugs. Asrock dropped the ball on these updates, quite disappointed, while I really like the board...
Mind if you share a link for the reddit thread? interested to see what people are saying about multiplier issues as im still having them after updating to 3.40 a while back
What I eventually figured, was that they must have reset the AGESA versioning with the new Pinnacle Ridge CPU's coming.