WHEA id 19 errors (Error Type: Bus/Interconnect Error) - Is it any good to ignore those ?

[Catz111]

I recently found out that i have a tons of WHEA 19 errors. So far i found out that it is related to overclocking settings maybe Infinity fabric settings or voltage. But for sure related to overclocking and voltage settings.
I have ddr 4 with 4000 mhz which is the only component that can be counted as "overclocked" because i use the XMP profile. And there is 1 issue with it as well. I have some Acer Predator samsung B-die ram and it has
latency of 17-17-17-37 but i had to switch to some "gear mode" if i remember correctly was like 1 year ago for more stability or something along those lines can't remember. But what i remember is that gear mode and the infinity fabric of 2000mhz on a ryzen 5000 series CPU made my timings (or it gave me a message that it has to make the first timing an "even" number to properly work lol ) So it changed the timings slightly from 17-17-17-37 to 18-17-17-37...

Now my question is - can this be the cause of my WHEA errors ?

 

[tabascosauz]

I recently found out that i have a tons of WHEA 19 errors. So far i found out that it is related to overclocking settings maybe Infinity fabric settings or voltage. But for sure related to overclocking and voltage settings.
I have ddr 4 with 4000 mhz which is the only component that can be counted as "overclocked" because i use the XMP profile. And there is 1 issue with it as well. I have some Acer Predator samsung B-die ram and it has
latency of 17-17-17-37 but i had to switch to some "gear mode" if i remember correctly was like 1 year ago for more stability or something along those lines can't remember. But what i remember is that gear mode and the infinity fabric of 2000mhz on a ryzen 5000 series CPU made my timings (or it gave me a message that it has to make the first timing an "even" number to properly work lol ) So it changed the timings slightly from 17-17-17-37 to 18-17-17-37...

Now my question is - can this be the cause of my WHEA errors ?

Your timings don't have much to do with it. Geardown can only work with even numbered tCL, so 17-17-17 automatically becomes 18-17-17.

WHEA 19 bus/interconnect is just classic Fabric instability. Either:

• Your 5600X sample cannot do 2000 stable at your given VSOC
• Your 5600X sample cannot do 2000 stable at your given combination of VDDG_CCD and VDDG_IOD (primarily the latter)
• Your 5600X sample cannot do 2000 stable, period

VSOC is already relatively high - can't tell if that is 1.18V set, or already 1.2V set with normal levels of droop. If it's 1.2V I wouldn't go higher for daily usage. Try to bring your VDDG_IOD up to about 1.10V or maybe even up to 1.15V to see if it makes a difference.

 

[Catz111]

Damn if the infinity fabric do not work i acctually run this around 1 year non stop on 2000mhz and so far i had very few pc crashes if i would guess it must be around 7-8 crashes in 1 year. It happens really rare that the pc just restart without any Bluescreen.

The really wierd thing like from the OCCT tool above is that the vcore is shown as 1.39 when im in idle but when i press Start on the OCCT stress test then this voltage drops to around between 1.01-and 1.2 is this normal ? I acctually activated recently PBO to negative 5 or 10 not sure and in idle it is around 1.25-1.3 and when i start it it drop between 1.01 and 1.2

And about the VSOC i think all those are set to auto.. I awso deactivated the PBO but it still gave me the WHEA errors. Should i go check the VSOC as you mentioned and VDDG_IOD settings ?

I have an Aorus Pro v2 b550 motherboard and as far as i know with the bios i had at that time it should be able to manage to do the 2000mhz infinity fabric. I guess its time to check those VSOC and VDDG_IOD settings you mentioned.

 

[Athlonite]

Just down clock it to 1966MHz and they'll go away and yes it's not good to ignore those errors eventually you'll end up with an unbootable system because of file corruption I've had the same issue with my 5800X trying to get it running 1:1 at 4000MT/s and I found down clocking my ram to 1966MHz worked perfectly fine and didn't really lose any noticeable perf

 

[Catz111]

Hey guys do you see anything out of order on this video of my voltage settings ?

bandicam 2023-08-17 00-53-12-272

Watch "bandicam 2023-08-17 00-53-12-272" on Streamable.

streamable.com

"Just down clock it to 1966MHz and they'll go away and yes it's not good to ignore those errors eventually you'll end up with an unbootable system because of file corruption"

Should i first not try with the voltage settings from the post above ?

 

[tabascosauz]

Damn if the infinity fabric do not work i acctually run this around 1 year non stop on 2000mhz and so far i had very few pc crashes if i would guess it must be around 7-8 crashes in 1 year. It happens really rare that the pc just restart without any Bluescreen.

