Ryzen 5000 WHEAs

[Ecostrider]

Does anyone have a fix for this? I just built my PC (5600x, Gigabyte Aorus X570 Elite, G.skill ripjaws 3600-CL16-19-19-39) and am having the same issue. All I did was enable xmp and change dram voltage to 1.35. My system seems stable and according to ryzen master the IF is running at 1800mhz.
Sorry for the potential noob question but this is my first build and I am still learning all the terms and what everything does. I still don't really understand what RAM timings are and what the IF does. I just want the WHEAs to go away.

 

[Snakedog]

I also get constant WHEAs with 5600x, MSI Mortar b550m, G.skill ripjaws 3600-CL16-19-19-39 running with xmp. I didn't manually change the voltage or anything. It seems stable with Prime95 and gaming, so maybe I'll just ignore the warnings for now and try the next bios release.
It sounds like bios updates are starting to fix it for people, but it's not yet released for my motherboard. Reddit thread on this.

 

[biffzinker]

what the IF does.

Infinity Fabric is a high bandwidth connection between two or more components. For Ryzen it allows the core die a high speed connection too the I/O die where the memory controller is located.

 

[Mussels]

5800x here, at stock (2x32GB @ 3600 XMP) i get no WHEA errors. Two of my ram slots wont boot past 3200 - have you guys tried different RAM slots yet?

This does sound like zen 2 and needing the new AGESA

 

[ratirt]

5800x here, at stock (2x32GB @ 3600 XMP) i get no WHEA errors. Two of my ram slots wont boot past 3200 - have you guys tried different RAM slots yet?

This does sound like zen 2 and needing the new AGESA

I got the same problem. Just added 2 modules and 3600Mhz go bye bye. Maybe future Bios updates will fix that.

 

[Snakedog]

Installing the latest beta bios for my b550m mortar solved the problem - no more WHEAs. However, my 5600x doesn't reach the same boost with XMP on. If I run Prime95 without XMP (default Ram speed 2400 MHz or something) the cpu is steady at ~4.5 GHz, but if I have XMP on (3600 MHz) the cpu is only at ~4.3 Ghz. Cinebench R23 multithread is down from 11117 without XMP to 10707 with XMP. What's going on?

 

[MrKr4bS]

Installing the latest beta bios for my b550m mortar solved the problem - no more WHEAs. However, my 5600x doesn't reach the same boost with XMP on. If I run Prime95 without XMP (default Ram speed 2400 MHz or something) the cpu is steady at ~4.5 GHz, but if I have XMP on (3600 MHz) the cpu is only at ~4.3 Ghz. Cinebench R23 multithread is down from 11117 without XMP to 10707 with XMP. What's going on?

Higher ram speed needs higher infinity fabric and so maybe more power draw. Then you have less power for the rest left.
Try enabling pbo.

 

[NoJuan999]

MSI tends to release BIOS versions quickly, BUT they do tend to be pretty buggy.
I'm sure that in time they will work out the bugs.
So, you guys will just have to be patient.

Remember, this is a New CPU series and there is a learning curve for BIOS development.

Windows Event Viewer Error (Even System Restart)
Note. This should relate to individual AMD CPU but not motherboard
Symptom: When FCLK is higher, system is more likely to receive WHEA Logger error and sometimes can end up with BSOD and reboot.
Workaround: Lower FCLK for now and wait for future BIOS update
MSI board
Gigabyte board
ASUS board

Solution: No ETA

AMD ZEN3 5000 Series on X570 ACE/UNIFY/CREATION FCLK max out at 1600 (RAM Frequency: 3200Mhz) problem Update
Workaround: Update to latest beta BIOS on MSI website
Beta BIOS allows FCLK to go up to 1900, higher depends on CPU quality
If your FCLK can reach 1900 before updating beta BIOS, there is no need to update BIOS

From the MSI support Forum - (1) MSI X570/B550 Beta BIOS Update & Bug Status | MSI Global English Forum - Index

 

[jesdals]

Got my 5950x today, no WHEAs yet - but on the Gigabyte Aorus Master x570 I am hitting a 1900MHz Infinity sealing

 

[Space Lynx]

haven't had a single whea error on my x570 tomahawk and 5600x.

 

[Caring1]

Then you have less power for the rest left.

WUT!!

 

[thunk_stuff]

