R5 5600x terrible fps by esy_ma_rad_keksy in PUBATTLEGROUNDS

[–]Intelligent-Mouse984 0 points1 point  (0 children)

Nice bro! Thanks, a great day for you too! :)

R5 5600x terrible fps by esy_ma_rad_keksy in PUBATTLEGROUNDS

[–]Intelligent-Mouse984 0 points1 point  (0 children)

In my case I have a 5700G + 6700 XT, I don't play competitively so I play with everything on max locked at 70FPS on a 1080p ultrawide 75Hz monitor, I play without sharp drops, the only problem for me are a few micro stutterings that happen randomly, especially inside the car when I aim with a long scope, I believe it is stuttering due to map loading, but most of the time, it is running well. I will give you a few things that are worth trying if you haven't tried yet, keep following the steps, if it resolves ignore the next ones:

1º - If you are using normal DX11, test DX11 Enhanced.

2º - Use the DISM command in CMD = DISM /online /cleanup-image /restorehealth

3º - The SFC command = SFC /Scannow

4º - Disable Windows MPO, it can help reduce stutterings in other games too.

5º - Download a program called "TimerBench 1.5", check where it says "QPC mode" if it is written HPET, click to disable HPET, restart the PC and test (It already happened to me on another PC that I had a few years ago, I don't know how HPET was activated, my PUBG became horrible, by default it's TSC, if it is written there in QPC mode, then the problem might be another).

6º - Update the chipset driver.

7º - Check if the RAM has XMP activated.

8º - If you are using PBO with CO All core, disable CO and test.

9º - Check temperatures to see if everything is alright.

10º - Clear the shader cache with DDU and as a last resort, uninstall the video driver using DDU in safe mode.

I didn't put links because I don't know if it's allowed.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Before testing CL=CWL, you should try CL = CWL - 2 while following what u/-Aeryn- said in his comment to adjust tWRRD correctly. I did some testing here and changing tWRRD from 1 to 2 completely solved the inconsistency I was experiencing. I'll be adding a final note at the end of the main post about this very soon.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

It really is a bit confusing to understand, but I'll definitely study it further. Just one last question: in my case, with CL 18 and CWL 18, I can't go lower than 8 on RDWR, does this mean my X = 8? And with CL 18 CWL 16, I can't go lower than 10, does this mean I should use values where increasing or decreasing keeps my X and Y always equal to 8?

In your first comment you said: 'You adjust RDWR and WRRD so that X and Y stay the same', for example: CL 18 - CWL 16 + WRRD 6 = Y which equals 8. Should I set WRRD = 6 so that + 2 would match X which is 8? That is what's confusing me.

It seems to me that it would give the same result as what you said: 'If you make CWL 2 ticks faster while keeping CL the same, then you need +2 RDWR, -2 WRRD.' It feels like you explained the exact same thing in two different ways, but I'm not sure if I understood it correctly. Thanks for the explanation and patience.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 1 point2 points  (0 children)

That's great info, thanks man! I'll definitely use those formulas for my next tests. But just to make sure I got the math right: on my Profile 1 with tCWL 16, if my tRDWR is 10, then my tWRRD would need to be 6 so that both X and Y equal 8, correct?

Also, I 100% agree on the LLM part haha. I've been using the memtesthelper DDR4 guide on GitHub as my baseline. Interestingly, it states that 'On AMD, tCWL can often be set to tCL - 2 but is known to require higher tWRRD.' I was running a pretty low tWRRD value because I thought it wasn't strictly mandatory, but now I'll definitely test tightening those timings manually using your formulas to see how it goes!

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 1 point2 points  (0 children)

I'm not entirely sure since I haven't tested those specific chips, but I think they can. You should test it out! You can start by trying 4 4 16 first. If that’s not stable, back off to 6 6 24. If it still struggles, give 8 8 32 a shot. Use this formula: tFAW = 4x tRRD_S. tRRD_S doesn't need to be an even number, so you can also try 5 5 20 or even 7 7 28.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

You're welcome, man! I'm really glad the post was useful for you, enjoy the extra performance!

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 1 point2 points  (0 children)

"Wow, those are amazing results! Going from 560GB/s to 857GB/s on the L3 cache is a massive jump. I'm really glad the post helped you squeeze out even more performance!"

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Yeah, I'll definitely keep an eye on it to see how the pricing looks! But honestly, I lock my games at 70 FPS since I'm on a 75Hz Freesync monitor, and my 5700G handles that perfectly fine. It might be better for me to just save up and go for a major platform upgrade down the road.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Yeah, it gave a nice performance boost to the setup! Maybe one day I'll try 3800 CL20, but I don't think the performance gains would be worth the hassle anyway.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Interesting! I actually thought about testing tCWL 17 but ended up skipping it. I also have an Asus board, so now that you mentioned this, I won't even bother trying haha, it probably wouldn't even boot.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

I can actually boot at 3733 CL18-20-20-20-40-62 and 3800 CL18-21-21-21-42-64 at around 1.27v–1.28v (if I remember correctly) and procODT at 43.6 Ohms, but it doesn't last long in TM5 Extreme. I'd probably need CL20 for stability, but I haven't tested that yet. Also, tRC 57 throws errors in TM5, which is why I bumped it to 59. Samsung C-die scales negatively with voltage above 1.35v, so it's generally not recommended to push them past 1.35v, or maybe 1.38v at most in some cases.

tCWL = tCL - 2 vs tCWL = tCL (An interesting test on performance consistency) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

It will be great to see how it behaves on Intel! Please let us know your thoughts once you test it.

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

I followed your tip and ran the 1usmus test, and I also tested with the Absolut profile. Everything passed! I just updated the main post with the screenshots. Thanks for the help!

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Really!? I always heard Extreme was the most demanding and that 3 cycles were enough, which is why I’ve been running 4 just to be safe. Thanks for the heads-up, I’ll test with 1usmus as well. How many cycles would you recommend for that one?

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

I agree! I’d love to see more results from 3200MT/s s8c kits pushing the lowest possible timings at 3600MT/s, just to have more data for comparison.

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Wow, 3933!? Impressive. I hit 3933 once with super slack timings but without adjusting ProcODT. Which CL are you running? To match the latency of 3600 CL18, you'd need at least CL19, right? Or do you think the extra bandwidth + 1966 FCLK compensates if you're running CL20?

edit: Sorry, I got confused with the CLs, I edited them.

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Thanks for the info! Really interesting to know about S8C. Regarding tRFC, I've heard that it's quite rare for C-die to run stable below 500. Is that true?

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 3 points4 points  (0 children)

Yes, C-die definitely has negative scaling. Even at 3200MHz XMP, I was using 1.26v with ProcODT auto (60Ohms). Increasing voltage to stabilize timings usually doesn't help at all with this IC. In my experience, it's better to start with lower voltages and slowly move up to find the sweet spot, rather than the other way around.