This. It is a known bug at AMD and acknowledged so starting a petition is pretty pointless. They will sort it with or without a petition.
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Change.org petition to add an option to disable power saving in GPU settings
- Thread starter sammarbella
- Start date
This. It is a known bug at AMD and acknowledged so starting a petition is pretty pointless. They will sort it with or without a petition.
- Joined
- 11 Feb 2015
- Posts
- 22
Thanks for replying, i really appreciate it.
I always thought the main reason to buy a dedicated gaming GPU that costs 300-700 euros is to have the best performance playing PC games, not to save a few cents/dollars in the next power bill.
Maybe there are people who buy a Fury X only to play Tetris HD but i guess there are eccentric people everywhere.
The option i would like to see added to Crimson settings is not connected to overclocking:
The goal is to have an option to choice full GPU performance (no downclocking, overclocking) or power saving without the use of third party tools like ClockBlocker or AfterBurner.
Normally a regular customer buying a "Ferrari" don't expect it to be delivered stuck in ECO mode forcing him to hack his way to be able to use it in the normal "PERFORMANCE" mode in this type of cars.
An option to toggle between normal mode (adaptive power saving) and performance mode (maximum performance) could be the best solution to let the customer decide what he/she wants globally or per application (in app profile).
Last edited:
- Joined
- 11 Feb 2015
- Posts
- 22
Done?No.
Maybe medium rare.
The goal is not to reach an AMD employee, it's to be able to avoid downclocking in AMD GPUs without the use of 3rd party tools.
That will be "done" when a driver allowing this will be released, not before.
Permabanned
- Joined
- 12 Sep 2013
- Posts
- 9,221
- Location
- Knowhere
I was having the problem with first gen Crimson and moaned about it all the time in this thread as I spend a lot of time playing the Stalker games and they were suddenly running at 300mhz with an average fps in the mid 20's, However it stopped being an issue for me from the first driver update, I have a Fury pro.
Funnily enough I did a ddu uninstall (my first ever) and installed the new crimsons and have not looked back.
I'm gonna sign though. It should have been an on or off option from the start.
- Joined
- 11 Feb 2015
- Posts
- 22
Leave AfterBurner started on the background monitoring GPU timings while you play games.
You can also look at the AB OSD while playing but this OSD can disrupt in some cases with gaming performance so the background moitoring is the best option.
GPU-Z can also monitor GPU timings in the background if you let it open in the "sensors" tab while gaming.
Both AB and GPU-Z have an option to log to file their monitoring data.
It will be a bit harder to find with for example single 290 card. In general things work very well in games where you are running with 100% gpu usage all the time. But when things get tricky, is that when you reach situation where your gpu usage goes down. There new powertune reacts to it, and downclocks your card to save power. You get these situations in quite many games with fury cards. Or you get these with crossfire setups aswell (maybe even more).
So here's a small example
Frame 1: 100% gpu usage, Clock speed 1100MHz
Frame 2a : 40% gpu usage, Clock speed 1100MHz
At this stage, powertune reacts, and lowers clockspeed to save power.
Frame 2b: 60% gpu usage, Clock speed 733MHz
Frame 3a: 100% gpu suage, Clock speed 733MHz
At this stage, powertune should react, and increase clockspeed higher.
Frame 3b: 100 gpu usage, Clock speed 733Mhz.
What went wrong? Powertune "forgot" to increase clocks, when more power is needed. This doesn't happen always, and is quite hard to find a real reason why it doesn't work same way always.
But overall, it's nice feature, when it works properly.
Soldato
- Joined
- 28 May 2007
- Posts
- 10,220
With the Nano i think it's all to do with temperatures. So it's probably changing frequencies to lower the temp. Try the fan at 100% and see if this persists and if not it's just reducing frequency to control temps.
Most likely related to the power saving issue/bug in question here. I get the same issue on my 390X in WoW - fps dips related with core clock speeds dropping for a few seconds.
Sooner it's fixed the better.
Think it's a bit of both, under water my nano runs fine at 1100 no issue. Does not drop a beat once I add + 50% to power limit.
Yeah but if he hadn't of started the petition, we would be talking about it and this entire thread would have only been a couple of posts long and wouldn't of caught the attention of AMDMatt.
Signed.
I'm an Nvidia user at the minute but freedom of application is important, and there's no reason I won't go AMD in the future.
Why anyone is slating the OP I do not know, he had a problem, he voiced it and has attempted to take further steps to achieve change.
People are so quick to condemn sometimes, does it make them feel big I wonder?
I'm an Nvidia user at the minute but freedom of application is important, and there's no reason I won't go AMD in the future.
Why anyone is slating the OP I do not know, he had a problem, he voiced it and has attempted to take further steps to achieve change.
People are so quick to condemn sometimes, does it make them feel big I wonder?
Caporegime
- Joined
- 8 Jul 2003
- Posts
- 30,063
- Location
- In a house
Yup, i can't use any of the Crimsons because of it, cores are just up and down, up and down constantly, going as low as 350, making my frames plummet, don 't have any problems with pre-Crimsons, cores go to 1040, and stay there, its ridiculous, as i said before, they should have left the drivers alone, and just updated the CCC, as they were fine, now they've ****** em right up, theres loads of problems with them, this bouncing clock issue is just one of them.
- Joined
- 11 Feb 2015
- Posts
- 22
Well there is not "forgot" in here.
This process (downclocking to power save) is not instant, there is always a delay between low power state/timing and the recovery of high power state/timing and performance delivery.
The problem with an aggressive power saving feature like this and real time gaming is it downclocks the timing (and voltage) as soon as it detects GPU usage is under a threshold (% and/or time?) and only raises back AFTER it detects GPU usage is over that threshold again.
If this process occurs once each 10 minutes, i.e only when a game script launch a cutscene there is no much trouble but if this process occur very often, even a few times per second, it's a complete mess for performance (FPS) and stability (sustained frametimes).
The best scenario is a single GPU without V-sync or framelimiter and not CPU and/or DX11 bottlenecked.
In a multicard scenario the problem is way worst even without limiting factor like V-sync or framelimiter.In this case a higher resolution helps a lot to sustain a GPU usage and high power state.
For me it's also about freedom of choice and the inconvenience to be forced to use 3rd party tools to get the GPU performance was abe to deliver without them before Crimson (November 2015).
My 290X Lighning CFX works pretty right now with AfterBurner locking timings and forcing constant voltage when AMD drivers provide a predifined and working CFX because since 16.1 there is no way to modify CFX profiles or enable them globally.
It could be nice to turn maximum performance mode on right in drivers like nvidia users do since ages.
You defined this MONTHS old problem very well.
Last edited: