• 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.

The AMD Driver Thread

It's still available (Display Color) it just lives in a different area and uses the OS gamma control. It should have the same functionality AFAIK.

DjVwlJt.jpg

I've already shared the feedback that some users prefer the old method.
 
hmmmm...seem to be getting a lot of subtle screen flicker using these drivers. Didn't happen previously, but since I got these this morning, I'm noticing it no matter if i'm in games, or in desktop. It's just like a backlight flicker.

Edit:

Dropped the panel down to 60hz, no flicker, back to 100hz, no flicker, back to 144hz no flicker now. With Freesync obviously, will just monitor and see what happens.
 
Last edited:
AMDMatt said:
It's still available (Display Color) it just lives in a different area and uses the OS gamma control. It should have the same functionality AFAIK.

DjVwlJt.jpg

I've already shared the feedback that some users prefer the old method.
Click to expand...

I just want the Gamma option back in Additional Settings.. at least put them in the same place as the other Hue, Saturation, Contrast sliders.. why have i got to go into Windows to change this?

Its some stupid huge window with a little slider in it every time i fire it up.. and it only works on the window its sitting in. Which would be the window my game is on..

Jesus, AMD really know how to make something simple, really ****** awkward! :mad:

Im gona look at some 1060's/1070's.. my 7950 needs replacing.
 
MyBrains said:
Core and Memory clocks not clocking down to 300/150 anymore with these new drivers.. its now 300/1250 and idling around 10c higher.

AMD are really starting to annoy me now.
Click to expand...

Running multiple display has always put the memory higher in all my time using AMD. I never once seen multi display configuration run a single GPU speeds.

You 100% sure it was 300/150? Mind going back to that driver and posting results?
 
I've found previously that multiple, different screens attached to the GPU gave me raised memory clocks but switching to multiple, identical screens allowed the memory clock to drop back to the same as it did for a single screen.

Haven't installed the latest driver yet, will try to get to it this weekend and will feed back if my memory clock stays low as it does the for the previous driver or if it gets stuck at high as it did when I was running multiple different resolutions.
 
Confused Stu said:
I've found previously that multiple, different screens attached to the GPU gave me raised memory clocks but switching to multiple, identical screens allowed the memory clock to drop back to the same as it did for a single screen.

Haven't installed the latest driver yet, will try to get to it this weekend and will feed back if my memory clock stays low as it does the for the previous driver or if it gets stuck at high as it did when I was running multiple different resolutions.
Click to expand...

That's because typically most GPUs have two memory clocks, idle and full 3D. When different display timings are used it usually kicks the memory clock up into the next clock state as more resources are required. If the displays and timings are identical, sometimes you get lucky and the memory clock will sit in idle.

This is not a bug and controlled by the bios on the GPU.
 
Yes the clocks were 300/150 running 2 1080p displays with 16.4.2. After trying the latest drivers and getting higher memory clocks.. i reverted back to 16.4.2 and still got higher memory clocks.. even tried DDU and a host of other tricks to get the memory clocks back down.. i give up now as im not spending my friday afternoon p****** about with GPU drivers.

I've decided to run my second 1080p monitor from the HDMI port on my Asus Z170 Pro Gaming board with the third running from the DVI on the Mobo too.. so just 1 monitor from the GPU now.

I guess its time to find out if Nvidia have the same crap going on with high memory clocks, and they obviously havnt got rid of the Gamma settings in the control panel from what i have read.

AMD need to pull their fingers out of their ***** and start leaving things how they were instead of trying to be smart.. if it aint broken then dont try and fix it.

Maybe this is their way of getting me to upgrade my 7950.. as much as i want a Sapphire Nitro 480, i was going to try and hold on to my 7950 for a bit longer and see what Vega brings..

Now i need to consider my options of moving over to the green team, i know Nvidia drivers can be just as bad but for what i want with idle clocks, Gamma settings being easy to access etc.. i have some research to do now..

At least i only need to game from the one display coming from the GPU.

For now im back on 16.4.2 as i cba with wasting anymore time today, i need to go out and do stuff.

Thanks AMD for making my afternoon a pain in the a** and putting me in a somewhat bad mood.
 
That's because they was never 300/150 to begin with :p running more than one display has always put the memory speed higher it's just a fact even nvidia has this.

One display = 300/150
Two or more = 300/1250

Reason even going back not changed this. You must have just missed this and thought you was idling at 150
 
shankly1985 said:
That's because they was never 300/150 to begin with :p running more than one display has always put the memory speed higher it's just a fact even nvidia has this.

One display = 300/150
Two or more = 300/1250

Reason even going back not changed this. You must have just missed this and thought you was idling at 150
Click to expand...

Of course they were 300/150.. do you think im stupid? do you think i dont monitor these things with GPU-Z, Real Temp (GPU Monitoring) MSI Afterburner?

Im pretty OCD with these sort of stats but go ahead and tell me im wrong and that i've been seeing things for the last 4 years.

You obviously think im really stupid and have overlooked all of this but at the end of the day you havnt been on my computer and seen it for yourself.

But you carry on as i guess you're the expert around here and think its impossible for me to have these low memory clocks with 2 monitors running off my GPU.

In the end you're making yourself look stupid.

