Any solution for high power consume while multi-monitor use

[BaronVonMehl]

Hi guys,

I just installed my new 390 Nitro and I'm pretty pleased with the performance in my games.
However I just can't justify the high power consume while using a multi-monitor setup.

I knew already, that AMD doesn't downclock the memory when using more than one monitor. But this means, that my system is pulling whole 50 W more and electricity is quiet expensive here in Europe. I'm coding a lot and I just can't stop using my second monitor. Unfortunately I'm thinking about switching back to team green.

So I thought about two possible solutions:

1) Downclock the memory yourself via profile setting.
2) Use the IGPU for my second montior.

Can anyone share some experience or thoughts about this topic?

Thanks for reading!

 

[thesmokingman]

You can set your 2D clocks.


http://www.techpowerup.com/forums/threads/updated-amd-ati-2d-clock-guide.117633/

 

[96Firebird]

It'll probably be easier to power the secondary monitor with iGPU. Some people experience flickering after decreasing the memory clocks under multi-monitor conditions, but some people have had success using that method.

 

[thesmokingman]

It'll probably be easier to power the secondary monitor with iGPU. Some people experience flickering after decreasing the memory clocks under multi-monitor conditions, but some people have had success using that method.

I idle at 300mhz/150mhz core/memory with triple 1080@120hz with zero flicker. I don't use edited powerplay tables though. With AB configured with a proper set of profiles, it will drop clocks to 150mhz as long as you are not running over 120hz on the desktop. I game at 144hz and leave the desktop at 120hz to avoid the clock threshold.

 

[96Firebird]

I don't think the issue exists with monitors that are the same resolution and refresh rates.

 

[thesmokingman]

I don't think the issue exists with monitors that are the same resolution and refresh rates.

Goal post moving? How do you know that's his problem or if it's even a problem? Anyways, this is an old built-in feature. It's so easy to bypass.

 

[96Firebird]

Goal post moving? How do you know that's his problem or if it's even a problem? Anyways, this is an old built-in feature. It's so easy to bypass.

Goal post moving, what? Cute, did you just learn that term and wanted to try it out?

If you for some reason think multi-monitor flickering because of low memory clocks doesn't exist, great. But, it does. Why do you think AMD decided to up the idle memory clocks in such states? For fun?

 

[KingFatty]

I'm using the iGPU right now to watch TV videos full-screen while browsing on my discrete video card.

 

[thesmokingman]

Goal post moving, what? Cute, did you just learn that term and wanted to try it out?

If you for some reason think multi-monitor flickering because of low memory clocks doesn't exist, great. But, it does. Why do you think AMD decided to up the idle memory clocks in such states? For fun?

It's something they have always done. It doesn't mean that you or I need to run 3D mem clocks while idling. And in that case it's absolutely not needed. I've been running triple panels for years w/o ever needing raised mem clocks on the desktop. Hell, I've even written guides on this.

Flickering is something else in most cases. It's usually caused by an app calling for hw acceleration and the gpu gets caught in a powerstate loop. As you can read below, the OP is using multiple apps that use hw acceleration that most likely calls for different powerstates. The black screen and garbled screens ppl get are indicative of powerstate issues. Essentially the gpu gets caught in the wrong powerstate for the accelerated load.

I'm using the iGPU right now to watch TV videos full-screen while browsing on my discrete video card.

 

[96Firebird]

It is NOT something they've always done, read up on the flickering issue back with the 5000 series cards. Their fix was in a driver update to increase the memory clocks when a second monitor was detected.

Thats great that you haven't had any problems, I even said in my post that some people have had success lowering the memory clocks.

Your quoted post was not the OP...

 

[thesmokingman]

It is NOT something they've always done, read up on the flickering issue back with the 5000 series cards. Their fix was in a driver update to increase the memory clocks when a second monitor was detected.

Thats great that you haven't had any problems, I even said in my post that some people have had success lowering the memory clocks.

Your quoted post was not the OP...

5000 series was over half a decade ago lol.

The quote shows what the OP is doing and why it's happening. Technically they are two different issues. One is the raised mem clocks due to multi monitors and the other is the powerstate bug. These are actually two different things ya know?

 

[Mondozei]

Use iGPU, OP. Problem solved.

 

[BaronVonMehl]

Thanks for your help.

I read through some official AMD posts yesterday and they always kept saying,
that there is no work arround and 1500 idle clocks are normal and necessary.
I don't get it, why they don't even suggest to manually change idle clocks ...

I'm now using 300/150 clocks for idle without any problems.
Power consume is not an issue anymore, I am now happy!

 

[tonyfreak215]

You can set your 2D clocks.


http://www.techpowerup.com/forums/threads/updated-amd-ati-2d-clock-guide.117633/

Thank you!!!

My room has been getting much warmer due to this. (HD6970) Been trying to find a way to fix it.

 

[thesmokingman]

Thank you!!!

My room has been getting much warmer due to this. (HD6970) Been trying to find a way to fix it.

Yw. You can also try this method if modifying the 2D tables is a pain. The link below walks you thru setting up profiles and taking control of any app that calls for acceleration. Zone in on the rtss section, that's the program that controls app detection level, ie. what makes AB change powerstates.


The AMD How To Thread


*Just wanted to add that in most situations simply setting up proper profiles will allow AB to drop clocks to 300/150 unless you run greater than 120hz on the desktop or it is a driver bug. Some past drivers locked the mem clocks. In situations like that modifying the 2D tables was the only approach that worked.

 

[Magic Carpet]

If you for some reason think multi-monitor flickering because of low memory clocks doesn't exist, great.

It varies from card to card. I suspect, AMD drivers just aren't good enough in that department to reliably offer multi-monitor experience while retaining low clocks at the same time. I stopped bothering with this (R9 270), and now using igpu to drive my 2nd monitor.