BornDownUnder
Member
Note: This is not a OBS Studio specific thread, just trying to lend a hand in troubleshooting someone elses problem. Hopefully devs don't mind as it could help others!
This thread is created as a result of the following post from @Flaim in the AMF plugin thread:
The following thread is created to assist with troubleshooting a base memory clock frequency locking issue, causing display/s to tear/flicker. Anybody that has this issue or has advice/ideas for this issue please chime in with detailed information on steps to reproduce, troubleshooting steps taken, etc. The more the merrier as it can only assist others!
This thread is in regards to AMD cards. If you have a nVidia card with this issue your troubleshooting steps could also help, though particular troubleshooting steps are relevant for AMD software only...
I don't use a multi-monitor setup myself, will try to lend a hand in troubleshooting though...
Doing a bit of forum perusing I would say it most likely is a driver issue, it may however be a registry entry issue via AMD software in setting the 2D clocks too low for the card to handle refresh rates of affected monitors. Though some threads I viewed are dated well before Watt Man and Crimson software came out, so it may also be a hardware issue of sorts.
To look at the issue more closely, it sounds to me like an issue where the card/s just doesn't have enough MHz on the memory clocks to keep the refresh rates of both displays going at the same time, so in turn ends up falling out of sync with one or more displays, causing the horizontal tearing/flickering. As to why the video card/s is locking at base clock frequency on the memory clocks, below are a few base line steps to take and some following questions for troubleshooting:
- Can you make sure you OS and your display software (If you have a display that uses such software, if you do you know the .inf I am referring to) is up to date.
- Can you do a DDU uninstall of the AMD drivers and components for your video cards only, followed by a run of CCleaner for the registry in case any entries are left over.
- Install the latest drivers for your video card/s.
Some questions for troubleshooting:
- What OS are you using?
- What video card/s are you using?
- What are the refresh rates of all displays?
- Are you able to disable then enable the affected display/s via Windows Display settings when the memory clocks are locked, allowing the memory clocks to ramp up speed correctly? If so, does this work after reboot, restart (Turning off then on PC) and cold start (PC turned off overnight, for example)?
- Does this happen for multiple displays or only one? For only one display scenario, does it matter which display you have as your primary display?
- What cables are you using for the displays? Have you tried switching around cable configuration for output to display? i.e- HDMI/DVI + DVI, HDMI/DVI + DP, DVI + DVI, DVI + DP and vice-versa for all displays.
- Have you tried a custom 2D profile via WattMan or via a 3rd party program, such as MSI AfterBurner, EVGA Precision, etc? With and without voltage increase (If overclocking)
- Have you tried not using WattMan at all, not accepting T&C of WattMan? Using only 3rd party programs, such as MSI AfterBurner or EVGA Precision, etc. to control overclocking rates (If overclocking)
- Do you overclock the card/s? Have you tried not overclocking to see if it replicates the issue.
--- If you post in this thread, please be constructive and detailed in information given.
This thread is created as a result of the following post from @Flaim in the AMF plugin thread:
my only concern is that switching between multi-display modes locks the memclock to 150 MHz, which in some cases can only be restored by rebooting in single display mode.
my 100% replication scenario is:
in some cases this can be alleviated by launching a YouTube video in chrome (haven't tried other browsers). then the clock goes up to the regular 1500 MHz.
- set your computer to extended display mode
- turn off computer and second monitor
- turn on computer without turning on the second monitor
- you now get a wonderful horizontal tearing/flickering because of the 150 MHz memclock
this scenario is so vast to me, because my second monitor is a tv which i'm not usually using as a second monitor and don't change the display mode before shutting down.
not even starting with voltage control via wattman...
The following thread is created to assist with troubleshooting a base memory clock frequency locking issue, causing display/s to tear/flicker. Anybody that has this issue or has advice/ideas for this issue please chime in with detailed information on steps to reproduce, troubleshooting steps taken, etc. The more the merrier as it can only assist others!
This thread is in regards to AMD cards. If you have a nVidia card with this issue your troubleshooting steps could also help, though particular troubleshooting steps are relevant for AMD software only...
I don't use a multi-monitor setup myself, will try to lend a hand in troubleshooting though...
Doing a bit of forum perusing I would say it most likely is a driver issue, it may however be a registry entry issue via AMD software in setting the 2D clocks too low for the card to handle refresh rates of affected monitors. Though some threads I viewed are dated well before Watt Man and Crimson software came out, so it may also be a hardware issue of sorts.
To look at the issue more closely, it sounds to me like an issue where the card/s just doesn't have enough MHz on the memory clocks to keep the refresh rates of both displays going at the same time, so in turn ends up falling out of sync with one or more displays, causing the horizontal tearing/flickering. As to why the video card/s is locking at base clock frequency on the memory clocks, below are a few base line steps to take and some following questions for troubleshooting:
- Can you make sure you OS and your display software (If you have a display that uses such software, if you do you know the .inf I am referring to) is up to date.
- Can you do a DDU uninstall of the AMD drivers and components for your video cards only, followed by a run of CCleaner for the registry in case any entries are left over.
- Install the latest drivers for your video card/s.
Some questions for troubleshooting:
- What OS are you using?
- What video card/s are you using?
- What are the refresh rates of all displays?
- Are you able to disable then enable the affected display/s via Windows Display settings when the memory clocks are locked, allowing the memory clocks to ramp up speed correctly? If so, does this work after reboot, restart (Turning off then on PC) and cold start (PC turned off overnight, for example)?
- Does this happen for multiple displays or only one? For only one display scenario, does it matter which display you have as your primary display?
- What cables are you using for the displays? Have you tried switching around cable configuration for output to display? i.e- HDMI/DVI + DVI, HDMI/DVI + DP, DVI + DVI, DVI + DP and vice-versa for all displays.
- Have you tried a custom 2D profile via WattMan or via a 3rd party program, such as MSI AfterBurner, EVGA Precision, etc? With and without voltage increase (If overclocking)
- Have you tried not using WattMan at all, not accepting T&C of WattMan? Using only 3rd party programs, such as MSI AfterBurner or EVGA Precision, etc. to control overclocking rates (If overclocking)
- Do you overclock the card/s? Have you tried not overclocking to see if it replicates the issue.
--- If you post in this thread, please be constructive and detailed in information given.