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
93 -
Feedback
0%
Content Type
Forums
Store
Events
Gallery
Profiles
Videos
Marketplace
Tutorials
Everything posted by J7SC_Orion
-
...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.
-
...after close to 2.5 years, I finally had a 'stuck pixel'...two rounds of the Pixel Cleaner option and that was that, for now at least. Also: OLED 48 + 4090 + 7950X3D + DLSS 3.5 w/ ray reconstruction =
-
DLSS3.5 coming for FS2020 ...some Vancouver fly-bys ...and some Miami / Miami Beach
-
V_SOC is a bit of a two-headed monster which fights with itself; high RAM clocks want it one way, but high InFin speeds the other way. It took me a while to find the common ground between the at 1.255 V_SOC for InFin at 2167 MHz and DDR5 at 8000. I don't know much about your specific CPU and mobo/bios, but if you have the latest bios and thus AGESA loaded, I would start with V_SOC at 1.25 V and the same for DDR_VDDQ and CPU_VDDIO_MEM. BTW, you likely will have to do two separate profiles - one for 1:1 (ie 6400) and one for 1:2 (ie. 8000). Best to lock one of the two in first (I settled on 1:2 8000 quite early on due to the specific type of new M-die 2x 24 GB). Once you get to 1:2 dividers and around 8000 MHz DDR5, you can test out V_SOC again at 1.25 V_SOC to 1.26 V_SOC but raise DDR_VDDQ and CPU_VDDIO_MEM to 1.3 V. Folks usually start out having these two the same but each mobo / chip combo can be different. Apart from TPU's Memtest64, I also use y-cruncher by itself, and the latest version of OCCT. I have not used Hydra Pro 1.x (1usmus) for RAM yet but I think it has a RAM stress / stability section for it as well . FYI, I had someone suggest the other day to run Karhu at (3x 30,000=) 90,000 % . You run these things long enough and error will creep up which is why servers have the full-meal EEC deal onboard.
-
...this seems to be geared towards Zen3...below on the left are Zen timings for my 5950X and on the right is the 7950X3D. They are different animals to some extent. For V_SOC on the 7950X3D, 1.3 V is supposed to be the safe max but I stay well below that, even at the speeds I am running. Some earlier bios would automatically push that to 1.4 V and above when enabling EXPO (or XMP) and that led to several such CPUs frying themselves. The MEM VDD is the main DDR5 voltage and I have seen folks push 1.7+ V with extra RAM coolers. My M-die comes in the 1.35 V, 1.4 V (and possibly 1.45 V) as nominal values from the factory so the 1.425 V I set it at is not a worry. FYI, I have lowered MEM VDDQ below a bit to 1.325 V since that screenie was taken.
-
I finished with all the memory tuning and finally got around to do per-core CO. That said, the Aorus board also has a 90L5 'all-core' setting on top which I did leave in place when doing the per-core CO tests. Below is for stock 100 bclk / DDR5 8000 and using the balanced Power Plan in Win 11 Pro . Translating that into my fav eclk 104 setting is going to be tricky since I am running a negative boost cap on that to compensate for the 4% increase in CPU speed - the 7950X3D (fortunately) does not allow me to set a positive v-core offset on CCD 0 at least. All this means that I probably have to run positive CO values for eclk 104, rather than the negative CO for the stock bclk. FYI, I among other tools used Hydra Pro to validate my CO for bclk though for now, I am staying below the 'max CO' by -4 or each core.
-
...I do use Aida but get Buildzoid's point(s). For general memory testing, I use OOCT / RAM and also highly recommend "memtest64" from TechPowerUp. It doesn't show you the actual latency but is a good test to run for final stability (ie. 10 loops min). I believe Hydra 1.3Pro also has some RAM test w/ latency but I'm just using it now to get per-core CO values. So far (ie below), I've just been using all-core trial+error...below is a fully stable eclk 104 screenie with all-core - these things can clock !
-
...re. tFAW, here is a time-stamped segment by Buildzoid running DDR5 8000. He explains the relationship between tFAW and other parameters (ie. tRRD_S). At lower RAM clocks both can be reduced but their relationship has to stay intact
-
...DDR5 setups are a bit trickier than DDR4 IMO - DDR5 has 'some' error correction code (re. single bit memory errors) though it is not the full ECC with an additional chip on the DIMM (per Corsair's web site). Because of this 'ECC Light', finding the edge of the canyon takes more testing. On my DDR4 systems I have GSkill GTZR Samsung-B for years and years, ezee-peezee to set up. DDR5 will take some more time to master. Apart from lower primary timings and maxed InFin, tRFC in secondaries also help with higher bandwidth and lower latencies, but it looks like you are already doing well on tRFC. I do wonder about your tFAW '15' in your Zen Timings screenie above, btw. It might be that your systems is just ignoring it - 15 is super low for DDR5 ...btw, Unigine's Superposition 8K does give your system memory a bit of a workout as well once you have run the usual RAM stress tests which can be a bit boring. At least Superposition 8K is s.th. to look at and listen to while waiting for it to do its thing.
-
...in addition to what @kaliz mentioned, a higher speed on the InFin fabric will also cut latencies though 2100 FCLK you showed in your post is nothing to sneeze at. I can run 2200 but typically have it at 2175 (2167 + Aorus 'bonus boost')
-
...yeah, I run mem DIV/2 at DDR5 8000. According to Buildzoid and a few others, DDR5 7600 speed is were DIV/2 becomes more or less worth it over DIV/1, at least in many more modern apps (think also resizable_BAR). As to latencies, I have now arrived at / dropped to the high 50 ns range in Aida bench, after much additional tuning. Things such as disabling PowerDown Mode and GearDown Mode give you an extra push in at least Aida cache and memory benchmark. That said, while I have disabled GearDown because I dropped a few primaries to 45, I re-enabled PowerDown again - sometimes, disabling it can lead to intermittent and hard-to-track oddities. Given the most recent AGESA updates which opened up a whole new world for Ryzen RAM clocking, a bone-stock 7200 kit at DIV/2 starts in the low to mid-70s ns latency - but the stock XMP and/or EXPO settings are soooo generous for the vendor as to not throwing any surprises (and RMAs). A well-tuned but 24/7 '''sane''' multi-purpose work-play setup should get to 59 ns - 64 ns range, depending on various factors such as your mobo's topology, your specific RAM kit and such...and I have seen low 50ies (51.x) ns on the 7950X/3D some folks showed w/ their Aida, but only with very high voltages. I have three rules for my 7950X3D build re. voltages (and related temps): 1.) V_SOC has to stay in the 1.25X V range (up to 1.30 V is considered mostly 'safe' even after the bubble-burns on the socket / CPU underside earlier in the year), and 2.) VDD DDR has to stay in the 1.42X V range. My RAM's stock voltage is 1.35 V, with many newer DDR5 high speed kits even at 1.4 V or 1.45 V 3.) Cool DDR5 is happy DDR5 - I have some extra Arctic P12 fans right above the DDR5 RAM - this kind of RAM gets hot (including PMIC) and you want keep it in the low 40s at most when under stress. Many folks resort to water-cooling as DDR5 has some fundamental differences (and heat sensitivity) compared to DDR4 Samsung-B, for example Final advice: Open your favourite beverage before diving into the RAM-tuning-and-stress testing rabbit holes (there are many of them)...it's going to take a while and a lot of testing...
-
...new patch today (DLSS update ?). After downloading a new driver for Cyberpunk 2077 w/ DLSS 3.5 ray reconstruction and path tracing, still found the time for a quick local flight...below is a parking lot of a nice pub.
-
Rejoice ! DLSS 3.5 for CP2077 with ray reconstruction is here
J7SC_Orion replied to J7SC_Orion's topic in Nvidia
...on the surface, just a frosted window in a back alley in the screenie below, but what's wild is that can look inside and the perspective changes as you move around....also, game-play seems much edgier and violent, even when 'just roaming'
- 1 reply
-
- 1
-
-
...had a few rounds roaming in-game and a quick benchmark in Cyberpunk 2077, after downloading the latest NVidia driver and a huge patch from Steam...it is worth it ! DLSS 3.5 with Ray reconstruction and Path tracing is faster than DLSS3 with (just) path tracing before. I had only a very mild 'oc' on the 4090, but it was still way beyond expectations (7950X3D doesn't hurt) ... looking forward to clock this up fully and also add some screenshots, suffice it to say it is gorgeous. As an aside, I like and play the new Starfield, but in certain scenes such as those with water or open fire, it can't measure up to CP 2077, never mind ray reconstruction which is not only faster as before but also unloads a bit from the CPU. Then again, Starfield has also announced 'official' support for DLSS 3.X (?), though unofficial mods for that are already out there
-
...here you > go ...and the latest Zen timings I use for DDR5 8000
-
Very good point, but I already did that both voluntarily and also via Win 11 Pro prompts during boot-up after pushing bus clocks too far. FYI, my avatar byline of 'invalid media' at another forum relates to exactly that, from back in the days when bus-clocking was still done by jumpers...I managed to lose some vital Excel tables for a work presentation the following day after my system would not boot up anymore after excessive bus oc-ing, with the bios splash screen stating 'invalid media' when it got to my C:\ boot drive That said, I did manage a few more SuperPi runs (first series of pics) with the DDR5. The second pic just shows the 'daily' setting, with more detail from 3DM SystemInfo
-
...pre-patch HDR settings
-
FYI - yesterday, I accidentally booted into Win 11 Pro at s.th. like 6008 MHz CPU and DDR5 8220+- ...I wondered why the mouse and also the audio was acting up after signing in, and when I checked HWInfo, I realized what had happened...I had set the RAM back to 80X but forgot to lower the bclk I had played with just before. Surprisingly, it didn't actually crash but I managed to hit an orderly 'shut down/restart'. Once the winter weather sets in, I might try to explore 'DDR5 8200' on purpose, though that likely will require a voltage bump to VDD & Co
-
been there, done that- just like the other Cinebenches since R11
-
...latest patch seems a bit crisper visually, in external scenes in particular
-
It depends on the app, I think. According to Buildzoid, the cross-over between 1:1 and 1:2 is somewhere around 7600 MHz - which is why I run 8000+ MHz.
-
Thanks kaliz ...I did tighten some of the primary and secondary RAM values a bit more and then thoroughly tested them, per below. tRFC is about 40 clicks away before RAM tests start to act up but that delta is really nothing with DDR5, I will try some of the other suggestions, though. Overall, I'm very pleased with this RAM kit (just under US$200 for DDR5 7200 2x24/48 GB M-die) ...CL30 6000 to CL36 > 8100 gives me a huge range to play with. Kudos also to Gigabyte for the Aorus RAM topology and other setup; it seems very resilient. FYI in the screenie below, the VDD at 1.425 was left over from the 8100+ runs. I also started exploring 'eclk' a bit on the mobo and am in the process of creating a table of eclk value vs. overunder clock boost setting in the bios - table is not quite finished yet but that will open up some more sandboxes to play in
-
...The earlier DDR5 8000 timings (incl. via Zen screen) are thoroughly tested, but I am guessing at everything else at this stage as I'm still putting this thing together properly. Also a quick note and AM5 backplates --- the dual mobos w-cooled build (prior 2x AM4s) both use Phanteks 360a blocks which work very well, and also use the stock AM4 backplate. But for some reason, the thread size (rather than pattern) was different for the Aorus Master 670E; I ended up getting 6/32s from the hardware store when mounting the Phanteks 360a cooler on the new AM5 backplate - very carefully, of course - works like a charm now, though: 7950X3D has yet to get past 85 C even with 164 W. EDIT- @neurotix @kaliz ...had a few minutes to clean up 8100+ a bit. Not fully optimized yet (re. extra CPU speed needing an updated boost ceiling) but clearly, it is a viable option and passed basic RAM and CPU tests. Superpi and Aida RAM speed results within run-to-run variance of 8000 though. I like to get latency under 60 if possible (best so far 60.8)....may be with eclk ?
-
...I'm not exactly a beginner when it gets to RAM overall (used to do sub-zero at HWBot), but this is my 1st DDR5 kit. DDR4 was easy, I only ran Samsung B-die 'GSkill GTZR' from 2015 - 2022. Funnily enough, this is my 4th AMD 16 Core CPU (incl. a TR) yet I have never owned an AMD specific microcode RAM kit, just always those marked 'Intel XMP'; seems to work for me though. I will do some more RAM setup work and testing later in the coming week...I first want to finish the actual re-/build project of the dual-mobo single case setup because I also need one half of it back for work... EDIT @kaliz : ..just did a super-quick test one over the lunch break. CL36 DDR5 8110 on the left (not yet optimized), including Superpi -- CL 30 DDR5 6400 (not even close to being optimized), including Superpi -- CL 36 DDR5 8030 (optimized and long-stress-tested). CL28 6400 also possible, but this new type of 24 GB Hynix-M-die / Intel XMP is clearly laid out for speeds above 7200 - I might even try 8200 next weekend. Please note that all voltages and sub-timings other than CL were the same for all three quickie tests and based on the fully tested 'daily DDR5 8000' setting.
.png.43f0cb06d8a348d2293f90070252028b.png)
.png.6d8c0996cc684c640fd381f5bbb1a185.png)
.png.56e09433de8c8089831a12f674724bc3.png)
.png.e4d18f995c4fbd3418b4b81ef06a635c.png)
.png.668cc5b3ac2c4e63960b39074c199770.png)
.png.03c651c2d8dbf331565685425c0af65d.png)
.png.10504d4a2505ed97464c6abfcbbaf58e.png)
.png.9e29b35f8c1f8d8a7c2481fc67f227da.png)
.png.c99122eb17f7b71a9a9694f690fd8e38.png)
.png.f0e1db76a3c48ae4c328af3020315201.png)
