samuelmorris
Supreme [H]ardness
- Joined
- Dec 20, 2010
- Messages
- 5,506
If the video is hardware accelerated, you will remain at video clocks, not full clocks, if the video is open. This applies to all the recent radeons, including the 6970s.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
If you mean me, it has ALWAYS been a problem for the 5800's, and it was effecting the 6X00's as well.Not quite sure why there is a problem for you..
If you mean me, it has ALWAYS been a problem for the 5800's, and it was effecting the 6X00's as well.
Sounds like they might have fixed it for the 6X00's but left out the 5800's
As long as your memory clock stays full-speed in all power states, you shouldn't see any flickering on secondary monitors.I tested this on my 6950, hooked up a second monitor and tried it. There is no flicker when you run dual monitors, the clocks switch up automatically. This is with overdrive enabled or disabled.
What happens if you update to 11.2? Shansoft and ocellaris say 11.2 managed to fix the issue on their 6X00 series cards.But, the issue with playing hardware accelerated video on one screen and trying to play games on the other screen is still there. I am using the 11.1a driver though.
As long as your memory clock stays full-speed in all power states, you shouldn't see any flickering on secondary monitors.
You'll only see flickering if the memory clock changes (temporary flicker while the new value is set), or if the memory clock is set too low (constant flicker) as is what happens when you enable ATi Overdrive on some cards.
For example, the idle speed on an HD5850 will drop from 400 / 1000 all the way to 157 / 300 if you enable ATi Overdrive on Catalyst 11.2, causing constant flickering. You have to use a profile hack to work-around the issue and trick Catalyst Control Center to idle the card at the correct clockspeeds again WITH Overdrive enabled.
What happens if you update to 11.2? Shansoft and ocellaris say 11.2 managed to fix the issue on their 6X00 series cards.
I can confirm the UVD clock issue remains unresolved on HD5800 series cards.
Woah, that did make it significantly better. Added it to the driver bug thread as a possible work-around. Thanks!
If that's true of the entire 6X00 series, and not just your sample, then they've finally fixed the issue that started this mess in the first place on the 5800 series.I can confirm that there is no flicker at all using dual monitors on a 6950. I have turned on and off video, played games, turned overdrive on and off with no flickering even when the memory clock changes.
If that's the case, then AMD is in a serious pickle.This issue must be hardware/bios related that they fixed in the 6xxx series cards and can't fix in the 5xxx series cards without releasing bios upgrades.
[snip]
Of course if this works, then you know it's a hardware/bios problem with the 5xxx series cards and it will never be fixed with a driver release.
Found my first issue tonight. Fired up Crysis and was getting 19 fps. WTF??
I tinkered around with everything and ran the benchmark and was only getting 20 or so. I uninstalled then reinstalled 11.2, restarted my computer and I seem to be ok now. Im actually a little over where I was I think. With 10.10e I was getting 55 fps average in the Crysis benchmark with everything on High and 2x AA. Now Im up to 58 average. Not a huge deal but still pretty sweet to pick up 3 fps just off a new driver.
Not sure what happened there but glad it was an easy fix.
I used the Crysis benchmark program. It runs 4 loops, the 1st of which is always lower. The average fps of the previous run is displayed in the upper left of the screen. I take the fps of the last 3 runs then average them together. Was 58.6 or something like that.
FRAPS always works in my version. Try hitting F12. That toggles screen position and off. If no luck, hit the "~" key and type "r_displayinfo 1". This will turn on a bunch of info in the upper left of the screen which includes fps. It gets pretty annoying after a while but you can see what your frame rates are.
For example, the idle speed on an HD5850 will drop from 400 / 1000 all the way to 157 / 300 if you enable ATi Overdrive on Catalyst 11.2, causing constant flickering. You have to use a profile hack to work-around the issue and trick Catalyst Control Center to idle the card at the correct clockspeeds again WITH Overdrive enabled.
can you elaborate more on this hack ?
Symptoms:
If you use anything but default clockspeeds in ATi Overdrive, your card begins to idle at 157MHz core, 300MHz RAM. These clockspeeds are too low, and can cause secondary monitors to flicker or corrupt in other ways.
Causes:
Appears to be a conflict between PowerPlay idle states, the newly defined idle clocks assigned by the driver (AMD's attempted fix for another driver bug), and ATi Overdrive causing those newly defined idle states to be overridden.
Workaround:
1. Catalyst Control Center > Graphics > ATi Overdrive.
2. Set your desired 3D clockspeed and apply it.
3. Your card's idle clock will have dropped to 157 / 300. Ignore that for now.
4. Options > Profiles > Profile Manager.
5. Name the profile "OverdriveFix" and make sure "ATi Overdrive" is checked.
6. Save the profile, but DO NOT apply it yet.
7. Navigate to "C:\Users\%username%\AppData\Local\ATI\ACE\Profiles\"
8. Right click "OverdriveFix.xml" and select "Edit"
9. Edit the clockspeeds and voltages as appropriate for your card.Code:<Feature name="CoreClockTarget_0"> <Property name="Want_0" value="40000" /> <Property name="Want_1" value="55000" /> <Property name="Want_2" value="72500" /> </Feature> <Feature name="PowerControl_0"> <Property name="Want" value="0" /> </Feature> <Feature name="MemoryClockTarget_0"> <Property name="Want_0" value="100000" /> <Property name="Want_1" value="100000" /> <Property name="Want_2" value="100000" /> </Feature> <Feature name="CoreVoltageTarget_0"> <Property name="Want_0" value="1000" /> <Property name="Want_1" value="1038" /> <Property name="Want_2" value="1088" /> </Feature>
10. Save the XML file.Code:<Feature name="CoreClockTarget_0"> <Property name="Want_0" value="40000" /> <Property name="Want_1" value="60000" /> <Property name="Want_2" value="85000" /> </Feature> <Feature name="PowerControl_0"> <Property name="Want" value="0" /> </Feature> <Feature name="MemoryClockTarget_0"> <Property name="Want_0" value="120000" /> <Property name="Want_1" value="120000" /> <Property name="Want_2" value="120000" /> </Feature> <Feature name="CoreVoltageTarget_0"> <Property name="Want_0" value="1063" /> <Property name="Want_1" value="1063" /> <Property name="Want_2" value="1160" /> </Feature>
11. Catalyst Control Center > Options > Profiles > Activate Profile > OverdriveFix
12. If only the core clock changed, repeat step 11 (apply the profile again).
13. Your idle clockspeed should now be correct. 400/1000 for the HD5850, or 400/1200 for the HD5870.
Official fix:
None. Unresolved as of Catalyst 11.2