The really wierd thing like from the OCCT tool above is that the vcore is shown as 1.39 when im in idle but when i press Start on the OCCT stress test then this voltage drops to around between 1.01-and 1.2 is this normal ? I acctually activated recently PBO to negative 5 or 10 not sure and in idle it is around 1.25-1.3 and when i start it it drop between 1.01 and 1.2

And about the VSOC i think all those are set to auto.. I awso deactivated the PBO but it still gave me the WHEA errors. Should i go check the VSOC as you mentioned and VDDG_IOD settings ?

I have an Aorus Pro v2 b550 motherboard and as far as i know with the bios i had at that time it should be able to manage to do the 2000mhz infinity fabric. I guess its time to check those VSOC and VDDG_IOD settings you mentioned.

The board doesn't really care. 6-layer boards like Aorus Pro can do upwards of 4000 dual rank. It's your individual CPU sample that matters.

Vcore is irrelevant to this, and that's how it's supposed to work. PBO is also irrelevant, those are CCD side things.

VSOC alone usually isn't enough at higher Fabric speeds. I'd say VDDG_IOD is the next most important thing. It can go as high as 0.04-0.05V below your set VSOC. If you haven't touched VDDG_IOD, you never know, maybe you don't even need that much VSOC.

Fabric instability usually has to be VERY unstable in order to crash/reboot or BSOD (even rarer). Frankly, it's up to you what you want to do. It sounds like being unstable isn't a huge impediment to your daily use. Lots of 2CCD owners (5900X/5950X) resorted to just disabling WHEA reporting service once they felt their CPU was "stable enough" at 2000MHz, since 2CCD has a much harder time with high Fabric speed. If you are getting crashes I wouldn't consider that "stable enough", but it's up to you.

If upping IOD doesn't make a difference, I would come down to 3800 or 3866, maybe run tighter timings on what presumably is B-die you have (?), and call it a day.

 

[Catz111]

If you are getting crashes I wouldn't consider that "stable enough" - Thats exactly what im thinking as well i was wondering even if i had rarely a crash what this is but i never dig too far till i found that i had the WHEA errors.

So lets get some easy step by step what to do best to solve this. So far there was the post above to lower the Infinity fabric to 1966mhz from

Athlonite​

And you mentioned to try to set the VDDG_IOD little below the VSOC... Question is my VSOC not set little too high if you check my video with the voltages ? Or do you see any other anomaly i might have there ?

bandicam 2023-08-17 00-53-12-272

Watch "bandicam 2023-08-17 00-53-12-272" on Streamable.

streamable.com

In the end i wish the CPU to be awso energy efficient so it would be nice if i could lower the VSOC if i do not need it to be that high well thats just some extra how i would like to run the cpu long term if that is possible with this high infinity fabric anyway. Priority tough should be to solve the WHEA errors so where do i start best with the VDDG_IOD or maybe even the VSOC as well if thats little too high ?

 

[tabascosauz]

And you mentioned to try to set the VDDG_IOD little below the VSOC... Question is my VSOC not set little too high if you check my video with the voltages ? Or do you see any other anomaly i might have there ?

No? SOC Voltage is SOC Voltage, Core voltage is Vcore. 1.2V VSOC is high but not alarmingly high - unless you have a golden sample CPU you will need to pump SOC to sustain high Fabric at 2000 or higher. I just wouldn't go above 1.2V.

Get your VDDG_IOD done first. Try 1.10-1.15V.

If you don't actually care about 2000 that much, then just lower speeds. If you haven't dialed in the rest of your timings (seems like you might not be interested in spending all that time anyway), then just being at 2000 IF for CL18 doesn't accomplish all that much, it's not that fast.

Your CPU probably only needs somewhere between 1.0-1.1V SOC for 1800-1900, so that should bring down your SOC power and package power a fair bit.

To check use https://zentimings.protonrom.com/

 

[Catz111]

"If you don't actually care about 2000 that much, then just lower speeds. If you haven't dialed in the rest of your timings (seems like you might not be interested in spending all that time anyway), then just being at 2000 IF for CL18 doesn't accomplish all that much, it's not that fast."

I was pretty dissapointed that my Samsung B-die ram downgrade the timing from 17-17-17 to 18-17-17 because of the gear mode thingy... I wish i could do something to that too lol but yeah i do care for 2000mhz and that sucks to hear that cl18 doesnt acomplish much but idk if cl 17 would be that much better either ? i guess my samsung B-die ram can get better with overclocking maybe 16-16-16 but i do not want to mess with that tbh...


