Someone knowledable on memory voltages want to chime in? (also what is PMIC and should I be worried)

[ShrimpBrime]

That is so far beyond where I am at right now.. just playing with 1:1.. speaking of which.. since I have some attention, is VDD and VDDQ supposed to be the same all the time or..? I have kept them the same.. but it gets kinda toasty

Why? ir_cow should take care of you and send a proper kit.

I am terrible for that..

Sorry OP.


I have never seen that.. crazy!

I been trying to help....

He's got a bad stick of ram with a janky PMIC.

 

[Svedski]

@Svedski just crossed my mind, have you been keeping chipset drivers up to date while you've been updating BIOS/AGESA? There seem to be some changes afoot and it's not every day I see MSI put in BIOS notes that a certain BIOS revision should be paired with a specific chipset driver version

This DID cross my mind - I've tried installing Windows and drivers 5 times or 6 times and the problem persists. The last time I tried to install Windows I specifically paired the NEWEST BIOS, with the NEWEST chipset driver from MSI instead of from AMD's site directly (it was indeed a different version), and the problem persists.

Though, I have NOT tried reinstalling Windows with the OLD BIOS (I used to have) and using the MSI chipset from the site, (The dates between them are about 1.5 - 2 months). I'm asking myself if I even want to bother at this point. Thanks for making me realise this either way.

The overtemp flag is a bit of a headscratcher as that shouldn't be part of the spikes......but it would help if OP could get a screenshot of when it's actually doing it. The OP pics look normal. Think I've only seen overtemp once and it is just a HWInfo-ism

View attachment 393198

"When" it's doing it is seemingly random (or not (more on this below)), It seems to trigger at random (as stated all the values), be it idlying or light usage, it did NOT trigger when I ran memtest for like 40mins at one point.

I've noticed this now, and this is a small sample size - this seems to, in my theory happen when HWInfo opens - I've not been opening HWInfo at PC start, have been using it, and 2 out of 2 times when I opened after a not so extended session, the values were normal, and the RAM was detected in the info panel as you would expect. Then seemingly it starts to happen a minute, two or a few after HWInfo is open.

Any ideas what other program I could use to check values? As I've said, when it gets greyed out / PMIC triggers - the RAM modules also dissappear from OpenRGB.

 

[ir_cow]

That is so far beyond where I am at right now.. just playing with 1:1.. speaking of which.. since I have some attention, is VDD and VDDQ supposed to be the same all the time or..? I have kept them the same.. but it gets kinda toasty

After 1.5v VDDQ can get finicky and won't boot on some memory kits. Haven't really figured it out yet because they all use the same PMIC. I'll stop between 1.5 and 1.55v and just keep going. With the VDD if need be.

Why? ir_cow should take care of you and send a proper kit.

You could send one too

I been trying to help....

He's got a bad stick of ram with a janky PMIC.

What if they both give the same warning message?

 

[ShrimpBrime]

What if they both give the same warning message?

What if you try a different kit and the symptoms go away?

At what point would the suggestion to try a different piece of hardware vs breaking down how a PMIC communicates via the motherboard chipset with RGB and possible interference from software and or firmware?? We can really make a lot of guessing. Quickest way to find out, use different memory. If a different kit displays the exact same issue, then maybe start hunting down the issue elsewhere.

The memory works as far as we know otherwise. Don't have extra kits, or don't want to spend money, learn to ignore the possible false reading nobody has ever seen before and will entice pages long more guessing.

No? I shall digress now.

Good luck gentlemen!

 

[freeagent]

ou could send one too

I have 3 sets of high end DDR3 here for him, and a board but I am terrible with my finances once my bills are paid

 

[Svedski]

Update: It seems my theory ''seems'' to hold true - that is, I can use the PC however long I want to (the sample pool is still just this evening), and as long as I don't start HWInfo (or for that matter OpenRGB (I would assume, I haven't tried yet), the PMIC sensors will always start at ''no'' and then after a few minutes of HWInfo being open, the usual happens.

I don't think I'm very smart personally hah, but this seems to me like a software / firmware issue in this case. I've yet to try if OpenRGB does the same though. Thoughts?

It hurts that my posts on this forum are probably training the google ai lmao, cause I know it is, I've seen it reference me more than once lol




