chew*

My guess would be aggressive error correction. 2000 is not really any more stable than 3933 or 3966 all produce whea errors when not cutting OS memory down via maxmem. 3800 and lower is perfectly fine if there is no post hole which apparently even on DARK my 5900 has at 3800 with 07 post code. 3800+ boots fine but wheas.

I've played with the feature. It's viable if your not setting your baseline at "prime stable clocks" but AMD does a better job at it if your target fixed clock is "prime stable clocks" Right now other than that feature and or want the ability to SHOW a number higher than 2000 fclk or require the slightly improved vrm for benching on ln2 or just want a fanless heatsink solution I see no reason to upgrade to DARK. It's not bad, I like it but overall experience wise it runs and performs the same in the 24/7 stable department.

probably a similar situation as this. Fmax scalar vs PBO. 4.6 avg clocks through CB 4450 avg clocks through CB Although I noticed something when pushing dual CCX chips to the ragged edge that score is effectively half what you would expect leading me to believe 1 CCX has dropped.

define working are you looking to be stable or looking to bench. I'm not saying its impossible but i am saying its possible that it will never be stable due to the whea reports being cpu bus/interconnect. booting and running does not denote stability which both hero's lack at anything over 1900 in my testing.

High pll buys you about 200 mhz more mem clocks linked. without it the chVIII non dark is capped at 3800/1900. If you experience slowdown crank it till you don't....... Board choice seems to matter alot as to how high the fclk can go linked to mem, as long as the vendors aren't already playing games with pll you should be able to gain 200 mem/100 fabric.

Jack up your PLL voltage to about 2.1v. Benching only........do not take this advice anyone running 24/7.........

probably error correction feature in cpu causing slowdown. bclk on asrock x370 was limted to like 110 previously have to kill all devices no nvme best to physically unplug the bluetooth/wifi from board as it knocks it out will probably break it. pci e gen 1 etc etc all the AMD bclk tricks will be needed for it to maybe work.

yep davis was a tad faster than this on the giga which was faster back then. This was one of the fastest 4 gig results back then. looks like 5000 series does it easily. Now ill have to break it down see if cpu model impacts results or we don't need the highest cache cpu to play the game. I imagine at your experience level you tested 2x8 also loud so coldbug was bad regardless i gather?

now AMD is faster than r1 finally. hows the 4 gig clock results loud?

yah it's not that causing this problem speed. These are neos. they are from the new bins. In fact they are very close to the non existent 1.4v c16 4000 bin as they can do 4000 16-16-16-36 4000 @1.4v if I leave everything else auto. I'm only running 1.45v to 100% ensure they can handle my subtimings. 1T is really not the problem anyway. the problem exists without even throwing 1t in the mix and the problem lies somewhere in the training when trying to manually tune shit. If B0 and B1 is shit then A0 and A1 should be shit as well. I have 4 8gb sticks of old B die so I will compare them versus my royals 2x8 gb which are new bdie but tbh i'm not expecting much as this board currently has an artificial wall. I already found a very convincing bug and can do 4600 with only 1.35vddr ( because if you change that it fails boot ) Almost full auto boots and runs tests fine 4400/4500/4600 but copying settings and inputting them identically fails training so it's not possible manual. Honestly I know how they test and i'm testing the same way so they probably think nothings wrong board does 4600 it's good. Go manual and not so good

That is not gonna kill anything. I've run up to 1.7v and i'm sure the hardcore benchers run more.

Just requires a little balls and good air/water, @ 4300 he was probably under 1.4 vccsa and 1.3vccio as that what the board autos to @ 4400.

Heres proof on 1.2z bios. I included voltages. If I even set vdmim manually to 1.35 this will not make it to bios. I would not call the bug voltage related I would say its manual settings related as literally I set speed primary timings that can actually run @ the 1.35vdimm limitation and set PPD 0. If I set rtl training no post. if I set turnaround training no post. if I set vdimm no post if I set vccsa no post if I set vccio no post. If I set subtimings no post. I should rephrase that. it fails OC it posts but fails to boot with desired settings. This is your 4300 limitation bug. Unfortunately my 32gig set can't seem to hack it over 4600 with 1.35 vdimm limitation or the vccsa is getting more retarded than it already is @ auto.....

It can boot above 4300 and that "wall" is around 4200 on DR 2x16gb but not full manual. I mentioned this bug awhile back. Touch no voltages set primaries loose and touch nothing else (18-18-18 4400 20-20-20 4600 ) even 32gb can boot 4600. after 4400 vccsa gets excessive ( 1.6 vccsa) though so fair warning. Just manually setting voltages alone and setting them to exactly what board is auto setting is enough to hang up the boot sequence but I have not pin pointed the problem.

Here's a tad more info on what it does. It existed on z390 but not everyone knew much about it.

RTL IOL are impacted by alot of things. Density. Cas latency and speed. Sometimes you can pull them in tighter if a board defaults loose. Sometimes you can't. typically speaking if 4 dimms 58,59,60,61 for example would be normal for 4 dimms. 58,59 for 2 dimms of course all this can change based on CL and speed so the simple way to drive RTL lower is lower CL. IOL at least on this board is rather loose with DR dimms.

100% in agreement but at least we are not taking steps backwards. Newer bios are improving operation.

It's 32g and that profile is conservative and still won't load everytime unless I set them to 0 not 2x8. I explored beyond and went balls out. this was impossible with out them set to 0. This also loads every time now. I'm fairly certain it would be way easier on 2x8

you guys are probably 1 version behind me then. Screenshot shows defaults. It's right under dll bandwidth. setting that to 0 alone does not buy me much. setting these all to 0 got rid of my random retrains something fails OC. Not only that but without it say I set trefI to max my rtls would go wacky even though set manual when I set trefI max. now they don't with 0,0,0,0. In fact I can pull a lot of timings in now and boot fine. I should probably do a video. My settings are prime stable hci stable tm5 anta stable occt stable aida stable but if I loaded defaults then loaded profile fail OC. just changing those now when I load profile it works every time.

Here's a guide although it mostly follows the rules which some can be broken. https://github.com/integralfx/MemTestHelper/blob/master/DDR4 OC Guide.md

Have you tried setting DLL bandwidth 0 and all the dllbwEN settings to 0? That seemed to solve my random load profile and sometimes train and sometimes not issues. I don't have a post code reader on unify itx but i have debug lights without those set it goes 1-2-3 repeats 3 times fails oc. With set to 0 it just goes 1-2-3 boot. Not to mention those settings are magical as i can run way tighter timings yet i can't measure any losses anywhere. I've played with Rtt's also but maybe I just have not found the right combo yet. So far its not buying much with DR on my particular setup.

Just exploring options in the new bios and what the board can and can not do. 2x16 DR 36ns flat @ 4200 c14.

I don't think 5 gig is an artificial issue. My chip can bench 5.2 ( multithread like CB ) and I've run xtu @ 5.1 on sub par cooling. If anything I gained 100mhz benchable over my buggy/broken from day 1 ASUS z490 Itx -013 serial # board. I'm sure if I swapped the cooler in the prototype i'm working on to my liquid freezer 2 280mm I could get over 5 gig stable.

you would be wrong. If i was not running memtests right now to screenshot i'd go screenshot bios right now. Unify I memory timing page bottom of page power options PPD enabled 2 or 3 settings down from that I have PPD 0 set. These are not even try hard memory timings and I'm sub 40ns because I have PPD 0 set in bios. And yes it absolutely on it's own does. My latency would be 45-46ns if i change nothing but that. I've already stated this in this thread if you read. Also the Asus being at 37ns @ 4400 c17 is not impressing me. My Asrock gets 37ns @ just c15 3600. Looks like PPD to me in screenshot 3 but maybe I forgot how to spell. Added as of 1.2w. screenshot 4 shows what was added with 1.2z bios.

I would go with the latest. Your latency issues is just the PPD setting bottom of mem timing page. Set PPD enabled in power options then set the PPD to 0.