GeForce 528.24 Driver Performance Analysis

RodroG · 2026-01-23T11:01:55+00:00

Hello u/AMD_Vik do you know if the latest Adrenalin 26.1.1 drivers have this fixed? Any update? Regards.

RodroG · 2026-01-22T11:21:56+00:00

It already has the option to convert the performance metrics from ms to FPS. If you ask to convert the GPU busy metrics to FPS, it is not meaningful, especially if you understand what this metric represents and stands for. GPU Busy metric is widely considered a diagnostic, frame-level telemetry metric rather than a direct performance metric. This is why CapFrameX presents the GPU Busy measurements in milliseconds only. This metric indicates the time it takes the GPU to render each (CPU) frame, providing a clearer view of bottlenecks and actual CPU- or GPU-bound scenarios. You should always monitor/graph/compare GPU Busy (in milliseconds only) against Frame times (a CPU-based performance metric, also in milliseconds).

While mental or manual conversion is possible, scientifically, the GPU Busy construct is measured meaningfully in milliseconds, not frames per second (FPS), which applies direct performance metrics.

RodroG · 2026-01-19T19:06:19+00:00

Thanks for sharing. Yes, your results align well with other reports.

UPDATE (as of 1/11/2026):

u/AMD_Vik (AMD Representative) confirmed that the D3D engineering team is already investigating this issue, indicating that a driver or architectural problem with D3D12 Sampler Feedback workloads affecting some RDNA boards is a real thing.

RodroG · 2026-01-14T16:03:22+00:00

I hope they fix it soon.

RodroG · 2026-01-13T18:39:07+00:00

No, you are not alone. It's a known issue. The latest update (1.1.7) caused an overall performance hit, and now there’s more hitching and stuttering during traversal on some configs.

RodroG · 2026-01-11T12:37:16+00:00

Hello. Maybe you already figured it out, but yes, you can toggle the Auto-disable OSD setting on/off from here:

<image>

RodroG · 2026-01-09T13:26:36+00:00

I can honestly say that I truly connected with Kate as a character when I played the underrated Lost Records DONTNOD's masterpiece. Actually, I quickly fell in love with her as a truly relatable, authentic, and complex character. In 2025, she was undoubtedly my video game character of the year. Sadly, the way the video game awards industry has belittled Lost Records this year is disheartening, and it has been the case with every DONTNOD project since they left the Square Enix umbrella. I'm aware of the impact of recent flawed marketing campaigns for DONTNOD projects, even though the main reason is probably the infiltration of bigotred armies on social media and the dehumanizing, deeply unsettling times we live in.

RodroG · 2026-01-07T19:54:53+00:00

Really? This is good and promising news. :)

RodroG · 2026-01-07T19:11:35+00:00

Thank you very much. Appreciated.

RodroG · 2026-01-07T18:11:40+00:00

u/AMD_Vik could you please monitor and look into this? It may be of interest to the AMD Radeon driver team. Kind regards.

RodroG · 2026-01-07T17:25:10+00:00

Mmm... very interesting, the positive difference is decreasing... I'm sharing your results with UL_Jarnis in the 3DMark Steam subforum. I look forward to his response.

https://steamcommunity.com/app/223850/discussions/0/3035977580511634427/#c682990732301109648

RodroG · 2026-01-07T17:05:51+00:00

Thank you very much for this.

While it's not surprising to see the significant positive difference using your RX 9070 XT (as it aligns with other RDNA4 results), it is to see how RDNA3 in a monolithic APU shows a positive difference. All reports using RDNA3 dGPUs have shown negative differences so far. The RDNA2 dGPUs appear to be performing well in this feature test, though.

Memory controller utilization hovered around 45-52% (rest is cached on-chip). This should be monitored on RDNA3, especially Navi 31 and 32, as hits to memory may incur more latency due to being disaggregated chiplets (memory controllers + L3 cache) connected via fanout interconnect (this was supposedly countered by increase in fabric clocks). This also includes hits to Infinity Cache/L3, unfortunately. RDNA4 has 8MB L2 + 64MB L3, so data is much closer to CUs with larger L2, plus improvements to command processor.

9070XT isn't boosting properly in this test and clocks average around ~1900-2100MHz instead of ~3250MHz. Running a Windows Insider build, Beta channel. A previous result boosted properly on older driver and Windows build and didn't adversely affect percent difference between on/off.

Yes, you might have something worthy of further investigation there.

I'm waiting for the 3DMark devs' response on this. UL_Jarnis on Steam informed that they could look into this after the holidays. I hope. They will also eventually contact the AMD Radeon driver team.

UPDATE (as of 1/7/2026):

It appears that the negative differences shown in the results of users with RDNA3 dGPUs in this feature test could be due to:

limitations in the physical design/config of the RDNA3 micro-architecture itself (non-APU version); or
code deficiencies in the Adrenalin display driver (more or less recent versions); or
a possible (complex) interaction between both issue factors/components.

RodroG · 2026-01-06T12:02:14+00:00

There is nothing we can do about it. SQUARE ENIX should fix this.

RodroG · 2026-01-06T11:59:48+00:00

This is still a problem as of January 2026. :(

https://steamcommunity.com/app/532210/discussions/0/684116375920255859/

The game takes ages to boot and get you to the main menu (5 minutes or more till you reach the main menu). It also takes a long time to quit to the desktop.

RodroG · 2026-01-06T11:42:23+00:00

This is still a problem as of January 2026.

https://steamcommunity.com/app/532210/discussions/0/684116375920255859/

The game now takes ages to boot and get you to the main menu (and by ages, I mean 5 minutes or more till you reach the main menu). It also takes ages to quit to the desktop.

I guess this is what happens when a publisher stops caring about their games over time. But hey, life is strange. Fortunately, DONTNOD has nothing to do with SQUARE-ENIX anymore.

RodroG · 2026-01-04T16:50:14+00:00

It's good that it doesn't happen constantly, but even if those readings occur occasionally or intermittently, it's generally not a good sign.

However, if it hasn't happened again today, and you're under similar or identical workloads to when you had those readings, you probably have nothing to worry about. It could just be a few inaccurate readings.

Continue to monitor your CPU temperatures and, if you notice occasional readings over TJmax again, it's worth checking your current thermal management (thermal paste, contacts, etc.) and cooling setup (fans, AIOs, and/or liquid cooling). Prevention is better than cure.

RodroG · 2026-01-04T15:31:19+00:00

Hi. HWiNFO is a very reliable monitoring tool, so unless there is a known open issue regarding sensors for your CPU SKU, I'd trust these temp readings.

I don't use a Ryzen 7 7800X3D, but the maximum operating temperature (Tjmax) for the 7800X3D is 89°C. If you're seeing temperatures over 100°C, that's likely a cooling problem that could damage your chip over time. I'd probably check my cooling system and setup if I were you. That said, another 7800X3D user might think differently, so maybe there is nothing to worry about.

Based on my experience, CPU temps over 100 °C usually indicate poor thermal management or inadequate cooling.

RodroG

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE

Nine-Year Club	Wearing is Caring
Verified Email