7970 not waking up from sleep

[moriz]

my radeon 7970 does not wake up from sleep. whenever i try, i'm presented with a black screen, occasionally i still have a mouse pointer, but with nothing to click on.

does anyone else notice this problem?

 

[nOOky]

No, I never use sleep. Your 7970 uses so little power at idle that you may want to consider just leaving the pc on. Not that it isn't an issue that needs addressing though.

 

[MrK6]

Yep, it's happened to me before. Are you overclocking or using MSI Afterburner? The culprit for me was MSI Afterburner 2.2 beta 11. After switching to beta 12, I haven't had the problem.

 

[lavaheadache]

try unplugging the monitor and plugging it back in. I have had twice I think.

 

[moriz]

let me clarify: the computer isn't in sleep, but i have the monitors turn off after 20 minutes.

i'm also using MSI afterburner beta 12, and the behavior persists. i also have two monitors, currently one is connected to the 7970, the second one connected to my GT240 physX card. i've tried plugging both into the 7970 with the same results. i've tried plugging the primary monitor into the HDMI and miniDP ports with the same results.

 

[NumericalMethods]

I've had this too. No solution, but another person experiencing the problem. MSI Afterburner beta 11 here.

 

[lavaheadache]

let me clarify: the computer isn't in sleep, but i have the monitors turn off after 20 minutes.

i'm also using MSI afterburner beta 12, and the behavior persists. i also have two monitors, currently one is connected to the 7970, the second one connected to my GT240 physX card. i've tried plugging both into the 7970 with the same results. i've tried plugging the primary monitor into the HDMI and miniDP ports with the same results.

I'm saying to unplug and replug in when it happens

 

[Arkadrel]

I could have sworn there was another thread like this one about the 7970 and sleepmode.
And it was the MSI afterburner software causeing it.

i'm also using MSI afterburner beta 12, and the behavior persists. i also have two monitors, currently one is connected to the 7970, the second one connected to my GT240 physX card. i've tried plugging both into the 7970 with the same results. i've tried plugging the primary monitor into the HDMI and miniDP ports with the same results.

Why use 1 monitor on the GT240 and the other on the 7970?
Try hooking both monitors up to the 7970 and see if that helps, because that seems like something that would give trouble (perphaps not related ones though).

Try pulling out the 240 completly out, and uninstalling the afterburner software, see if problem pursists.

 

[lavaheadache]

I got it and I don't even have afterburner but I am overclocked using CCC

 

[thilanliyan]

Splash some cold water on it. That usually does the trick.

 

[moriz]

I could have sworn there was another thread like this one about the 7970 and sleepmode.
And it was the MSI afterburner software causeing it.



Why use 1 monitor on the GT240 and the other on the 7970?
Try hooking both monitors up to the 7970 and see if that helps, because that seems like something that would give trouble (perphaps not related ones though).

Try pulling out the 240 completly out, and uninstalling the afterburner software, see if problem pursists.

videos cards no longer idle properly when you plug two or more monitors to it. splitting the displays between the two cards means that the 7970 can actually idle, instead of running at 400/1550. it's both for power saving as well as noise reduction, since another side effect is that the 7970 fan never spins down properly if it doesn't go into low power 2D.

i've also tried plugging both monitors to the 7970. same behavior.

 

[djnsmith7]

My MSI 7970 had this same exact problem last night.

 

[Tempered81]

Since youre using Msi Afterburner, change Use unofficial overclocking method variable to 0, 1, or 2. Test your monitors in and out of sleep with these 3 variables. Reboot between each time you change this setting in Afterburner's config.

 

[moriz]

Since youre using Msi Afterburner, change Use unofficial overclocking method variable to 0, 1, or 2. Test your monitors in and out of sleep with these 3 variables. Reboot between each time you change this setting in Afterburner's config.

What do those settings do exactly? I know that setting it to 1 greatly increases the range of clock speeds. What does 0 and 2 do?

 

[Tempered81]

What do those settings do exactly? I know that setting it to 1 greatly increases the range of clock speeds. What does 0 and 2 do?

Originally Posted by Unwinder
Found rather misinformating post about ULPS and overclocking AMD cards with Afterburner at OCN. Not surprized to see guests from OCN with fundamentally wrong understanding after that. A few comments to fix understanding given with that info:


