AMD Ryzen 5000 Builders Thread

[Det0x]

My 5600x rig has the 3200 CL14 G.Skill 16GB kit.

3866/1933 1.5v's currently CL16 1t GDM disabled with zero WHEA errors so far. Haven't tightened all the timings yet, but it does look promising so far. I'm treading cautiously on timing. If I can get CL16 good to go I'm shooting for CL15 next.

Can you do a maxxmem2 run when you have finalized the timings ?

MaxxPI² - MaxxMem² - Download

System Bench, MaxxPi, Maxxmem, Memory Benchmark

maxxpi2.de

 

[Kenmitch]

Can you do a maxxmem2 run when you have finalized the timings ?

MaxxPI² - MaxxMem² - Download

System Bench, MaxxPi, Maxxmem, Memory Benchmark

maxxpi2.de

I'm still toying around with some timings. This is as far as I've gotten so far without generating any bsods or WHEA errors. I did manage 1 bsod and generated a few WHEA errors when dropping the CL without bumping the dram voltage up.

Using 1.54v's currently on the dram.

 

[CakeMonster]

Thanks everyone for testing out these settings making it a lot easier for the rest of us to set up our systems with probably less problematic OC settings when we finally get our stuff and BIOSes will be a lot more mature

 

[repoman0]

Thanks everyone for testing out these settings making it a lot easier for the rest of us to set up our systems with probably less problematic OC settings when we finally get our stuff and BIOSes will be a lot more mature

No problem it’s fun. I’ve never bought hardware this early in its lifecycle. Fun to mess around with and discover things. I’d probably find it a lot less fun if I actually used my PC for anything important, but it’s basically an overpriced gaming box. I use a laptop for actual work and remote in to a >5 Pflop supercomputer for anything important

 

[repoman0]

Well, with your voltages and the 1.1.9.0 beta BIOS, with otherwise the exact same settings that I had before, I was able to go through my "guaranteed WHEA BSOD" sequence of events without an error. So maybe AMD has done something there. I know in the changelog for 1.1.9.0 there is something about improving stability in the Fclk 1800-2000 MHz range. Going to just use the system for a while to see if it's stable, then work on reducing voltages and tightening RAM timings.

I can't help but keep messing with things. So far so good on 1.1.9.0 with settings below .. this would have been completely unstable on the previous 1.1.8.0 BIOS. Reduced voltages a bit, along with Vdimm to back down to stock 1.35. It's nothing crazy compared to others here but not bad for a $110 32GB kit bought a couple years ago, and gets 62ns in Aida64.

 

[Noid]

Gold standard P95 test completed @ Cas16 on boost mode
( 12+hrs - I fell asleep )
attached Buggy BIOS screenshots
( incase MSI is reading )

Missing BIOS sensor values

 

[Noid]

IF2000 !!!

I had no WHEA errors until I ran AIDA. ( 202 errors )

