AMD what you need to do next Update make FRCT pre profile games and image sharping make it to go down to 0% and anti-lag need to be work with Chill
and those Known Issues i don't have them never experience those bug
I click install in the upper right corner, once finish. next i install the two sample games. took a while finishing installing. At one point i had to close out the program, restart my computer and finish reinstall. maybe uninstall completely, delete the ue5 folder and restart and try again.
probably can't even run the samples, heard they're pretty powerful. haha, will find out once i wake up.
I don't have those 2 under Engine Versions... That is why I can't download it.. Guess I'll have to reinstall epic games store.
On my 27", if I downsampled from 4K to 1080p, I use 100% driver sharpening AND ReShader FidelityFX sharpening.
For native 1080p, I like 80% sharpening usually.
Then there are some games that look over sharpened very easily, where I do stick with 30%.
People should be warned from this driver. If you own a Zen 3 CPU and a RDNA2 GPU this driver might Overclock your CPU without telling you. See: https://www.tomshardware.com/news/amd-confirms-its-gpu-drivers-are-overclocking-cpus-without-asking
If you really want to install this driver use the Tool Radeon Slimmer and remove RyzenMaster SDK before installation. Otherwise there might be a "bad awakening" if you use any custom profiles/CPU UV etc..
That feature to OC the CPU from the performance tab has been there since driver 21.9.1. The drivers never messed with my PBO or changed anything in the bios...but I never messed with the CPU OC in the Radeon drivers.
Yep that's when it started 21.9.1 to mess with systems, I undervolt and it messed with mine randomly to the point of frustration. Don't know why they didn't remove that section or just RyzenMasterSDK.msi from this driver as a precaution.
No issue after removing that now, tho I used that Radeon Software Slimmer to be sure to remove before install.
That feature to OC the CPU from the performance tab has been there since driver 21.9.1. The drivers never messed with my PBO or changed anything in the bios...but I never messed with the CPU OC in the Radeon drivers.
Problem this time is you don't really have to Mess with CPU OC in Radeon drivers. It's enough when you load up a custom GPU OC/UV-Profile then it might overwrite your Uefi Settings and overclocking CPU that way (without asking nor telling you what it actually does). Though so far it only seems to happen if you have a Combination of Zen 3 CPU + RDNA2 GPU + Loading some kind of GPU Profile. I think this is really problematic and unexpected that your Uefi Settings would get overwritten by loading a GPU Profile.
Problem this time is you don't really have to Mess with CPU OC in Radeon drivers. It's enough when you load up a custom GPU OC/UV-Profile then it might overwrite your Uefi Settings and overclocking CPU that way (without asking nor telling you what it actually does). Though so far it only seems to happen if you have a Combination of Zen 3 CPU + RDNA2 GPU + Loading some kind of GPU Profile. I think this is really problematic and unexpected that your Uefi Settings would get overwritten by loading a GPU Profile.
That might happen part is strange....
I have a 5800X and a 6700XT and I constantly use a custom saved profile for my GPU. It never modified my bios settings for PBO, CO or anything else.
This is from my saved profile, I didn't include the GPU part because that is not relevant. This is how it should look like if you didn't enable any kind of CPU OC from the drivers. Maybe check the profile to be sure there is no saved CPU overclock before loading it.
Trouble is when testing this issue I also tested stock bios settings as well as my custom bios BIOS/PBO settings and it still made my system unstable as soon as I applied a Radeon profile in both scenarios. I genuinely thought I had an issue with my mobo or PSU.
I could run Cinebench/Timespy and Furmark fine but when I tried two particular games they'd always crash at start up, other games ran fine, so made it difficult to point the finger at the games, videocard, mobo or psu for the issue.
Ended up having a BSOD with 22.3.2 tho and luckily others started to speak up about having the same issues now.
I'd say it will be difficult replicating this bug with a lot of configurations, they need to remove the feature in the mean time.
@Romulus_ut3
After a shutdown (with hybrid startup to on as default) the aspm register in pcie for the hadaudio on gpu rx580 is wrong.
It supports only l1 but if you shutdown the pc and start it again it reports also l0.
Before shutdown:
After shutdown:
It supports only l1 but if you shutdown the pc and start it again it reports also l0.
keep in mind, not every register can be properly queried across a sleep cycle, and some require a full reboot after driver update to query correctly.
DDR timings are commonly misreported after S3 resume for example despite operating at the correct rates.
after testing many more Finally with this Driver no Black screen and Flickering But the frame drop with SAM on in Forza Horizon 5 still not fixed !!!!!! i don't know it is AMD or windows or the game problem i just brought new RAM crucial ballistix memory i don't think is the RAM is the problem
Windows 11 update 22000.593
AMD Driver 22.4.1
AMD chipset 4.03.03.431
Bios last update 6024
https://uploads.disquscdn.com/images/9cbc4877d0e8f814ea773361ae89875e8c1c71362c40c0f8fd31d69eaeb7878b.png
after testing many more Finally with this Driver no Black screen and Flickering But the frame drop with SAM on in Forza Horizon 5 still not fixed !!!!!! i don't know it is AMD or windows or the game problem i just brought new RAM crucial ballistix memory i don't think is the RAM is the problem
Windows 11 update 22000.593
AMD Driver 22.4.1
AMD chipset 4.03.03.431
Bios last update 6024
https://uploads.disquscdn.com/images/9cbc4877d0e8f814ea773361ae89875e8c1c71362c40c0f8fd31d69eaeb7878b.png
Such a strange readings on your 6900xt. 34c, 26% usage, 59W? Whats going on there are you limiting the framerate?
After shutdown: