AMD Ryzen memory support

[artur.aragao@outlook.com.br]

Esteemed,

I put it here on SOC Voltage 1.150v too. Let's see how it goes from now on. I'll give it a few days and then return. If this is the case, it could only be so. I have two tickets open with MSI and we could shed that light on them. I already shared this thread for them and another one from AMD.

 

[artur.aragao@outlook.com.br]

IS! It didn't work for me.
Looped.

I am getting a new font. I'm suspicious that it could be her. Wait!

 

[artur.aragao@outlook.com.br]

I'm taking another source.
I'm starting to suspect that it might be the source. When I hang up on her switcher, I can spend more time without the WHEA.

 

[artur.aragao@outlook.com.br]

Unfortunately SOC Voltage 1.150v did not work for me.
It seems to be something with the source itself.
I'm getting an XPG CORE REACTOR 850W.
Waiting to arrive.

 

[artur.aragao@outlook.com.br]

UPDATE:
DISREGARD. I TAKEN ANOTHER WHEA.

I'm still not really sure about that, but after I disabled the features marked in the image below, I no longer had WHEA. I was very suspicious of these resources that I always used in the configuration of the mainboard. That was the configuration that also made with the MSI X370 XPOWER GAMING TITANIUM.

I disabled it and the WHEA stopped. I was suspicious between this session and the ErP. The problem is very clear when the error occurs in a certain part of the system boot, preceding the entry and when the system enters an idle state. I remembered that I always activate these features and on the last attempt, I disabled it.

I cannot guarantee the solution yet. I need to do more tests. I would really like the staff to test it too. It may not fit in all situations.

 

[andre.ifg]

I'm still not really sure about that, but after I disabled the features marked in the image below, I no longer had WHEA. I was very suspicious of these resources that I always used in the configuration of the mainboard. That was the configuration that also made with the MSI X370 XPOWER GAMING TITANIUM.

I disabled it and the WHEA stopped. I was suspicious between this session and the ErP. The problem is very clear when the error occurs in a certain part of the system boot, preceding the entry and when the system enters an idle state. I remembered that I always activate these features and on the last attempt, I disabled it.

I cannot guarantee the solution yet. I need to do more tests. I would really like the staff to test it too. It may not fit in all situations.

View attachment 146009

Hello, how are you?

You can do a test with the voltages that I tested here and there was no more WHEA errors. If you can, take the test and see if the errors still persist:

CPU loadline Calibration Control: Mode 3

CPU NB Loadline Calibration control: Mode 5

VDDP Voltage: 1,100
VDDG CCD Voltage: 1,100
VDDG IOD Voltage: 1,100

SOC voltage: 1.150

If there are no errors, go down the voltages until you find the ideal point.

 

[artur.aragao@outlook.com.br]

Hello, how are you?

You can do a test with the voltages that I tested here and there was no more WHEA errors. If you can, take the test and see if the errors still persist:

CPU loadline Calibration Control: Mode 3

CPU NB Loadline Calibration control: Mode 5

VDDP Voltage: 1,100
VDDG CCD Voltage: 1,100
VDDG IOD Voltage: 1,100

SOC voltage: 1.150

If there are no errors, go down the voltages until you find the ideal point.

Andre,

I will test this solution further that I found. If something goes wrong, I use your solution.

From what I can say about what I remembered about the Setup Wake Up Configuration session, after I disabled the features shown in the image from the previous post, it is that my system has already entered about 10 times in disregard and the errors have not occurred. It's stable. I need to extend the tests for more days. In previous tests it never went beyond 3 or 4 attempts.

I also tested boot and showed excellent reliability, running the boot until entering the system.

 

[artur.aragao@outlook.com.br]

I am trying these parameters right now.
CPU loadline Calibration Control: Mode 3
CPU NB Loadline Calibration control: Mode 5
VDDP Voltage: 1,100
VDDG CCD Voltage: 1,100
VDDG IOD Voltage: 1,100
SOC voltage: 1.150

 

[artur.aragao@outlook.com.br]

All the attempts pointed out here were used and did not have different effects. I'm just waiting for the source to arrive to take my position on how much. This is ridiculous.

 

[artur.aragao@outlook.com.br]

Look!
MSI needs to URGENTLY improve the quality of the applications in the Dragon Center and stop messing around. I definitely discovered my problem. I already know how to force WHEA here and then I did it by elimination. He was a driver !!! Some driver that MSI inserts to further control the PC's sleep state. I have S2 / S3 / S5 enabled in the BIOS. S5 is a new state and already accepted by Windows 10. With Dragon Center, my computer is almost completely dormant. And this is where the WHEA problem occurs. Something is not working well with this on the DC and generates these errors. I removed the DC and everything returned to normal. I don't have this more advanced state of rest of the S5 that I considered to be VERY cool, but at least I have the reliable computer again.

