• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

AMD Ryzen Discussion Thread.

Frankly, AMD doing the temp offset thing for a "consistent fan profile" always struck me as really really strange. Yeah, it's confusing as if they were trying.
Yeah, I'm not a fan of it at all to be honest. :( This platform also has a lot of voltage reporting errors from what I'm seeing too, which adds to the confusion.
 
So back to hard modding sensors to the board? :D
 
Try disabling the sense MI skew for non X will give more realistic readings
 
Try disabling the sense MI skew for non X will give more realistic readings
That did the trick for me, it's how I've been running it since day one. Temps are much closer to what should be accurate.
 
NIce,disabling on the "X" removes the 20° offset as well
 
where do you usually find that sense mi feature in the bios? or is it exclusive for asus chVI hero only?
 
where do you usually find that sense mi feature in the bios? or is it exclusive for asus chVI hero only?
I never had the Taichi running long enough that I messed with it and found it. Unfortunately I have no clue if it has that setting :(
 
where do you usually find that sense mi feature in the bios? or is it exclusive for asus chVI hero only?

As far as I know, it is only related to the Crosshair VI Hero since it is a bug within the bios 0902.


Temperature readings (fixed in 1001 and later)

Tctl readings can be off on 0902, to fix set Sense Mi Skew = Enabled and Sense MI offset = 272. Most reliable sensor is the CPU sensor reading from SIO (listed under Crosshair VI Hero in HWInfo64). New BIOSes should be OK with defaults SenseMi Skew setting of 272.
 
my only issue with this chipset now is not being certain of the temps. my temp for the die jumps to 28 27 26 25 - 18c on the rog front base. HWMonitor has it @39c then jumps to 46c and counts back down to 39 and then sits there for a few seconds. after reading what others are doing. this is probably sensemi related. i'll try turning it off later.
 
my only issue with this chipset now is not being certain of the temps. my temp for the die jumps to 28 27 26 25 - 18c on the rog front base. HWMonitor has it @39c then jumps to 46c and counts back down to 39 and then sits there for a few seconds. after reading what others are doing. this is probably sensemi related. i'll try turning it off later.
Mine were better with it off. But I am still skeptical about the temps to be honest.
 
Okay, I haven't built my system yet, but not being able to check temps reliably is starting to worry me....not that I was going to OC from the get-go anyway, but still

Aside that, calling all MSI X370 GAMING PLUS/PRO (not carbon)/KRAIT/SLI PLUS owners!!!
I noticed two jumpers on my gaming plus that are not documented, JOV1 and JOV2...any idea what they might be?
Now...common-sense tells me, since one is near the socket and the other near the DIMMs, they must enable off-spec voltage settings, but I haven't assembled it yet, so I can't tell...but I'm curious :D
 
I got it up to 4 GHz without any problems, but cant get over 2133 MHz on the mem.
Think I will watch @phanbuey ´s ram OC video.......

Since no-one answered, I had an issue with my Asus board as well, same as you, being stuck at 2133MHz for the RAM. Turns out that after a UEFI update, you need to do a hard reset and then it works to set the memory frequency. Some weird Asus bug it seems. The best speed I get out of my RAM and 3000MHz though, no 3200 as yet.
 
@jp there are 2 pin connectors for sensors. I have a couple so I thought I might try to get some readings. but where would I need to put the sensor and when you say hard modding sensors to the board, where and how.
I'm interested in trying...:toast:

ps have you seen the oculus rift price... ive dropped some cash on one... off topic I know so just a heads up.
 
Last edited:
I really like what this guy is saying about this motherboard. Especially when it comes to memory. Also it has a bad look, i also don't like the black and white. and it has no rgb light on it....even though it does have the option to add rgb strips and play around with the msi app.

I also have my eye on the more expensive 80$+ https://www.msi.com/Motherboard/X370-GAMING-PRO-CARBON.html#productSpecification-section
This one has an Intel lan chipset ,rather than Realtek ,better look,build in under the motherboard rgb lights.
I think it all boils down to if you hate the black/white theme and if you wanna have Intel Lan.
What do you guys think ?
 
I really like what this guy is saying about this motherboard. Especially when it comes to memory. Also it has a bad look, i also don't like the black and white. and it has no rgb light on it....even though it does have the option to add rgb strips and play around with the msi app.

I also have my eye on the more expensive 80$+ https://www.msi.com/Motherboard/X370-GAMING-PRO-CARBON.html#productSpecification-section
This one has an Intel lan chipset ,rather than Realtek ,better look,build in under the motherboard rgb lights.
I think it all boils down to if you hate the black/white theme and if you wanna have Intel Lan.
What do you guys think ?

http://www.asrock.com/mb/AMD/Fatal1ty X370 Gaming X/index.us.asp
http://www.asrock.com/mb/AMD/Fatal1ty X370 Gaming-ITXac/index.us.asp
http://www.asrock.com/mb/AMD/Fatal1ty X370 Gaming K4/index.us.asp
http://www.asrock.com/mb/AMD/X370 Killer SLI/index.us.asp
http://www.asrock.com/mb/AMD/X370 Killer SLIac/index.us.asp
 
Right, so...I'm undefeated but not very happy right now.
Spent part of this weekend assembling the rig, more time troubleshooting than the dissasembly/cleaning thoroughly/assembling process. :(

It doesn't POST.
EZ debug CPU LED stays on, then off, fans full blast and nothing more...
MSI says this means the CPU is not detected.

Tried the usual steps, reseating the CPU twice, ran all memory banks with both DIMMs individually...

My long-shot conclusion is, the board came with a very early BIOS build and its not playing along with the F4-3200C16D-16GTZB kit
I say this because, reading a bit about it, most MSIs that don't start from the get-go and signal that there is a problem with a CPU, it's actually the RAM that isn't getting pick-up. Run-of-the-mill QVL 2133MHz sticks seem to solve it until you can update the UEFI (which is somethign I don't have), however, it's a mess online when it comes to MSI boards not posting, every kind of situation and "snake-oil" solutions being found in forums.
I'm aiming at the DIMMs though. AMD has always been picky about this, my FM2 was no different.

EDIT: Okay, didn't word it like that, but also reaching for you guys for ideas to get the bugger to post at least :D
 
Last edited:
Well, I came back my hols and my DOCP memory setting wouldn't post. Continually 3 beeps then nothing. Safe boot and reset, put timing manually to 3200 with latencies untouched 16's instead of the DOCP 14 value. Working fine.
Will upgrade BIOS when it's not a beta for the AGESA one.
 
Okay so, I feel dumb right now. The kit I bought is not on the QVL list. :banghead: :(
That might be the very reason it doesn't post, but I'm still wondering how the hell I made the mistake because I know I checked for compatibility :confused:
 
Okay so, I feel dumb right now. The kit I bought is not on the QVL list. :banghead: :(
That might be the very reason it doesn't post, but I'm still wondering how the hell I made the mistake because I know I checked for compatibility :confused:

Which kit exactly did you buy?

Also, a stupid question: have you tried to reset CMOS?
 
@_JP_ I'm using the same exact kit on my Ryzen setup and had no trouble with it. I'm using an Asrock board but the ram isn't on it's QVL either.

Note that I did have an initial issue with the ram not being fully seated in the slots (one stick wasn't showing up) but other than that it's doing fine.
 
Which kit exactly did you buy?

Also, a stupid question: have you tried to reset CMOS?
G.Skill Trident Z F4-3200C16D-16GTZB.
The C14Ds are on the QVL list. Mine having loose timings should help, I figure. They are SS B-dies, IIRC, so they should work (been thinking about it over lunch. That might have been my logic, tighter timings bring difficulties. I do remeber I picked this kit over another because it was the ones in stock.)

And yes, I've cleared the CMOS. Multiple times. :D
@_JP_ I'm using the same exact kit on my Ryzen setup and had no trouble with it. I'm using an Asrock board but the ram isn't on it's QVL either.

Note that I did have an initial issue with the ram not being fully seated in the slots (one stick wasn't showing up) but other than that it's doing fine.
I did find the slots a bit flimsy, but they seemed nicely seated and locked every time. I made each DIMM sit on every one, no only on DIMMA2, like MSI recommends.
 
Last edited:
G.Skill Trident Z F4-3200C16D-16GTZB.
The C14Ds are on the QVL list. Mine having loose timings should help, I figure. They are SS B-dies, IIRC, so they should work (been thinking about it over lunch. That might have been my logic. I do remeber I picked this kit over another because it was they stock they had.

And yes, I've cleared the CMOS. Multiple times. :D

I did find the slots a bit flimsy, but they seemed nicely seated and locked every time. I made each DIMM sit on every one, no only on DIMMA2, like MSI recommends.

Question: Does the C14D refer to the latency of 14?

I ask because I have the C14D set and it works fine at 3200MHz. BUT - when i use the proper setting the mobo bugs out with the latency at 14. It has zero issues when runniung manually at 3200MHz and the latency at 16.

That's Ryzen for you....
 
G.Skill Trident Z F4-3200C16D-16GTZB.
The C14Ds are on the QVL list. Mine having loose timings should help, I figure. They are SS B-dies, IIRC, so they should work (been thinking about it over lunch. That might have been my logic. I do remeber I picked this kit over another because it was they stock they had.

And yes, I've cleared the CMOS. Multiple times. :D

I did find the slots a bit flimsy, but they seemed nicely seated and locked every time. I made each DIMM sit on every one, no only on DIMMA2, like MSI recommends.

That's the exact model i'm using but i'm still @ the detected speeds, which is 2133 or 2400 (not sure) because i'm a complete noob when it comes to Linux so i figure learn to work with Linux 1st and then tinker with the speeds (CPU as well as RAM).

Ofc the mobo i'm using is different, so there's that ...

Could there be a problem with the RAM modules? Do you have a friend that can test the RAM for you to rule that out?
 
Question: Does the C14D refer to the latency of 14?

I ask because I have the C14D set and it works fine at 3200MHz. BUT - when i use the proper setting the mobo bugs out with the latency at 14. It has zero issues when runniung manually at 3200MHz and the latency at 16.

That's Ryzen for you....
It does seem like it to me :ohwell:, C14 for 14-14-14-34 and C16 for 16-18-18-38.
That's the exact model i'm using but i'm still @ the detected speeds, which is 2133 or 2400 (not sure) because i'm a complete noob when it comes to Linux so i figure learn to work with Linux 1st and then tinker with the speeds (CPU as well as RAM).

Ofc the mobo i'm using is different, so there's that ...

Could there be a problem with the RAM modules? Do you have a friend that can test the RAM for you to rule that out?
Right, that's what I was expecting, for it to boot but at those speeds. Guess I wasn't that lucky. :laugh: I'm still convinced the board was shipped with an early UEFI version. I need it to post once so that I can update it.
Thing is I don't have extra DDR4...say, 2133MHz, but I'll try to source a stick this week.

I think the modules are fine, because I tested them both, individually and the result was always the same.
 
Back
Top