AMD’s new GPU driver is reportedly inflicting severe efficiency points with RDNA 3 graphics playing cards beneath Windows 11, although the bug is a uncommon prevalence from what we are able to inform.
One other level to notice rigorously right here is that apparently the issue is barely affecting 3DMark runs, particularly the TimeSpy benchmark (we’ll come again to that later).
VideoCardz (opens in new tab) broke the information {that a} software program engineer at Google (Osvaldo Doederlein) working an RX 7900 XTX with the newest model 23.3.1 of the Adrenalin driver bumped into trouble (opens in new tab) with a lot decrease TimeSpy outcomes than ought to have been produced.
Certainly, Doederlein’s outcomes got here out at greater than 50% slower than regular, an enormous efficiency loss.
One of many builders at UL (which makes 3DMark) replied to Doederlein to say that they raised the difficulty with AMD, and it seemed to be associated to the newest driver model.
The dev noticed: “We additionally checked out our [3DMark] database to match outcomes on the earlier driver vs. new driver on any consequence utilizing 7900XT or XTX and might affirm that this seems to be an actual, if very uncommon difficulty.
“Amongst all outcomes with the brand new driver, roughly 3% of the outcomes present irregular (very low) scores on Time Spy. No comparable group of very low scores seem on the outcomes with the earlier driver model.”
Doederlein went on to make clear that they’re working a check model of Home windows 11 (Launch Preview – so probably the most secure construct), which the 3DMark dev famous isn’t supported by the benchmarking suite.
The developer added that AMD did ultimately handle to breed this extreme efficiency glitch and that “it’s beginning to look increasingly more like a driver difficulty,” with the very best plan of action for these bothered by the gremlin being to roll again to the earlier driver. Or alternatively to only sit tight and await the repair to be deployed.
Evaluation: Greater than meets the attention
There’s a bit extra to this than meets the attention, as additional within the thread on the Steam boards replying to the unique criticism from Doederlein, there’s an RX 6800 GPU proprietor saying they’re affected – so perhaps it’s not simply an RDNA 3 difficulty – and that rolling again to the earlier AMD driver model didn’t assist. (The 3DMark dev appears fairly certain that the issue does pertain to the newest AMD driver, although).
Moreover, a few Nvidia RTX 4090 homeowners have chimed in saying they’ve been hit, too – however that’s simply two scattered stories, so add seasoning there. Nonetheless, the commonality right here seems to be working check variations of Home windows 11. Certainly, a kind of RTX 4090 homeowners lays the blame on the toes of the preview model of the following huge replace for Home windows 11 (Moment 2).
Regardless of that, AMD nonetheless believes this bug to be a driver difficulty, so we’ll follow that as probably the most correct analysis to date – though it’s doable that the issue can also be wrapped up in utilizing a preview model of Home windows 11, too.
The extra optimistic information is that whoever is being affected right here, it’s seemingly a uncommon bug. The broader concern for these encountering this difficulty is that perhaps it’s slowing down video games in addition to 3DMark benchmarks, and it’s simple to see how of us would possibly get paranoid about that chance.
It’s actually one thing that occurred to Doederlein, who consequently ran a complete bunch of assessments on video games. That included benchmarking with Guardians of the Galaxy, Horizon Zero Daybreak, Dying Gentle 2, Batman Arkham Knight, Returnal, and extra, however Doederlein discovered no efficiency hit in any respect with any of them. So it does certainly look like a benchmarking-only difficulty solely, fingers crossed – hopefully AMD will shed extra mild on the bug sooner or later.
What we are able to rule out is that it’s any type of 3DMark drawback, as a result of because the dev clarifies, the TimeSpy benchmark “has not been modified for ages”, so the misbehavior is clearly all the way down to the AMD driver or Home windows 11 (or each together maybe, as talked about).
By way of Neowin (opens in new tab)
Discussion about this post