Hard reset occurred using the handbrake benchmark ...
( no BSOD's )
Upped the DDR from 1.45 to 1.5
( NO reset or BSOD )

Benchmarks:
Final Fantasy lost 1000 points. ( 7600 to 6700 )
HB benchmark ( here ) sky rockets to 215 seconds !
( from 170 @ boost )
CB23 lost 2000 --- 22,000 to 20,000 Multi core

No need to run any more tests ...
.... my chip is bottlenecked at IF2000.

I did notice the WHEA errors only occurring in HEAVY load.
( IF1933 produced them at load also )

Loaded IF2000 from the MSI " Memory Try It ! " BIOS item
( In my NoValues BIOS screenshot above )
( No POST manually setting IF2000 )

And, as I just found out the hard way ...
if your BIOS does not offer an IF1966 preset option ...
... then don't try it ...

I experienced BIOS checksum error an BIOS freeze and BIOS screen corruption at IF1966 trying to manually load it ...
CMOS reset required.

Back to testing IF1933 again ...

Remember ... my BIOS is Beta 1.1.9.0

 

[Justinus]

I've got my asymmetrical config memtesting right now.

2x16GB Trident Z RGB 4000CL16 + 2x8 Trident Z 3600CL15, set to 3800 14-16-16-32-1T 1:1

Strangely my memory controller appears to have no trouble running triple rank, but these 3600CL15 DIMMs have some weak IC's, while tweaking timings I was constantly getting memtest errors in the same address space and always of the exact same kind (x8xxxxxx actual, xxxxxxxx desired), always seeming to be flipping that one bit.

I guess my old 3600CL15 aren't binned as well as I'd hoped.

I wonder if triple rank gets even more yield in gaming?

 

[Noid]

MSI x570/b550 work around for WHEA and BIOS updates

2021/01/12 --> MSI starts to release AGESA ComboAM4PIV2 1.2.0.0 BIOS

I have never messed with CPU voltage offsets
They say it's a workaround for the WHEA error 18
Error 19 --- drop the IF

 

[Justinus]

MSI x570/b550 work around for WHEA and BIOS updates

2021/01/12 --> MSI starts to release AGESA ComboAM4PIV2 1.2.0.0 BIOS

I have never messed with CPU voltage offsets
They say it's a workaround for the WHEA errors
I'm going to try

I suppose I'd have to check and see if the errors I get are 18 or 19.

 

[Noid]

yea ... mine are 19
( opps )

IF1933 ----- has more headroom for me
IF1966 ----> scary BIOS corruption --- unknown if more headroom
IF2000 ----- bottlenecked

I have not giving up looking for a fix ( myself )
Headroom to be had !!!

 

[samboy]

I finally have my 5950x build......... I simply swapped the 3900x for the 5950x in an Asus ROG x570e motherboard (using latest 3202 BIOS......ok, just checked and looks like they have a new 3404 BIOS today!).

Used same memory settings 3600 16-19-16-16-36-73 (Micron-E ram) and everything seems stable

Will do some more stability testing over the weekend.

 

[Noid]

I looked up the GUID on my Error 19
{c26c4f3c-3f66-4e99-8f8a-39405cfed220}
Bluetooth is failing ?

I turned off bluetooth.
Went into BIOS to integrated peripherals and Disabled WiFi

My errors dropped in half ...
( running Aida = 200+ errors before ,,,,, --- > now 105 )

 

[Kenmitch]

I looked up the GUID on my Error 19
{c26c4f3c-3f66-4e99-8f8a-39405cfed220}
Bluetooth is failing ?

I turned off bluetooth.
Went into BIOS to integrated peripherals and Disabled WiFi

My errors dropped in half ...
( running Aida = 200+ errors before ,,,,, --- > now 105 )

What clocks are your running?

I'm running my b-die at 3866/1933 and the only thing that will generate the WHEA 19 is Aida64 stress test. Memory passes stability test, system is stable, no bsods or funny behavior etc. I'm still experimenting with settings. My errors are few and far between luckily so I'm thinking I can whip it in the end. In the past trying for 1900 FCLK or higher Aida64's memory copy benchmark would trigger dozens of them instantly.

 

[Noid]

Working on IF1933
( IF1900 is error free )
Yes, errors only under HEAVY load for my system.
DISABLING WiFi in BIOS cut these in half.
Disabling Bluetooth and WiFi services did nothing.
All my services are back on.
Left WiFi in BIOS off for now.
And, I'm still investigating ...

 

[thesmokingman]

I'm wondering it patch C will let me use Cas19 .... bbl with results

You cannot run odd CAS numbers w/o disabling gdm and power down.

 

[Kenmitch]

Working on IF1933
( IF1900 is error free )
Yes, errors only under HEAVY load for my system.
DISABLING WiFi in BIOS cut these in half.
Disabling Bluetooth and WiFi services did nothing.
All my services are back on.
Left WiFi in BIOS off for now.
And, I'm still investigating ...

I saw that same {c26c4f3c-3f66-4e99-8f8a-39405cfed220} in my WHEA 19's and googled it, but I don't even have Bluetooth so I'm not sure it leads anywhere in the end.

If I leave Aida64's stress test alone and do nothing I don't even get errors. When I let it run and surf the web and do other things it'll generate a few errors.

 

[Justinus]

All my whea errors are 20. No idea what that means.

 

[repoman0]

Anyone have any technical details on how exactly these WHEA errors are detected and corrected? There must be some internal ECC functionality within the CPU that can report to Windows? I still have never seen a correctable WHEA error on my system, just the blue screens on 1.1.8.0 that have cleared up.

 

[thesmokingman]

Anyone have any technical details on how exactly these WHEA errors are detected and corrected? There must be some internal ECC functionality within the CPU that can report to Windows? I still have never seen a correctable WHEA error on my system, just the blue screens on 1.1.8.0 that have cleared up.

Use hwinfo. At the bottom of the sensors window there's a whea tracker. Set hwinfo to display that stat on the taskbar, and voila you'll know instantly when you get a whea error. They can't be corrected afaik just detected and can lead to data corruption etc. There's also different kinds of whea errors, like some early Ryzen 5k bios' were very susceptible to errors.

 

[Noid]

repoman , Windows writes WHEA errors to the Event Viewer
Windows Logs --- > System.
They are flagged yellow warning.
Specific error info ----> Details Tab

I'm an old DOS 3.0 programmer.
Hardware exceptions were captured at the Assembler level code.
( In my old days ... )
I used to create/modify/call assembler level API's to perform machine level functions.
( manipulating memory/data ... writing to disk .. etc .. )
Linkage used to call the API's retrieve/capture any error codes produced and pass them though the linkage.

Things are more complicated now ... I have no idea ...

 

[Noid]

What ratios are being offered in your BIOS ?
Do they POST ?
Been trying to over-ride the 1/2 ratio
( like in my BIOS memory presets - attachment )
None of them POST.
( 4000 / 1800 = 2.22 ratio )
Tried to fool the BIOS to 4000 / 1900 using the presets.
Unsuccessful.

I can manually set DDR4000 at IF1900 and POST but
the 1/2 over-ride takes over ( IF 1000 - as usual )

 

[Justinus]

What ratios are being offered in your BIOS ?
Do they POST ?
Been trying to over-ride the 1/2 ratio
( like in my BIOS memory presets - attachment )
None of them POST.
( 4000 / 1800 = 2.22 ratio )
Tried to fool the BIOS to 4000 / 1900 using the presets.
Unsuccessful.

I can manually set DDR4000 at IF1900 and POST but
the 1/2 over-ride takes over ( IF 1000 - as usual )

That's weird. I'm on an ASUS board but I can set whatever FCLK and memory speed I want and it posts and runs at them fine (within reason, of course). I have no issue setting 4000 mem and 1900 FCLK.

Of course it tanks memory latency, but that's to be expected.

 

[Noid]

Can you add a CPUZ screenshot of DDR4000 at IF1900 ?
( memory tab )
DRAM Frequency 2000 ?
Uncore Frequency ~1900 ?

I also can set these --- but they do not " stick ".

 

[Justinus]

Can you add a CPUZ screenshot of DDR4000 at IF1900 ?
( memory tab )
DRAM Frequency 2000 ?
Uncore Frequency ~1900 ?

I also can set these --- but they do not " stick ".

I would, but it sure don't like 4000 memory with 3 ranks per channel lol! Lemme take out some dimms.