GPU: ASUS TUF Gaming Radeon RX 6900 XT OC
Mobo: Asus ROG Crosshair VIII Hero
CPU: Ryzen 9 3950X
Memory: 16GB @3200MHz
Monitors: Left main: 27" 2560x1440 secondary right 24" 1920x1080
Radeon Adrenalin ver. 21.3.1 locked my left hand monitor (2560x1440) to 640x480 and it is impoosible to change the resolution.
My right hand monitor with 1920x1080 works.
My first attempt to install ver. 21.3.1 over powered the my left hand monitor with almost everything so there was not possible to even se anything on the monitor, it went bonkers. The right monitor however worked as befofre.
I had to revert to ver. 21.2.3 and then everythings is ok.
There are some seriuos trouble with the latest driver 21.3.1
Stay away from this update and I think AMD should revoke this from their website.
Best regard from Sweden.
Solved! Go to Solution.
solve the issue for my on FI27Q
downgrade frimware F03
then install new driver
can used DP 2k on 165Hz hope another can fix it to....
Not tried it was wondering if the risk is worth the reward worried about bricking the monitor not sure if something goes wrong what damage it could cause.
"We all want to use the newest drivers."
Yup, I wanted that too, but since 21.3.1 some weird things happens with DWM and full screen optimizations. I consistently get black screens when I try to ALT+TAB (or WIN+NumKey) and my PC becomes unusable untill I restart.
21.3.1 was stable for me, untill I hit weird 640x480 bug. Now rolling back (again) to 21.2.3 and I have no other choice than waiting.
"Try the new driver that just came out. 21.8.1"
Patch notes does not say anything about ongoing problems, like black screens and timeouts. I guess I will stick to the 21.2.3.
I don't know. That is what an AMD rep suggested to try and let him know if it fixed the issue.
But I already have the issue fixed with 21.7.2 so someone else will need to try it.
Another power outage and I'm back to the 640x480 with 21.7.2
How is this happening I have no idea?! OMG
Managed to fix again: Using 21.8.1 now
But this issue will probably return in the next power outage.
I was also having the the issue with F03 suddenly stopped working and again locked my monitor to 640x480 a month and a half back, even though it had been working perfectly after I downgraded from F05 to F03 earlier in the spring.
My fix to this then and its still working (re-loading the F03 for the second time):
1. Load a previous/older working AMD GPU s/w driver.
2. Connect the DP cable and the USB cable.
3. Important: download the latest OSD-Sidekick s/w and use that when You reload the F03 firmware.
also at the same time re-download F03 firmware and use that.
4. Restart the computer and download latest AMD GPU driver https://www.amd.com/en/support
5. Right click on the file (for ex.) "non-whql-radeon-software-adrenalin-2020-21.8.1-win10-64bit-aug10.EXE" and Run as Administrator.
6. Restart the computer when the Adrenalin s/w is fully installed.
7. check that the Windows is using the AORUS-FI27Q monitors full capacity at 165Hz
Hope this will work as it did for me.
Best regards from Sweden
Ps. My system:
Monitor: Gigabyte AORUS-FI27Q
Mobo: Asus ROG Crosshair VIII Hero (wifi) with latest BIOS 3801 with Agesa V2 PI 22.214.171.124 Patch C.
CPU: AMD Ryzen 9 3950X
RAM: 2x8GB at 3200MHz
GPU: ASUS TUF Gaming Radeon RX 6900 XT OC (Under volted).
I have also enabled above 4G decoding and SAM (Smart Access Memory) in BIOS.
I still have issues with AMD Adrenalin GPU driver timeout in some games especially AC Valhalla, but that is for another thread - not in this thread.
Do you just install the new driver over the old one without DDU or uninstalling the old one?
Is there a difference in installing via .EXE file or via Adrenalin Software?
I did not use DDU at all, just installed the new Adrenalin s/w driver over the previous one, but I always right click on the file and then choose 'Run as Administrator'.
And I have always been doing the Adrenalin s/w installation via .EXE files.
Did you have any power outage after that?
Wondering if it will still work, since I've basically done what you did but without taking the monitor cord out, etc..
DID NOT WORK
JUST ANOTHER WASTE OF TIME
I HATE AMD AND GIGABYTE FOR THIS
AND WHO PUT THE "SOLVED" UNDER THIS TOPIC? THIS IS NOT SOLVED DEAR AMD!!!
Had a response from gigabyte let’s see if it works.
Please click here to download the latest version F08 firmware and try again. Please flash the firmware via OSD Sidekick.
Feel free to contact us again anytime if you have any feedback or need any support from us.
update from F03 to F08 Just work on me for the "current driver"~ then? there is still problem guys? still don't know about next update~ Lol
I solvet the 640x480 Problem for me:
I downloaded F05
Installed F05 over my F03
Then installed F03 over F05
Then updated my Graphic Driver to actually Drivers (normal Windows, no SafeMode)
Then, i never toggle the switch on the power strip xD
And it works, shut down computer, start computer, everytime WQHD
Hi, in Your link above for F08, is that a beta version?
I must wonder since Gigabyte has not yet officially put it up on their support site: https://www.gigabyte.com/us/Monitor/AORUS-FI27Q/support#support-dl-firmware
My monitor runs just fine with F03 - at the moment - so I think I will be waiting until Gigabyte update their official support site with latest firmware.
Best regards from Sweden
Every time I turn on the monitor I get screen flickering. Need to change to 144hz and revert back to 165 hz to fix it.
But each time monitor goes to sleep you need to do it again. I do it 10 times a day. This is so stupid.
@Titan777 "There's no need for 10 bit. Basically ZERO difference in windows."
Please explain so I can fully understand this.
I have this Gigabyte AORUS-FI27Q in which I have the option with the latest drivers to activate 10-bit 4-4-4, which I did (of course connected via DP to my ASUS TUF Gaming Radeon RX 6900 XT OC) and You are saying that this is meaningless?
Best regards, from Sweden
Yes, it is meaningless also since the monitor can't get bright enough.
You need at least 1000 nits for real HDR.
Try and play with HDR on and off and see if you notice the difference.
Anyways I rather play with 165hz and not 120hz.