-
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
- Thread starter LtMatt
- Start date
Soldato
Definitely a problem with running the latest drivers and 144hz. Not sure if it's tied in with freesync, but I keep getting this flicker issue, could almost describe it like a strobing flicker. Goes away when I drop hz down to 120hz weirdly.
Soldato
Not had any flicking here Tony.
Soldato
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.
Hey you know if people are gona just treat me like im a noob then i'll just go to a different forum when it comes to GPU's. I've been running the same setup for over 4 years and you're gona say i might be mistaken?
Jesus Christ these forums.
Just in case some of you might have missed it..
I've had 2 identical Samsung Syncmaster SA350 monitors running off the same AMD 7950 GPU for over 4 years.
Im not even gona carry on with this because im obviously mistaken.
What is wrong with you? Nobody was rude and nobody treated you like a noob. You are such a whiny, moaner. Go to another forum, because you won't be missed here.
When two monitor are plugged into a GPU the memory clocks rise and the temps increase. That's the default state of operation for both AMD and Nvidia GPU's. It's done to combat flickering.
If you had memory clocks of 150 with dual monitors before this then there was something else keeping them down.
1. Some kind of profile was setup in Afterburner to downclock the card and that was overwritten or stopped working with the drivers you installed.
2. You read the clocks wrong.
3. There was a bug in you system and for whatever reason your previous driver installs hadn't applied the fix that raised memory clocks when dual monitors were attached.
If you are correct and the clocks were 150 for the past 4 years, then I am leaning towards 3. Because when you re-installed the older drivers they still raised the memory clocks, which is what the drivers are supposed to do!!!
There is a pretty simple solution too, and if you had come in and asked for help instead of complaining, moaning and ranting about been treated like a noob maybe your after noon wouldn't have been spoiled.
Download afterburner, make a new 2d profile, lower the memory clocks until you notice flicker. Apply profile. Done. Both Nvidia and AMD owers have used this fix.
Soldato
After 4 hours on Arma 3 i had a quick look at how to fix it, and i fixed it..
Am i mistaken now?
[/IMG]
@AMDMatt.. thanks for the help.. what you said earlier helped me fix this issue even if i am still using Cat 16.4.2.
Cheers mate
Am i mistaken now?
@AMDMatt.. thanks for the help.. what you said earlier helped me fix this issue even if i am still using Cat 16.4.2.
Cheers mate
Soldato
KK I stand corrected I never seen this before.. Would be nice to find out why its working like this for you and not others.
Soldato
Melmac and Shanks, I know you both mean well, but in this case you're wrong.
If you're running different monitors, then you will get raised idle memory clocks.
If your screens are the same model (and sometimes even just the same size and resolution if you're lucky), your GPU will downclock to fully idle memory clocks.
I've run different cards and multi-monitor resolutions for years, and always with higher idle memory clocks and hence slightly higher idle temperatures. When I switched to 3 IIyama E2409HDS screens and a fourth Packard Bell Viseo243D a couple of years ago (so all 1920x1080 60Hz screens), I got lucky and my cards are able to run these without needing to raise idle memory clocks. It's been this way for every driver for the past few years, and presumably going back further.
Here's a screenshot I've just taken of my system with 4 monitors attached and the GPU running at 300/150. If it's not clear, the memory clock is the 4th graph down on the left hand side.
It's not common, and most people with multi-monitor setups will get raised idle clocks, but it is possible to run multi-monitor with fully idle clocks if your screens are identical (enough) and you're lucky.
If you're running different monitors, then you will get raised idle memory clocks.
If your screens are the same model (and sometimes even just the same size and resolution if you're lucky), your GPU will downclock to fully idle memory clocks.
I've run different cards and multi-monitor resolutions for years, and always with higher idle memory clocks and hence slightly higher idle temperatures. When I switched to 3 IIyama E2409HDS screens and a fourth Packard Bell Viseo243D a couple of years ago (so all 1920x1080 60Hz screens), I got lucky and my cards are able to run these without needing to raise idle memory clocks. It's been this way for every driver for the past few years, and presumably going back further.
Here's a screenshot I've just taken of my system with 4 monitors attached and the GPU running at 300/150. If it's not clear, the memory clock is the 4th graph down on the left hand side.
It's not common, and most people with multi-monitor setups will get raised idle clocks, but it is possible to run multi-monitor with fully idle clocks if your screens are identical (enough) and you're lucky.
Soldato
Melmac and Shanks, I know you both mean well, but in this case you're wrong.
If you're running different monitors, then you will get raised idle memory clocks.
If your screens are the same model (and sometimes even just the same size and resolution if you're lucky), your GPU will downclock to fully idle memory clocks.
I've run different cards and multi-monitor resolutions for years, and always with higher idle memory clocks and hence slightly higher idle temperatures. When I switched to 3 IIyama E2409HDS screens and a fourth Packard Bell Viseo243D a couple of years ago (so all 1920x1080 60Hz screens), I got lucky and my cards are able to run these without needing to raise idle memory clocks. It's been this way for every driver for the past few years, and presumably going back further.
Here's a screenshot I've just taken of my system with 4 monitors attached and the GPU running at 300/150. If it's not clear, the memory clock is the 4th graph down on the left hand side.
It's not common, and most people with multi-monitor setups will get raised idle clocks, but it is possible to run multi-monitor with fully idle clocks if your screens are identical (enough) and you're lucky.
Seems because its rare for people to have matching monitors I just thought it always works this way. Good to know and I learn something new! This should be in AMDs FAQ for eyefinity
Soldato
Crossfire and Freesync issue possibly then.
It's not common, and most people with multi-monitor setups will get raised idle clocks, but it is possible to run multi-monitor with fully idle clocks if your screens are identical (enough) and you're lucky.
Thanks Stu, but, AMD Matt did say that sometimes if you are lucky and have the same screens your mem clocks will be 150. I had two identical screens, but had high memory clocks. It's just like some people never had flicker when running dual monitors but some people did.
But, he got it sorted, so guess it's all ok now
I've already raised this issue of Wattman being limited to 2050Mhz on the RX 480 under 16.7.3 internally. That is not expected behaviour so it can be considered a bug. Roll back to 16.7.2 if you want up to 2250Mhz.
With this new control, fan minimum speed, target speed, and min acoustic limit can now be set. Minimum, is the absolute minimum the fan can run at. Target, is target maximum fan speed, the fan will run at if temperature level is not above target. Min Acoustic Limit is the clock limit/threshold where acoustics can be violated.
Soldato
Melmac and Shanks, I know you both mean well, but in this case you're wrong.
If you're running different monitors, then you will get raised idle memory clocks.
If your screens are the same model (and sometimes even just the same size and resolution if you're lucky), your GPU will downclock to fully idle memory clocks.
I've run different cards and multi-monitor resolutions for years, and always with higher idle memory clocks and hence slightly higher idle temperatures. When I switched to 3 IIyama E2409HDS screens and a fourth Packard Bell Viseo243D a couple of years ago (so all 1920x1080 60Hz screens), I got lucky and my cards are able to run these without needing to raise idle memory clocks. It's been this way for every driver for the past few years, and presumably going back further.
Here's a screenshot I've just taken of my system with 4 monitors attached and the GPU running at 300/150. If it's not clear, the memory clock is the 4th graph down on the left hand side.
It's not common, and most people with multi-monitor setups will get raised idle clocks, but it is possible to run multi-monitor with fully idle clocks if your screens are identical (enough) and you're lucky.
I seem to recall when I ran 2 of the Samsung 750D monitors (the 1080p 120Hz ones) that the idle clock speeds idled at whatever the 2D clocks where. Then when I got my new monitors that don't match resolution or refresh rate the idle clocks went up and I put it down to the differences.
Maybe in future Shankly should be a little slower to claim things as fact as in this case it clearly wasn't fact.
I can understand MyBrains frustration at being told he can't have seen what he knows he'd seen because someone else hadn't ever seen it and so it couldn't be possible. I think it was also uncalled for for melmac to tell him to leave and go to another forum because of this frustration.
Still, glad MyBrains got this fixed, I can imagine how annoying this might have been. It's not a big deal, but annoying if you can see no reason for the change in behaviour.
Thank you. although I'm still unsure with
"Min Acoustic Limit is the clock limit/threshold where acoustics can be violated"
What is a violation of acoustics?
I think what I'm saying is, what will happen if I set it 300 compared with 1300.
Pity about the Mem OC bug. I was enjoying messing around. Can't really roll back as I'm enjoying the improvement with Rise of the Tomb Raider
What Shankly said was right though. It's not guaranteed to have low clocks when two monitors are connected. The default behaviour is to raise the memory clocks. See AMD MAtt's post above.
I told him to do what he said he was going to do. There was no call for him to call Shankly stupid and rude. He didn't come in here looking for help, he came in to rant and rave and then take out his frustrations on people trying to help him.