Basically, all third party softwares involving the idle states of slave GPU(s) monitoring will interfere with ULPS and will cause throttling (using Afterburner as monitoring not overclocking).


Incorrect. There is no any throttling, no any interference with ULPS, the only "downside" of using low-level monitoring tools like Afterburner or GPU-Z is seeing no ULPS related zero clocks on the graphs because AMD driver's ULPS activity is invisible to low-level monitoring tools. And monitoring those things through AMD driver like it is done in CCC is deadly ineffective and slow and may cause stuttering in games if using in realtime. If you absolutley want to see active ULPS on the graphs, Afterburner provides a config tweak allowing you to use only driver-level things for monitoring on AMD cards, but it won't give you anything useful besides zeering 0 clocks on the graphs when ULPS enabled slave idles and it will degrade performance (due to the reasons mentioned above, i.e. due to poor optimization of monitoring API provided by AMD driver).


Using Afterburner to OC and overvolt in crossfire configuration, it has to be disabled because it inteferes with ULPS, hence BSOD/crash.


Incorrect again. Overvoltage has zero relation to ULPS, the same applies to overclocking if it is performed via official overclocking interface (ADL) within CCC clock limits. It can safely coexist with ULPS.
The only thing that is incompatible with ULPS is unofficial overclocking path (which is used by default in Trixx and can be optionally enabled in Afterburner). Using AMD's unofficial overclocking path inside Catalyst will indeed result in BSOD, because AMD driver writers cannot make their own unofficial overclocking path to be compatible with their own power saving technology.


Nothing has changed with the release of MSI Afterburner 2.2.0 Beta 12 other than the ability to use PowerTune (Power Control Settings).


Incorrect again. Beta 11 and up introduces /XCL command line switch, which allows extending CCC clock limits and acheive higher clocks while using official overclocking path.


Things might change in future with the 7900 series.


The things will never change because of AMD's stupid politics related to overclocking. For many years they seriously limit CCC clocks and force vendors to stay within really low overclocking limits. Their stupid politics is a direct reason why developers are searching holes like an unofficial overclocking to provide more overclocking freedom to overclockers.


UnofficialOverclockingMode;
•1 = To keep PowerPlay (ULPS) active.
•2 = To traditionally disable PowerPlay (ULPS).
•0 = To temporary disable unofficial overclocking path.


Incorrect again. Alternate overclocking modes have zero relation to enabling/disabling ULPS. They control PowerPlay only.


There's another option to use Afterburner without having to turn off ULPS by disabling "Low Level Hardware Access Monitoring" in Afterburner UI settings. Unfortunately by doing so also disabling the ability to tweak voltage.


And again incorrect. This option does nothing related to ULPS compatibility.

 

[moriz]

sooo... in other words, i should set it to 2 to disable powerplay?

i have a suspicion that this is caused by the zerocore feature, which effectively switches off the card when the screen is off. in this case, it is not waking up properly.

i'll also try disabling unofficial overclocking and use the /XCL switch.

 

[Larnz]

Try it with only the 7970 in for a night, it might be zero core kicking in then not waking up as it detects another card is already active or some strangeness.

 

[VulgarDisplay]

My card does that when overclocked using MSi Afterburner. I have had it happen maybe one time when just using CCC.

 

[kidsafe]

My card does that when overclocked using MSi Afterburner. I have had it happen maybe one time when just using CCC.

Same here. When I remember to bump it back down to 925MHz for long periods of inactivity I don't encounter the bug. For newcomers to this thread, this is not sleep/suspend related. My HDDs spin down and my monitor goes to sleep, but that's all.

 

[moriz]

i've set unofficialoverclocking to 0 and enabled the /XCL command line switch. so far, the computer has been waking up from monitor sleep just fine. fingers crossed and knock on wood and so forth.

 

[Tempered81]

cool good deal

 

[Compddd]

I had this problem when I had a 5870, never could figure out how to fix it.

 

[moriz]

AND.... i just encountered it again. bummer.

looks like i'll have to turn off monitor sleep and go back to the good old screen saver.

 

[MrK6]

I just leave my browser open with a YouTube video up, locks the card in low 3D. I still haven't figured out a rhyme or reason to this, but it's not just Afterburner that causes the issue.

 

[Tempered81]

Afterburner fixes it, its not ab that causes it. It's powerplay breaking itself due to an overclock IMO