• Guest, The rules for the P & N subforum have been updated to prohibit "ad hominem" or personal attacks against other posters. See the full details in the post "Politics and News Rules & Guidelines."

AMD Ryzen 5000 Builders Thread

Page 30 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

repoman0

Diamond Member
Jun 17, 2010
3,548
1,911
136
I have never seen a WHEA error appear in the HWInfo count, but I have been trying to fix occasional WHEA uncorrectable error BSODs at IF/DRAM 3600 MHz. Weird that I only get uncorrectable system crash ones and many people get regular countable ones. I’ve run memtest86 and memtest for windows for many hours with no errors so not entirely sure what the problem is.
 

Kenmitch

Diamond Member
Oct 10, 1999
8,502
2,244
136
The worst part is I can post, enter windows, run memtest86 etc. It's just I get CPU bus/interconnect errors fairly quickly and occasionally a memtest86 error.
Same here. I updated my 5600x rigs uEFI this AM to give it another whirl.

The normal 3600/1800 boots right up and allowed me to input my previous stable CL14 clocks without any stability issues.

I can't boot 1900 FCLK. Tried multiple times, but eventually gave up.

I can boot 2000 FCLK those WHEA warning errors instantly pop up

After scratching my head I tried 1933 FCLK just to see and it booted right up. I haven't tried tweaking it yet, but no instant WHEA errors or any WHEA errors yet. 3866MHz with some really loose timings CL18 which isn't going to fly with me. I'm going to go back in a tweak the settings slowly to see how she goes.

Memory tweaking requirement for me at least
Spare power switch connected to the cmos jumper as mine lies beneath my 6800
Batch file to clear the event viewer....I know it's best to not clear them, but I tweak my rig then just reload windows once it's stable and to my liking.
 
  • Like
Reactions: Tlh97 and Elfear

Justinus

Platinum Member
Oct 10, 2005
2,701
821
136
Same here. I updated my 5600x rigs uEFI this AM to give it another whirl.

The normal 3600/1800 boots right up and allowed me to input my previous stable CL14 clocks without any stability issues.

I can't boot 1900 FCLK. Tried multiple times, but eventually gave up.

I can boot 2000 FCLK those WHEA warning errors instantly pop up

After scratching my head I tried 1933 FCLK just to see and it booted right up. I haven't tried tweaking it yet, but no instant WHEA errors or any WHEA errors yet. 3866MHz with some really loose timings CL18 which isn't going to fly with me. I'm going to go back in a tweak the settings slowly to see how she goes.

Memory tweaking requirement for me at least
Spare power switch connected to the cmos jumper as mine lies beneath my 6800
Batch file to clear the event viewer....I know it's best to not clear them, but I tweak my rig then just reload windows once it's stable and to my liking.
Right now I have 3800/1900 CL16 (fairly tight timings) stable. I can post 1933, 1966, 2000, and 2033 FCLK with little to no hassle, but on all of them I get the CPU interconnect/bus errors. I've tried dozens of different voltage configurations with no success.

I'd rather get 4000CL16 than 3800CL16 as for some reason, I can't get my ram anywhere near stable at CL14. Maybe because it's dual rank dimms, maybe because I just haven't tried hard enough yet - not sure.

The ram is fully stable at 4000CL16 (same timings) though, I've tested it with async FCLK of 1900.

At this point I'm just playing with tossing in my kit of 2x8 b-die single rank for 3 rank/channel and seeing if it will go at all the same settings I've already got stable. At least I can get 48GB of reasonably fast ram, in that case.
 

Justinus

Platinum Member
Oct 10, 2005
2,701
821
136
The site that I ordered from doesn't show X570, so I'm a bit worried. I guess I'll find out the hard way, as no one has it in stock. Thanks for your help!
If it's the "Dark Hero", it's X570. Additionally, if it's Crosshair VIII, it's X570.

There is only one Dark Hero. Batman.
 

Kenmitch

Diamond Member
Oct 10, 1999
8,502
2,244
136
At this point I'm just playing with tossing in my kit of 2x8 b-die single rank for 3 rank/channel and seeing if it will go at all the same settings I've already got stable. At least I can get 48GB of reasonably fast ram, in that case.
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.
 

repoman0

Diamond Member
Jun 17, 2010
3,548
1,911
136
Did you guys have to mess with other voltages like VDDG or VDDP to get these high FClks stable? I can’t even get 1800 MHz after messing with it a bunch. I have a sequence of events that will create a WHEA uncorrectable error BSOD every time:

1. start 10 threads of Memtest for windows each using 2000 MB
2. start overwatch game and leave character in the practice range
3. leave it alone for a while
4. at this point it will run forever with no errors or reboots, but will BSOD a few seconds after I exit the game and stop the RAM test

