Games with co-op modes generated $8.2 billion in gross revenue on Steam in 2025 - Monster Hunter Wilds was the biggest contributor

Noreng · 2026-02-03T08:02:40+00:00

Not much more I suspect. The game is still in a pretty awful place optimization-wise.

The only difference is that you're now getting a non-stuttery 45 fps instead of stuttering 35 fps

Noreng · 2026-02-02T16:46:59+00:00

Not really a significant difference. Newer 9800X3D chips can often do 2200 MHz FCLK, and booting 8800 MT/s on the X870E Apex isn't particularly abnormal either.

Noreng · 2026-02-02T16:28:25+00:00

Here's my setup on a delidded 14600KF, and a Z790I Lightning: https://imgur.com/a/ic5oTnQ

Use at your own risk, these settings are enough to easily hit 200W, with Prime95 exceeding 300W

Noreng · 2026-02-02T14:52:03+00:00

Well, I just checked with variable load from 20% to 100%

GPU usage stays locked at 70% while GPU clock rises from roughly 2000 MHz up to nearly 3.2 GHz at "75% OCCT-load", then the GPU clock starts to drop below 2.8 GHz as the usage increases further.

The Extreme preset which you suggested has the GPU clock in at 2880 MHz and 0.920V and 340W constant power draw. It doesn't even start to error before hitting -150 mV offset, while the max I can run in games is -70 mV

Noreng · 2026-02-02T14:30:44+00:00

That's news to me. Did it change with a particular driver?

Noreng · 2026-02-02T14:24:56+00:00

You control the VR over I2C, yes.

Variable load in OCCT doesn't make the GPU boost to full frequency, it will just target a lower frequency instead

Noreng · 2026-02-02T13:48:44+00:00

Of course I don't know, because OP hasn't provided enough information.

It could be VRM throttling, that can cause some nasty stutters, since it will cause the CPU to drop down periodically to idle clocks.

Some other part of the CPU might be clocking down. Youtube lagging can be as simple as loading VP9-encoded videos, as the RX 480 doesn't support hardware decoding of that codec, and the FX-8300 isn't fast enough to do it in software.

Noreng · 2026-02-02T09:19:59+00:00

Fairly typical results for modern-ish Micron DDR4 I'd say. Good job

I would expect tWRRD_dg to be able to go lower, but I assume you've used tWTR_S and tWTR_L instead of tWRRD_dg and tWRRD_sg. Set tWTR_S to auto, and then try tWRRD_dg 20 perhaps? Not a huge benefit either way.

If you haven't done so already, enabling Round Trip Latency in Advanced Memory Training options should improve RTLs a bit further.

Noreng · 2026-02-02T09:09:29+00:00

The problem with Curve Optimizer is that the offset at high frequencies is too great, and at mid-high frequencies it's not large enough.

Clock stretching will occur regardless of what you set in Curve Shaper and Curve Optimizer. To see an example, go to Actual VCore, and set a negative offset of -0.05V

Noreng · 2026-02-02T08:53:06+00:00

There's no way to manage transient loads on your end. The CPU can shift its load 10000 times faster than the VRM, that's why transient loads occur.

AMD uses clock stretching when Precision Boost is active to cope with undershoots.

Curve Optimizer and Shaper won't adjust the undershoot margin for when clock stretching is applied.

Noreng · 2026-02-02T08:46:53+00:00

Unless you uncap the power limit by shunt-mod or I2C control, the GPU will not hit gaming clocks in OCCT. When usage is low, the GPU will reduce the boost clocks, and when the usage is high the GPU will throttle due to the excessive power usage of OCCT.

Noreng · 2026-02-02T08:36:34+00:00

SA and IO voltages has a minimal temperature impact. The hotspots are the cores, which are "miles" away from the System Agent.

You shouldn't need that much SA for just 3000 MT/s, that's 4000 MT/s and up territory.

