Welcome to ExtremeHW
Welcome to ExtremeHW, register to take part in our community, don't worry this is a simple FREE process that requires minimal information for you to signup.
Registered users can:
- Start new topics and reply to others.
- Show off your PC using our Rig Creator feature.
- Subscribe to topics and forums to get updates.
- Get your own profile page to customize.
- Send personal messages to other members.
- Take advantage of site exclusive features.
- Upgrade to Premium to unlock additional sites features.
J7SC_Orion
-
Posts
2,209 -
Joined
-
Last visited
-
Days Won
92 -
Feedback
0%
Content Type
Forums
Store
Events
Gallery
Profiles
Videos
Marketplace
Tutorials
Everything posted by J7SC_Orion
-
...I think higher fclk does make a difference on both bandwidth and latency, at least according to my tests and my setup. Lower primaries, especially CL, have a larger impact on latency, though. In any event, the key is to recognize when fclk is on the edge because it too can throw various errors before crashing outright. I know this because my system will run with fclk at 2200+, but errors sneak in, so I set it to 2167 and with the Aorus bonus boost that comes to 2175.
-
It's NOT even April 1st yet ! -
I also leave PowerDown enabled because the RAM is always busy doing something anyways with 2,300++ threads . I have GearDown disabled though. @ENTERPRISE @neurotix if you get to the point that RAM stress tests that loop over and over are fine for the first 10 times but fail at the eleventh or so, it is worthwhile checking the various DDR5 temps > that type of RAM really dislikes higher temps and starts throwing errors (I use 45 C as the cut-off). Another point is that my final 'fine-grain' DDR5 8000 tuning came down to CPU_VDDIO_Mem. At 1.33 V it works fine (same for DDR_VDDQ) and it has not given me a single WHEA ever, or other errors since I finished tuning the RAM. I got there by observing the number of memory errors it was showing in a given test loop early on, then made some small voltage adjustments...if the number of errors declined, I knew I was on the right track...rinse and repeat until no errors even over full-length RAM stress tests, y-cruncher et al. All in all, it was rather painless for me, not least as Buildzoid had tested very similar 2x24GB RAM on an Aorus mobo (650E Tachyon) just recently. My Aorus MAster 670E could take those values as a good starting position, and I actually ended up with (mostly) slightly lower voltages and tighter timings at 8000 than he showed. The real tricky bit was to run FCLK at 2167/75 and 8000 while staying within my voltage boundaries.
-
VDDP...1.05 V (shows as 1.0478 V in Zen timings)...it was one of the voltages I lowered a bit per earlier post; before it was at 1.06 V.
-
...my 670E Aorus Master has most of these
-
For DDR5 8000/+, I've set both to 1.0 V daily but don't exceed that even with bench settings at higher bclk / eclk.
-
-
...don't despair, gentlemen - setting up new memory usually is a big chase down a deep rabbit hole - it can get frustrating....but also be fun in a weird sort of way FYI, once I had locked in my daily setting shown before, I went back and slightly lowered several memory-related voltages (which weren't high to begin with) and also dialed back both LLCs to medium (fyi, more aggressive LLCs can help with RAM oc sometimes). This meant going through the short and long test suite again but in any case, the newer SK Hynix M-die 2x24GB kit really likes the higher speeds, up to CL36 8100+, though it will also do CL30 6000 at stock voltage (didn't even try a lower CL).
-
What about 7800 MHz on your board, noting that the Aorus boards are usually among the better ones for RAM oc'ing. In any event, 7800 MHz was fairly easily locked in with tight timings. I only went up to 8000 after I 'learned' the particulars about my mobo, CPU and specific RAM at 7800. Also, depending on your board, bclk can also get you there, but again subject to A LOT of testing. FYI, another thing to remember per earlier posts in this thread is that V_SOC adjustments work in opposite directions for higher FCLK vs higher RAM speed; you might want to try 2033 fclk and see what that brings re. top RAM speed.
-
...Keeping in mind that we have different boards and also that both CPU and RAM kits can have some variation, I would start with the less-tight settings shown on the left > here ...start with the stock RAM speeds and primaries per XMP setting, then work your way up. Also make sure that your FCLK is rock-solid; I typically lock that in after RAM tuning is done
-
Ouch ! Complete reinstall or 'repair' ?
-
GAME: Ban the Above User for a Reason - EHW Edition
J7SC_Orion replied to Simmons's topic in Chit Chat General
all_ban for disturbing this bandom's deep beauty sleep -
per Zen sheets, mine are single rank. After RAM and standard CPU, bclk+, and eclk+ profiles are all set now, I played around a bit with with Process Lasso , something @ENTERPRISE @neurotix and Co will also surely enjoy soon. It is more complex than Microsoft's XBox GameBar but ultimately gives better control. edit: ...did a few quick benchies; all that CPU & memory tuning is worth it:
-
...let's put it this way: This is actually XMP / Intel RAM micro-coded DDR5, and I have not touched either of those settings...
-
...just for the record, while both DDR5 8000 settings pass long RAM stress-tests, the one on the left is my 'normal' every day one. The differences to the 'tighter' one on the right are minute in for example games, and it never hurts leaving a few steps of space between the abyss and every-day fun. Per-core CO on the other hand has some real and obvious pay-offs. I have got the per-core done for the 'standard' bclk 100 / 8000 but am still working on per-core CO for eclk 104 / 8000 though I have a decent working-set locked in...final steps in CO require a lot of repeated testing across the board.
-
...RGB works great both via Aorus mobo setting and also Open RGB
-
...chocolates and flowers !
-
...decided to go for the slightly tighter of the two tested profiles for now (36-45-45 instead of 36-46-46, and tRFC to 738 from 800). When I have more time, I will try to lower tRAS and later on, also lower and re-test tCL as long as MEM VDD does not exceed 1.45 V. I know tCL 34 at DDR5 8000 won't work at 1.4V
-
Now looking ahead to CPU tuning after your RAM is all locked in, you might want to use corecycler and Hydra 1.3x Pro (or higher) to get to your specific per-core CO if you haven't already done so. FYI, I did my own all-core and best-guess-per core CO, then used those two tools to confirm / deny. My 7950X3D is a bit of a weirdo, but I ended up setting '-6' from 'per core max' across all per-cores, noting a.) that I was running a base of 90L5 (a secondary but cumulative CO settings with my Aorus 670E mobo) and b.) -6 off the recommended max CO level for each core (from as much as -48) works just great. Superb single and all-core results in CineR23/24 (see above) and no crashing anywhere, anytime, and 'zero' WHEA. I like it...I like it a lot ! After RAM tuning, per-core CO awaits you, @ENTERPRISE
-
Not much to add, @kaliz already got it covered better than I could. FYI, I keep V_SOC at below 1.26 V and VDDQ in the 1.3s and yeah, as already mentioned, either go to 1:1 for 6400 and below, or 1:2 for 7800 and higher
-
...all in the name of science: Running through some of my fav games with the modded 7950X3D / 4090 combo while generating detailed numbers in HWInfo for 4K Ultra play
-
...now that my C1 OLED pixels are clean and scrubbed, it's back to eye-candy...
-
...reminds of an older system (an Intel 8C/16t 5960X ROG Rampage LGA 2011) that sort of drove me crazy. It had a name: Nemesis. Time and time again, the relatively sane oc setting on Nemesis would pass every single short, medium and long stress test but once every 5 weeks or so, it would just throw (always different) errors and reboot int he middle of something. After resetting and testing everything, it would be fine again, until the next time...eventually, I gave that whole system away (set to stock speeds) since I still had a 5960X ES left over from another project. More specific to your current sinuation, I would browse Buildzoid's channel for settings of other RAM types (rather than the specific 24 GB / stick new M-die I had linked). I know he did some earlier ones for A-die, and also the initial-release 'M-die'
-
...Pixel cleaning won't fix really 'dead' pixels but they can get stuck on a specific colour, including black - have to figure out which one is which. Using an all-black background (desktop setting will do) and then an all-white and an all navy blue one usually helps to identify which pixels need attention cleaning. The one pixel that needed attention on my C1 was dead center both horizontally and vertically...as mentioned, I did two rounds of pixel cleaning. The pixel had clearly improved by more than 50% after the first round (recalling that it was stuck white-green). Second round seems to have fixed it.
-
...I had one pixel on my C1 that was stuck on white-greenish, so not 'dead dead'. If you go into the LG menu, look for support > OLED Care > OLED Panel Care > Pixel Cleaning... takes a bit more of an hour (per onscreen instructions, can't use the monitor/tv then), but it will turn itself back on when done. I had to do two rounds and then it was back to normal.
.png.9dbea6f99bd8822b58608e14c56d0268.png)
.png.42ee61dff8853298b2a59c804bdaba26.png)
.png.f4406ff5c3928fc193288a21846cf08e.png)
.png.5ebcb2c4b8d3150c9335588a53617370.png)
.png.0af826b58ad24878330c2e60ead0735c.png)
.png.9b3aaef767302616c6de6b07a58cca61.png)
.png.bc91b96efb88f761e1d98924ea437227.png)
.png.be086a49e295a60c30b2e0c7c8757b4c.png)