Very odd, I am running Trident Z5 memory as well (although it's a higher bin), with higher voltage (at 7600 MT/s), and the overtemp and overvoltage detection doesn't trigger. Are you able to place a fan on top of your memory sticks for a test? Mine gets plenty of air, so that's a consideration. Does it drop the speed once this flips to yes?

View attachment 393196

I'm not sure how I would go about testing the speed, I'm under the impression that the system will be generally unstable if the RAM is actually causing issues. I really don't think it's the temperatures, happens on idle and it's an open case. It's usually less than 20*C here, and there's a fan always blowing on the RAM (CPU fan)

https://imgur.com/9kapp4p

-122*C first time this happened in many hours of restarts, and general troubleshooting and seeing what happens. That's one hell of a cooling setup I have huh?

Surely false readings in this case? It always SUDDENLY spiked by ~10*C. Now it does this.

 

[tabascosauz]

-122*C first time this happened in many hours of restarts, and general troubleshooting and seeing what happens. That's one hell of a cooling setup I have huh?

Surely false readings in this case? It always SUDDENLY spiked by ~10*C. Now it does this.

I hate to break it to you, but software will be software you will see a lot of this kind of crap the more you use HWInfo. It's not that HWInfo is bad, but software is software

If you tortured it adequately with TM5 for long enough, then none of this will be problematic.

• The only reservation I have is that SPD Hub temp is not PMIC temp, and G.skill is notorious for having bad (read: none) PMIC cooling due to lacking a thermal pad. And because PMIC temp is not reported (from a quick survey of Google it looks like it's not usually possible to get an actual temp reading out of PMIC at a hardware level?), no one really knows how it's doing.
• On the other hand, you did stress it up to about 5W DIMM power, which is a good bit and ballpark for stock 1.35V. If PMIC was truly getting hot enough at idle to be responsible for the overtemp flag, then I would imagine it would have become a serious problem under stability testing.
• And there are SFF builders that pay no heed to DDR5 cooling and hotbox their G.skill sticks up to reading north of 80C SPD Hub. And they're still fine. So you should be fine.

So, still nothing changed - seems to be nothing to worry about. I'd lean towards blaming the board, honestly. And seeing as it's not affecting stability, probably just a board quirk.

35C still seems slightly on the warm side for idle, but I also don't know how your PC cooling is set up and how warm your place is. My numbers at idle are sub-30 just like @freeagent 's

 

[Svedski]

View attachment 393236

I hate to break it to you, but software will be software you will see a lot of this kind of crap the more you use HWInfo. It's not that HWInfo is bad, but software is software

If you tortured it adequately with TM5 for long enough, then none of this will be problematic.

• The only reservation I have is that SPD Hub temp is not PMIC temp, and G.skill is notorious for having bad (read: none) PMIC cooling due to lacking a thermal pad. And because PMIC temp is not reported (from a quick survey of Google it looks like it's not usually possible to get an actual temp reading out of PMIC at a hardware level?), no one really knows how it's doing.
• On the other hand, you did stress it up to about 5W DIMM power, which is a good bit and ballpark for stock 1.35V. If PMIC was truly getting hot enough at idle to be responsible for the overtemp flag, then I would imagine it would have become a serious problem under stability testing.
• And there are SFF builders that pay no heed to DDR5 cooling and hotbox their G.skill sticks up to reading north of 80C SPD Hub. And they're still fine. So you should be fine.

So, still nothing changed - seems to be nothing to worry about. I'd lean towards blaming the board, honestly. And seeing as it's not affecting stability, probably just a board quirk.

35C still seems slightly on the warm side for idle, but I also don't know how your PC cooling is set up and how warm your place is. My numbers at idle are sub-30 just like @freeagent 's

Open case, it's 22*C most days here. There is an INTAKE CPU fan and an EXHAUST CPU fan on the CPU cooler itself blowing air next to it through the CPU cooler.

This board, and the board before it (both X670E boards from ASUS and this one from MSI) have had coil whine around the CPU that suddenly appeared. It's been worrying me. The coil whine only appears in Windows, and it's at it's worst when idle. Putting load on the PC quiets it down.

not my vid, but this is what I hear, it's most apparent when listening at the back of the case (where the CPU socket is, behind the motherboard). Again, PC seems to work fine, but this, in combination with the (now I assume false) readings makes me nervous for this whole setup.

 

[tabascosauz]

Open case, it's 22*C most days here. There is an INTAKE CPU fan and an EXHAUST CPU fan on the CPU cooler itself blowing air next to it through the CPU cooler.

This board, and the board before it (both X670E boards from ASUS and this one from MSI) have had coil whine around the CPU that suddenly appeared. It's been worrying me. The coil whine only appears in Windows, and it's at it's worst when idle. Putting load on the PC quiets it down.

not my vid, but this is what I hear, it's most apparent when listening at the back of the case (where the CPU socket is, behind the motherboard). Again, PC seems to work fine, but this, in combination with the (now I assume false) readings makes me nervous for this whole setup.

I think it's really apparent now that you just worry too much coil whine is a fact of life, sounds like you drew the short straw with this board unfortunately