AGESA 1.0.0.6a |
Post Reply | Page <1 1718192021 23> |
Author | ||
Windows98
Newbie Joined: 11 Apr 2017 Status: Offline Points: 22 |
Post Options
Thanks(0)
|
|
I have the Gaming K4 and have never been able to get my kit (F4-3000C15D-16GVR) to run stable above 2666.
If I choose the XMP profile for my RAM (15-15-15-35 @ 3000), it actually commits 16-15-15-35 @ 3000. Even if I go in and modify the CAS to 15, it still boots at 16. The only way I can get those timings to stick is if I set my XMP to "auto" and let the board figure out the timings itself (which it does correctly -- but clocks the ram to 2133. tl;dr -- my board refuses to accept 15-15-15-35 @ 3000 but will happily run those timings @ 2133.
|
||
Drain_Bamaged
Newbie Joined: 14 Jul 2017 Location: Lalaland Status: Offline Points: 48 |
Post Options
Thanks(0)
|
|
^ it's known Ryzen doesnt do uneven CAS timing.
|
||
Windows98
Newbie Joined: 11 Apr 2017 Status: Offline Points: 22 |
Post Options
Thanks(0)
|
|
|
||
Drain_Bamaged
Newbie Joined: 14 Jul 2017 Location: Lalaland Status: Offline Points: 48 |
Post Options
Thanks(0)
|
|
Who the hell uses 2133 on Ryzen though. Strange that RAM speed changes it's dislike for uneven CAS timings but using 2133 isn't exactly a valid trade off.
|
||
Windows98
Newbie Joined: 11 Apr 2017 Status: Offline Points: 22 |
Post Options
Thanks(0)
|
|
I've experimented with it. It runs with the uneven timings @ 2666 with no issues. At 3000 (2933) it runs stable for approx 4-5 days and then BSOD's on me. I'm trying 2800 right now (16-15-15-35) to see what happens. I still can't figure out how/why the timings won't commit if I input them manually. Worst case it shouldn't post, but instead it just changes the CAS to 16. Edited by Windows98 - 04 Aug 2017 at 12:30pm |
||
Drain_Bamaged
Newbie Joined: 14 Jul 2017 Location: Lalaland Status: Offline Points: 48 |
Post Options
Thanks(0)
|
|
I'm referring to CAS 15,17 etc. 16 will work no problem. Perhaps I'm confused by your post.
|
||
Windows98
Newbie Joined: 11 Apr 2017 Status: Offline Points: 22 |
Post Options
Thanks(0)
|
|
I thought it was pretty clear, but I'll lay out the scenarios:
My sticks are rated @ 3000 with 15-15-15-35 timings.
1. Resetting BIOS to defaults sets my memory at 15-15-15-35 @ 2133. (which is fine) 2. Loading XMP defaults properly loads the timings (15-15-15-35 @ 3000), but BIOS seems to ignore the CL of 15 and sets it to 16. No matter how much changing I do, it always reverts back to 16. In scenario 2 my machine randomly BSOD's once a week or so. I feel this is related to the CAS timings, of which I can't change for some damn reason. If I back the speed off to 2666 with the same "bad" timings, it also appears stable. So in other words, I can't tighten my timings to their appropriate values because the BIOS is being stupid. Edited by Windows98 - 04 Aug 2017 at 12:43pm |
||
Drain_Bamaged
Newbie Joined: 14 Jul 2017 Location: Lalaland Status: Offline Points: 48 |
Post Options
Thanks(0)
|
|
ok enjoy your snark and your 2133.
|
||
Windows98
Newbie Joined: 11 Apr 2017 Status: Offline Points: 22 |
Post Options
Thanks(0)
|
|
oh ok thanks for your help
|
||
chainsaw
Newbie Joined: 05 May 2017 Status: Offline Points: 95 |
Post Options
Thanks(0)
|
|
ASRock Fatal1ty X370 Gaming K4 P3.40
AMD RYZEN 7 1700 @ 4Ghz 1.39v Noctua NH-D15 "blocks top 1x pci-e" 16GB GSkill Ripjaw V F4-3200C16D-16GVRB @ 2933 14-15-15-15 T1 1.365v GTX 1080 x2 Sli |
||
Post Reply | Page <1 1718192021 23> |
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 |