Ok im going to try now the VDDG_IOD do i start first with 1.10 or 1.15 ?

 

[tabascosauz]

"If you don't actually care about 2000 that much, then just lower speeds. If you haven't dialed in the rest of your timings (seems like you might not be interested in spending all that time anyway), then just being at 2000 IF for CL18 doesn't accomplish all that much, it's not that fast."

I was pretty dissapointed that my Samsung B-die ram downgrade the timing from 17-17-17 to 18-17-17 because of the gear mode thingy... I wish i could do something to that too lol but yeah i do care for 2000mhz and that sucks to hear that cl18 doesnt acomplish much but idk if cl 17 would be that much better either ? i guess my samsung B-die ram can get better with overclocking maybe 16-16-16 but i do not want to mess with that tbh...

Ok im going to try now the VDDG_IOD do i start first with 1.10 or 1.15 ?

It's not that it's CL18, it's that 2000 FCLK really doesn't make much of a practical difference over 1900............I might say it at least counts for some e-peen, if there weren't already plenty of 6- and 8-core owners hitting 2100+ daily stable.

B-die is by and large THE choice for practical tweaking; if you aren't willing to delve into that rabbit hole I can fully understand as it's a real time waster, but then there really is no reason to put such emphasis on 2000MHz Fabric when it's not really doing anything for you.

It doesn't matter which you go with, as long as it doesn't go higher than VSOC minus 50 millivolts.

 

[Catz111]

I'm going in boys wish me luck



EDIT: I don't have VDDG_IOD but i have only VDDG. It say something that VDDG should not exceed VDDG_SOC if i remember correctly damn.. but it say it is related to the infinity fabric and SOC

Just want to confirm that this is the right one yes ? As it seem all those settings are set to "auto"

Ok i just try again so after i set the VDDG from "auto" to "manual" 2 new settings appear VDDG CCD und VDDG IOD both have values set automaticly to 700.. Why 700 is this not way too high and i should go with 1.10 ? Should i awso set the VDDG CCD as well to 1.10 ? As both seem to appear togheter after i switch from auto to manual and they have a value of 700 which suggests that those are related somehow..

What do i do now ?


I found this about the high 700 numbers it seems that my MOBA is counting it in mili volt so 1100 mili volt should equal to the 1.10 that i have to set ?



And here the info with the VDDG IOD and VDDG CCD:


" I see a strange situation when I try to switch the VDDG voltage to manual with the aim of improving stability at high IF clocks 1900-2000+ MHz. I can change the VDDG CCD by inputting the voltage in mV and do the same for VDDG IOD. The problem is that while the BIOS take the values like 1000 for example, it actually only keeping/saves the VDDG IOD while switching back to 700 (mV) for the CCD. So, the manual voltage does not stick, and I discovered this the hard way as the board booted, but upon checking in the BIOS menu at AMD CBS I saw that it booted with 700mV for VDDG CCD !! and 1060V (as I input) for VDDG IOD and just as I saw the values it froze due to obviosly too low CCD voltage. Is there something I am missing, is this a BIOS bug potentially, can anyone advise?

Something similar also happens with CPU limits where the EDC reverts back to 0 no matter the number I try to put there. The TDC and PPK accept and save numbers just fine."







Guys i decided to just lower the infinity fabric for now... It seems it is the more easier way and i don't want to mess with the voltages right now but i may later at some point lol

The good news is that i just run the OCCT tool stress test (extreme) and it seems that it fixed all the WHEA errors

But i have found another problem.. The CPU seems to underperform. On Cinebench r23 i get around 9600 score where i should have around 11000 . And all core frequency boost to only around 3,8ghz and not 4,2 ghz as it should - What can i do about that and what is the issue that is causing this ?

Same thing happens with cinebench r20 i get a multi core test score of 3800 which equals exactly to a ryzen 3600xt but not 5600x which should be around 4400
Any tought or ideas why this is and those low 3,8 ghz all core frequency and not 4.2ghz ?

 

[Amber Shade]

Though this may look like necroposting, but: your CPU seems to be super power constrained, screenshots provided show it only ever consuming <80 watts of power - this is not what you're looking for to get high MT results. 5600X should be happy with 120-140 watts, though this might get it a little warm - try increasing it gradually, start with 95-105 and watch your temps. Your cooling solution seems adequate, give it a chance to shine

And regarding your settings not getting applied, I've only encountered a similar issue once and solved it with a bios reflash, Not something I would advise if you're not sure in what you're doing, even though it's not really that hard