Suggestion I give to friends. If you have a support app like Dragon Center on your mainboard, remove it. The most current version at least manages to completely uninstall itself. The most current version is 2.0.100.0. They need to review this urgently.

I'm out of control of the LEDs now.

I make the suggestion that I went through, as it may actually be a driver on your system that is causing these anomalies. In some cases the problem is located in the BIOS. I find WHEA disgusting because it generates a huge false positive for us, making it impossible for us to quickly find the problem. In summary, my Corsair RM-1000 font had no problems and I ended up buying another one without any need.

NOTE: The boot and the system are more agile without the Dragon Center.

Thank you MSI!

 

[artur.aragao@outlook.com.br]

Esteemed,

Final test carried out and the problem is in fact in the VGA RX5700 XT.

I tested the VGA on another computer and had the same problems. When I tried to leave only the standard driver downloaded from microsoft, it behaved a little better. However, when I tried to uninstall the standard driver, the PC crashed. I tried another 4 times in a row and the same bizarre crash behavior occurred. I put the MSI RX5700XT back on my PC and tried to do the same.

I took the RX5700XT from MSI and put in an ASRock RX550. Everything works normally, with Dragon Center included.

Apparently the problem is with the VGA in fact. After this exchange, everything normalized. WHEA-Logged ID: 18 events are over.
Requesting the MSI RX5700XT RMA.

 

[gungungu157702dc]

From B550 Tomahawk the memory compatibility support list:

But in fact, I can't boot with that xmp profiles. (My bios version is A.50 and CPU Ryzen5-3600)
Can you fix this?

 

[darkhawk]

From B550 Tomahawk the memory compatibility support list:View attachment 146341
But in fact, I can't boot with that xmp profiles. (My bios version is A.50 and CPU Ryzen5-3600)
Can you fix this?

You're not talking to MSI here. See : >>Please read and comply with the Forum Rules.<<

If you want to talk directly to MSI, see : >>How to contact MSI.<<

 

[prii151c02d4]

When will MSI join the proud crowd of ECC compatible motherboard manufacturers? And I don't mean "Supports ECC UDIMM memory (non-ECC mode)" but in actual ECC mode, like professional motherboard makers do?

 

[dom.l.curti155402df]

When will MSI join the proud crowd of ECC compatible motherboard manufacturers? And I don't mean "Supports ECC UDIMM memory (non-ECC mode)" but in actual ECC mode, like professional motherboard makers do?

Who says they don't?

 

[prii151c02d4]

Who says they don't?

Who says they do? MSI sure don't.

 

[Nichrome]

No one really uses ECC memory in consumer systems, makes no point. It sure is a good idea to have in a server though, or rather whole cluster of them..
Anyway, you should contact MSI to get an answer as it's not something anyone here would know what are their plans >>How to contact MSI.<<

 

[prii151c02d4]

No one really uses ECC memory in consumer systems, makes no point. It sure is a good idea to have in a server though, or rather whole cluster of them..

It's like saying no one really uses DDR5 or PCIe 4 in consumer systems, makes no point.

Not because noone would want to use it, but because it hasn't been available previously in consumer space. Because of intel artificial market segmentation and money grab (still isn't in intel world). Now it is available from AMD, if the motherboard manufacturers support it. Decent ones do.

 

[darkhawk]

It's like saying no one really uses DDR5 or PCIe 4 in consumer systems, makes no point.

Not because noone would want to use it, but because it hasn't been available previously in consumer space. Because of intel artificial market segmentation and money grab (still isn't in intel world). Now it is available from AMD, if the motherboard manufacturers support it. Decent ones do.

Last warning. See : >>Please read and comply with the Forum Rules.<<

Don't like it, go elsewhere. You've made your point. Complaining here does nothing. No one here cares, much less can do anything about it. If you want to actually complain to someone that can, go talk to MSI directly : >>How to contact MSI.<<

We're all users here anyway.....so this whole discussion is meaningless.

 

[patazzmusi153402d0]

Is there a source for compatibility that intersects with MB, memory, and processor? MSI's compatibility to MB vs. Memory and MB vs Proc, but I don't see any way to find all three.

Specifically, I'm looking to find the sweet spot for memory on a B450-A Pro MAX with a Ryzen 5 2600 processor. Other specs in my signature. Right now my DRAM will only run at 2133, and I've tried XMP and manually changing the frequency, but all it does is fail to boot and require me to reset the BIOS (remove the battery, wait, and then start over). If I can get my 3200 dram to get above 2133 then I'll probably just add another 16 GB of DRAM and call it good. Otherwise I will likely buy something beefier from the official compatibility list.