I think we discussed this some place else but if I remember correctly, it was because you’re running an Intel-based chipset motherboard.
Based on the fact that the AMD Gitlab link I posted a second time in one of my last posts was still clicked over 50 times (just like the one in the first post), I think there’s a greater ‘dark figure’ of affected users simply not posting but reading the forum post.
And that’s just fine because I asked everyone to post any issues over in the AMD gitlab. I would like to assume this worked 
, because I am subscribed to a bunch of the AMD gitlab issues and especially #2950 was updated regularly with a constant stream of new users reporting the same issue.
EDIT (27/06/25):
When I read across multiple discussions in the AMD driver gitlab about the VNC race fixes, I really thought they finally found the ‘culprit’. 
It seems though, we shouldn’t get the hopes up too high because some people are still reporting freezes past kernel 6.16rc6.
I thought, I’ll add in two interesting links about the current development which I stumbled across in the AMD gitlab.
- discussion @ “Display Next Hackfest 2025” about ‘Pageflip Timeouts’
- discussion @ “amd-gfx” mailing list about bug not fixed in 6.16-rc6
EDIT (06/08/25):
At this point you’re probably annoyed about reading of possible fixes while your screen still freezes daily 
(like mine), but there’s more progress/new hope, another ‘race condition’ might get fixed soon.
This time it’s in .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c (which a lot of the journals posted in the AMD gitlab point to as the source in the warning).
A new set of patches has been submitted on 30/07/2025, including one from ‘Aurabindo Pillai’ fixing a dmub access race condition. Since these have been submitted after the release of kernel 6.16, I’m not sure when/where the patches will finally appear, but they’re coming. 