something about the IF / memory controller / RAM really doesn’t like being in the idle state

edit: forgot to mention that I tested out RAM at 3200 MHz with mismatched IF at 3600, and that had the same BSOD behavior (matched 3200 is fine) so I have narrowed it down to the Fclk
 

MrTeal

Diamond Member
Dec 7, 2003
3,116
786
136
Did you guys have to mess with other voltages like VDDG or VDDP to get these high FClks stable? I can’t even get 1800 MHz after messing with it a bunch. I have a sequence of events that will create a WHEA uncorrectable error BSOD every time:

1. start 10 threads of Memtest for windows each using 2000 MB
2. start overwatch game and leave character in the practice range
3. leave it alone for a while
4. at this point it will run forever with no errors or reboots, but will BSOD a few seconds after I exit the game and stop the RAM test

something about the IF / memory controller / RAM really doesn’t like being in the idle state

edit: forgot to mention that I tested out RAM at 3200 MHz with mismatched IF at 3600, and that had the same BSOD behavior (matched 3200 is fine) so I have narrowed it down to the Fclk
What are you running for voltages? Could it be an issue with your board overshooting the memory voltage when you go from full load to idle?
 

Justinus

Platinum Member
Oct 10, 2005
2,701
821
136
Did you guys have to mess with other voltages like VDDG or VDDP to get these high FClks stable? I can’t even get 1800 MHz after messing with it a bunch. I have a sequence of events that will create a WHEA uncorrectable error BSOD every time:

1. start 10 threads of Memtest for windows each using 2000 MB
2. start overwatch game and leave character in the practice range
3. leave it alone for a while
4. at this point it will run forever with no errors or reboots, but will BSOD a few seconds after I exit the game and stop the RAM test

something about the IF / memory controller / RAM really doesn’t like being in the idle state

edit: forgot to mention that I tested out RAM at 3200 MHz with mismatched IF at 3600, and that had the same BSOD behavior (matched 3200 is fine) so I have narrowed it down to the Fclk
My 3800/1900 CL16 stable setting is:
VDDSOC: 1.050
VDDG CCD: 0.950
VDDG IOD: 1.000
CLDO VDDP: 0.90

This is on a Dark Hero, tho.
 

repoman0

Diamond Member
Jun 17, 2010
3,548
1,911
136
What are you running for voltages? Could it be an issue with your board overshooting the memory voltage when you go from full load to idle?
I’ve tried many different voltages:

Vddr 1.35 - 1.45
Vsoc 1.0-1.1
Vddg 0.9-1.05
Vddp 0.7-1.0

with very little change. I did notice an option under AMD overclocking for SoC “OC” mode which disables power saving supposedly .. wonder if that would help considering problems always happen at idle or semi-idle states.
 

repoman0

Diamond Member
Jun 17, 2010
3,548
1,911
136
My 3800/1900 CL16 stable setting is:
VDDSOC: 1.050
VDDG CCD: 0.950
VDDG IOD: 1.000
CLDO VDDP: 0.90

This is on a Dark Hero, tho.
Thanks, I’ve tried settings very close to those with no luck. Maybe I’ll flash the 1.1.9.0 beta bios and see if that improves things.
 

Justinus

Platinum Member
Oct 10, 2005
2,701
821
136
Thanks, I’ve tried settings very close to those with no luck. Maybe I’ll flash the 1.1.9.0 beta bios and see if that improves things.
These have been stable for me on 1.1.8.0, 1.1.9.0, and now 1.2.0.0 with no change to overclockability or voltages, either improved or worsened.
 

Noid

Platinum Member
Sep 20, 2000
2,283
103
106
My chipset SOC is 1.2v ( always )
( not CPU SOC - I don't touch this )
My MB chipset fan isn't spinning - ( under 60C - default )
My beta 1.1.9.0 isn't pulling current values to the screen
( for the voltages you want above ---> more bugs
-- they are on Auto )
My timings are at 16-16-16-38 in P95 now ... for 3 hrs... so far Ok
 
Last edited:

amrnuke

Golden Member
Apr 24, 2019
1,165
1,730
106
Strange... posted a message on prev. page (wrote it in a half an hour), mainly to your attention, but there it's been said waiting for approval :)
Can you copy-paste it as an edit to the above post? I've never had an issue like that.
 

repoman0

Diamond Member
Jun 17, 2010
3,548
1,911
136
These have been stable for me on 1.1.8.0, 1.1.9.0, and now 1.2.0.0 with no change to overclockability or voltages, either improved or worsened.
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.
 

ASK THE COMMUNITY