F5F Stay Refreshed Hardware Desktop Is the XT artifact related to Question 7900, or is there another explanation?

Is the XT artifact related to Question 7900, or is there another explanation?

Is the XT artifact related to Question 7900, or is there another explanation?

Pages (2): Previous 1 2
S
Snak00s
Junior Member
3
03-22-2022, 12:26 PM
#11
I'll check if going back to earlier driver versions resolves the issue. I didn't realize it was present in the prior driver release (before the RDNA4 launch) until yesterday, and updating to the latest didn't help. I only noticed it after seeing it in GTA. I plan to revert to an older driver group and test again. It also appears to occur consistently when I set the SpeedWay benchmark to 4k instead of 1440p.
S
Snak00s
03-22-2022, 12:26 PM #11

I'll check if going back to earlier driver versions resolves the issue. I didn't realize it was present in the prior driver release (before the RDNA4 launch) until yesterday, and updating to the latest didn't help. I only noticed it after seeing it in GTA. I plan to revert to an older driver group and test again. It also appears to occur consistently when I set the SpeedWay benchmark to 4k instead of 1440p.

S
SavoiaB
Junior Member
37
03-24-2022, 09:37 AM
#12
I went back to a beta driver from last year, and the issue remains unchanged. It seems to be related to 3Dmark's 4K version of Speed Way, which I can't recreate elsewhere, though I noticed GTA V Enhanced behaves similarly.
S
SavoiaB
03-24-2022, 09:37 AM #12

I went back to a beta driver from last year, and the issue remains unchanged. It seems to be related to 3Dmark's 4K version of Speed Way, which I can't recreate elsewhere, though I noticed GTA V Enhanced behaves similarly.

Y
yojochemhier
Junior Member
37
03-24-2022, 02:31 PM
#13
I chose to share this question on 3DMark's Steam community discussions. The developer replied within less than six hours, confirming it’s not a hardware problem but checking if it relates to a driver or benchmark issue.
Y
yojochemhier
03-24-2022, 02:31 PM #13

I chose to share this question on 3DMark's Steam community discussions. The developer replied within less than six hours, confirming it’s not a hardware problem but checking if it relates to a driver or benchmark issue.

Pages (2): Previous 1 2