was playing borderlands with everything maxed out. noticed the FPS never went 120fps using the overlay stats, no vsync, no fps limit. i used the advanced features in the control panel to set the lowest gpu speed to 2501mhz and boost set it self to 2601mhz, which is fine. what im seeing is that the low GPU load from borderlands is keeping the gpu speed at 800 to 1000mhz. searched around which lead me doing the control panel gpu speed setting in advanced options. is this tied to the drivers some how? as i also followed another suggestion, i forget the option in the control panel that messes gpu load? i also messed with afterburner and other programs that allow control over the video card. what i want is to get it to run at its actual clock speed, not based on load. that is when im gaming, nothing i have tried or find out online is making a difference. this also goes for 55.3avg fps in Wolfenstein new order. while i cant see the overlay, it disappears, checking the control panel shows that low fps. i read there is something in the driver level for that, it has been a issue even on the 5x00 cards or last gen. there was a mention of the driver team sticking to popular titles on steam for priority to fixe/tweak. i hope that isnt true and hope that someone can help.
i see people talking about needing more cpu but that doesn't make sense. A gpu on the low/mid range side shouldn't need a lot of cpu to be maxed out. while i have intel 11th gen parts waiting to be put together, i want to see if i can get this issue with the gpu resolved. otherwise im going to be forced to send it back to newegg, it just cost to much to have these issues.
head off questions,
i used DDU more then once to remove drivers, went from NV to AMD. when i downloaded these drivers is 21.12.1, i have not tried the new ones that just came out.
PC specs
run all my games at 1080P
i5 9600k@ 4.4ghz
2x8GB DDR4-3600(running at 3600)
that should cover it since im using Samsung 860 evo drive. plenty of free space on the drive(s), fixed ms swap space to 3xram size.
**guess i could give the new 22.1.1 driver a try