Sorry that i didnt take a screenshot of my low clocks..

This is all i have to show the low clocks..

3DMark Extreme..

http://www.3dmark.com/3dm/1364350?

3DMark11..

http://www.3dmark.com/3dm11/4508935

They both show the low memory clocks when 3DMark didnt pick up my overclocks.. wouldnt they show 1250 if what you claim is true?

:p
 
Last edited:
I have been running multi Display since owning 7950, 290, and even all showed 1250 on the memory!

Nvidia run a higher core clock once more display are connected.

It's a matter of a fact your wrong on this one sorry don't take it personal :(

You making the GPU work harder something has to give way and single idle clocks are not enough to run more than one display..

They is countless topics out there proving am correct.
 
MyBrains said:
Of course they were 300/150.. do you think im stupid? do you think i dont monitor these things with GPU-Z, Real Temp (GPU Monitoring) MSI Afterburner?

Im pretty OCD with these sort of stats but go ahead and tell me im wrong and that i've been seeing things for the last 4 years.

You obviously think im really stupid and have overlooked all of this but at the end of the day you havnt been on my computer and seen it for yourself.

But you carry on as i guess you're the expert around here and think its impossible for me to have these low memory clocks with 2 monitors running off my GPU.

In the end you're making yourself look stupid.
Click to expand...

Shankly is right about this though. The only way to stop flickering on multimonitor setups is to raise the memory clock. Both Nvidia and ATI do this.

You can use afterburner to downclock manually and then setup a profile with that clock speed.

You might have had something like that setup before and forgot about it maybe? Or there was an issue and you didn't realise it. I know a few people who never noticed the flickering before AMD fixed the problem.
 
MyBrains said:
Yes the clocks were 300/150 running 2 1080p displays with 16.4.2. After trying the latest drivers and getting higher memory clocks.. i reverted back to 16.4.2 and still got higher memory clocks.. even tried DDU and a host of other tricks to get the memory clocks back down.. i give up now as im not spending my friday afternoon p****** about with GPU drivers.

I've decided to run my second 1080p monitor from the HDMI port on my Asus Z170 Pro Gaming board with the third running from the DVI on the Mobo too.. so just 1 monitor from the GPU now.

I guess its time to find out if Nvidia have the same crap going on with high memory clocks, and they obviously havnt got rid of the Gamma settings in the control panel from what i have read.

AMD need to pull their fingers out of their ***** and start leaving things how they were instead of trying to be smart.. if it aint broken then dont try and fix it.

Maybe this is their way of getting me to upgrade my 7950.. as much as i want a Sapphire Nitro 480, i was going to try and hold on to my 7950 for a bit longer and see what Vega brings..

Now i need to consider my options of moving over to the green team, i know Nvidia drivers can be just as bad but for what i want with idle clocks, Gamma settings being easy to access etc.. i have some research to do now..

At least i only need to game from the one display coming from the GPU.

For now im back on 16.4.2 as i cba with wasting anymore time today, i need to go out and do stuff.

Thanks AMD for making my afternoon a pain in the a** and putting me in a somewhat bad mood.
Click to expand...

I run 2 displays, one on DP and the other on HDMI. One driver option I've found that influences idle memory clocks is Pixel format.

On the HDMI Display (DP cannot be changed):

YCbCr 4:2:2 150MHz
YCbCr 4:4:4 150MHz
RGB 4:4:4 (limited) 1500MHz
RGB 4:4:4 (Full) 1500MHz

Does changing pixel format on the HDMI display have the same effect on your system?
 
p5ychonaut said:
I run 2 displays, one on DP and the other on HDMI. One driver option I've found that influences idle memory clocks is Pixel format.

On the HDMI Display (DP cannot be changed):

YCbCr 4:2:2 150MHz
YCbCr 4:4:4 150MHz
RGB 4:4:4 (limited) 1500MHz
RGB 4:4:4 (Full) 1500MHz

Does changing pixel format on the HDMI display have the same effect on your system?
Click to expand...

Mmm nice find I'll after test this, I run my TV hdmi on RGB full. Might explain why I always have higher speeds.
 
p5ychonaut said:
I run 2 displays, one on DP and the other on HDMI. One driver option I've found that influences idle memory clocks is Pixel format.

On the HDMI Display (DP cannot be changed):

YCbCr 4:2:2 150MHz
YCbCr 4:4:4 150MHz
RGB 4:4:4 (limited) 1500MHz
RGB 4:4:4 (Full) 1500MHz

Does changing pixel format on the HDMI display have the same effect on your system?
Click to expand...

I have always used YCbCr 4:4:4 on both monitors.. Im fine with running the other 2 from the Mobo for now anyway but thanks for the suggestion.

Anyway case closed, when i get 2 displays running off the GPU with low clocks again i'll post the evidence, something i never though i'd have to provide.
 
MyBrains said:
Anyway case closed, when i get 2 displays running off the GPU with low clocks again i'll post the evidence, something i never though i'd have to provide.
Click to expand...

You don't have to provide anything. All Shanks was trying to say is that maybe you were mistaken as to what you thought your settings were. They were just trying to help, no more no less. :)
 
You must log in or register to reply here.
Back
Top Bottom