Jump to content
HWBOT Community Forums

chew*

Members
  • Content Count

    576
  • Joined

  • Last visited

  • Days Won

    3

chew* last won the day on September 19

chew* had the most liked content!

Community Reputation

73 Excellent

About chew*

  • Rank
    You haz bag of sand?

Converted

  • Location
    UNITED STATES

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.....
  2. 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.
  3. Here's a tad more info on what it does. It existed on z390 but not everyone knew much about it.
  4. 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.
  5. 100% in agreement but at least we are not taking steps backwards. Newer bios are improving operation.
  6. 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
  7. 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.
  8. 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
  9. 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.
  10. Just exploring options in the new bios and what the board can and can not do. 2x16 DR 36ns flat @ 4200 c14.
  11. 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.
  12. 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.
  13. 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.
  14. define stable. I probably run more stability then most. I could pass anything anyone asked before at 2k yet not load the profile 100% and get a failed Oc reset. Now I don't get a failed Oc reset loading a 2k profile I'm let see at 23 hour mark in prime 95 which 99% of users won't even run.... That would denote more stable. Oh before I forget. At least on my bios they added the DLLbwEN options theres 4 of them.
  15. Artificial manual tuning DR dimm wall at 2000 is gone. No clue how far it can go yet. Seems that training may be improved I'll test more my 2000 profile would load from defaults sometimes and sometimes I had to baby step to 1900 then 2000 but seems to handle shotgun approach better now. Not 100% sure but looks like have lost 1ns latency.
×
×
  • Create New...