Hi all, I was running into the same constant WHEA bluescreens (Bus/Interconnection errors) after upgrading to 5900X and found my way here. The only way I could keep system stable was turning PBO off. With PBO on, Windows would crash within a minute of start up.

I've stumbled on a fix that so far I've gone an hour now and have not gotten bluescreens or WHEA mentions in event log. It's allowed me to enable XMP at 3600Mhz and leave PBO on. I've done a lot of benchmarks and stress tests on all core and single core, along with idle and low usage (web browsing). So far so good. Crossing fingers.

FIX: I went into the PBO curve optimizer of the BIOS and set the voltage magnitude adjustment for all cores to positive 6.

I chose 6 for the magnitude adjustment in the curve optimizer by chance and it happens to be the one working so far. I did try a negative 6 (under voltage) and it immediately gave a WHEA error.

Specs:

• ASRock B550 Phantom Gaming ITX/ax
• G.SKILL Ripjaws V Series 32GB (2 x 16GB)
• Ryzen 5900X
• Corsair SF750
• 1.71 Beta BIOS. Latest AMD chipset drivers. (Not sure if curve adjustment is available in 1.61)

Will update if my luck goes south.

 

[MrKr4bS]

Hi all, I was running into the same constant WHEA bluescreens (Bus/Interconnection errors) after upgrading to 5900X and found my way here. The only way I could keep system stable was turning PBO off. With PBO on, Windows would crash within a minute of start up.

I've stumbled on a fix that so far I've gone an hour now and have not gotten bluescreens or WHEA mentions in event log. It's allowed me to enable XMP at 3600Mhz and leave PBO on. I've done a lot of benchmarks and stress tests on all core and single core, along with idle and low usage (web browsing). So far so good. Crossing fingers.

FIX: I went into the PBO curve optimizer of the BIOS and set the voltage magnitude adjustment for all cores to positive 6.

I chose 6 for the magnitude adjustment in the curve optimizer by chance and it happens to be the one working so far. I did try a negative 6 (under voltage) and it immediately gave a WHEA error.

Specs:

• ASRock B550 Phantom Gaming ITX/ax
• G.SKILL Ripjaws V Series 32GB (2 x 16GB)
• Ryzen 5900X
• Corsair SF750
• 1.71 Beta BIOS. Latest AMD chipset drivers. (Not sure if curve adjustment is available in 1.61)

Will update if my luck goes south.

Wich agesa version are you using? Don't have a curve optimizer...

 

[Mussels]

Wich agesa version are you using? Don't have a curve optimizer...

curve is hidden away on my board, at least for asus it was the second patch C bios that included it

 

[MrKr4bS]

curve is hidden away on my board, at least for asus it was the second patch C bios that included it

I found it. But i can input values from 0 to 9999 what is the unit of measure?????

 

[thunk_stuff]

I haven't found anyone who says exactly what the unit is, but you can see how tweaking it affects voltage:

Ryzen 9 5950X Curve Optimizer to 5.1 GHz, PBO and...

www.overclock.net

It's not exactly a perfect match, but setting to -15 lowered mV by -25. So it seems like just mV offset?

I did not try setting a higher PBO voltage offset to see if that would have brought stability to my system as an alternative to setting the all core curve magnitude to a positive value like 6.

Computer has been stable last 12 hours.

 

[R0H1T]

I found it. But i can input values from 0 to 9999 what is the unit of measure?????

That probably varies from one board manufacturer to another. What options are you seeing in BIOS, there should be some info or tip available there?

 

[MrKr4bS]

That probably varies from one board manufacturer to another. What options are you seeing in BIOS, there should be some info or tip available there?

 

[R0H1T]

Looks like the value should set the curve to be more aggressive, with a higher value.

 

[MrKr4bS]

Looks like the value should set the curve to be more aggressive, with a higher value.

Yeah but should I set 1 or 10 or 10000…?

 

[R0H1T]

Try with a lower value then make your way up. I'll go with 10~100 first, given it goes till 9999 even a triple digit value should be fairly safe.

 

[MrKr4bS]

Try with a lower value then make your way up. I'll go with 10~100 first, given it goes till 9999 even a triple digit value should be fairly safe.

I don't know... I probably will wait for msi to implement this in their oc menu with the next bios version....

 

[Mussels]

I used -10 and got crashes at idle, now i'm stable at -8

 

[MrKr4bS]

I now found something.

 

[Deleted member 193596]

i found out that disabling global C States fixed every issue for me (so far.. it has been around 36 hours now since the last crash)