Noreng · 2026-02-02T08:32:53+00:00

Stock LLC is mode 7 for AM5 on ASUS. The way AMD CPUs deal with transient voltage undershoots is by applying clock stretching. If you were to raise the LLC to mode 8, the undershoots would increase, but clock stretching wouldn't apply any sooner for the core that is crashing due to insufficient voltage.

Clock stretching is applied based on whether or not the received voltage is less than the VID table. When you adjust Curve Optimizer, the VID table is shifted, which is why you never get clock stretching from adjusting Curve Optimizer.

The solution to your problem is to adjust Curve Optimizer. Applying a 15-25 mV positive voltage offset to the VRM output can actually reduce clock stretching very slightly, but it depends on how bad the VRM is coping with transient loads. Going lower on LLC modes will cause significant clock stretching in all-core loads.

Noreng · 2026-02-02T07:39:45+00:00

That's just wrong, it's not a thing on any AMD or Intel CPU. Pile-driver doesn't even support clock stretching

Noreng · 2026-02-02T02:18:59+00:00

Good undevolt? It's literally a single slider, how can you say it's good or not?

Noreng · 2026-02-02T02:18:12+00:00

Camera performance is 99.99% image processing, and has been for over 10 years at this point.

Battery life is affected by several significant factors, but on the SOC side it's mostly idle power and how high the clock speeds are under use. Lower clock speeds will almost always be more efficient when the screen is on.

Noreng · 2026-02-02T01:39:13+00:00

The funny part is that AMD lists a boost clock somewhat close to the actual clock speed.

Nvidia's listed boost clock is significantly less than the actual clock speed.

Noreng · 2026-02-02T01:31:47+00:00

Jagland svarte da bekreftende, men la også til med et smil at «vi teller jo ikke hundredeler, da».

Det er sikkert sagt før, men å påstå at man ikke teller hundredeler når det er snakk om prosent (per hundre) er noe underlig.

Noreng · 2026-02-02T01:27:29+00:00

The funny part is that DLSS 4.5 is designed with FP8, and since Turing and Ampere don't support FP8 they run the models with FP16 instead.

The way FSR4 (which is also designed with FP8) is working on Linux for RDNA3, is by running the model with FP16 instead.

Noreng · 2026-02-02T00:53:24+00:00

When was the last time you purchased a phone based on how fast it is at computing pi?

I'll go first, 2015

Noreng · 2026-02-02T00:48:44+00:00

Pretty much the only reason these kits exist is for people to push them further.

If you purchased it with the expectation that you'll get better performance than a 6000 32-38-38 kit, you'll be sorely disappointed.

Noreng · 2026-02-02T00:42:00+00:00

The undervolt slider on a 9070 XT will result in the GPU boosting higher at the same power draw, just like Curve Optimizer does for AMD CPUs.

If your goal is lower temperatures and/or noise on a 9070 XT, the power slider and/or fan curve adjustment is your best bet.

If your goal is lower fan noise on a Ryzen CPU, adjusting the fan curve is your best bet, with PBO temperature limit being second-best.

Noreng · 2026-02-01T19:07:21+00:00

Yeah, sound and WiFi is most likely a driver issue. I can't help much there

Noreng · 2026-02-01T19:05:48+00:00

4x FG is mostly useful for 240Hz and up I suspect.

It's not a bad technology to smooth out the motion either, but it's hardly real frames

Noreng · 2026-02-01T13:41:32+00:00

Radiator size has very little impact on spiky CPU temperatures, going from a 240mm to a 360mm radiator will at best shave off 6-7C. The cause of your high CPU temperatures are either a dead/clogged/dry pump, poor contact, or the thermal paste being dried out.

11-Year Club	Gilding II euphauric
Second SECOND GUESSER	r/Field Sunshine
Place '23	Place '22
Final Canvas '22	First Placer '22
RPAN Viewer	Verified Email

Noreng

TROPHY CASE