Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#6 AMD Video driver crashes (and recovers) repeatedly

pending
nobody
None
2012-10-08
2011-07-14
No

Recently, Album Art Downloader has become completely unusable for me.
When I just start AAD, it may happen that every bit of UI (windows, other programs, everything) but the mouse pointer freezes. After 4 seconds of being able to move the pointer around, it also freezes, my screens go to black and several seconds later I get the message that my display driver has stopped responding but has succesfully recovered.
The same sometimes happens when I use the file browser to search for files, but the absolute killer is trying to download album art for several albums. That is an absolute freezefest, with my display driver stopping for 10 seconds with 2 seconds of usable interaction time in between until I've either exited every last window of AAD or AAD finishes all its actions.

Although I am completely baffled as to how any application can have such a debilitating effect on my OS, I would be satisfied with this specific problem going away (as I do love the awesome functionality of AAD!).

No other application shows similar behaviour and apart from when using AAD, the display driver message is extremely rare for me.

On:
Windows 7 x64 Ultimate (fully updated)
AMD Catalyst 11.6 on an Radeon 5770
XUI 0.40.1 (but 0.39 did the same)

Discussion

  • Also: switching my UI to Windows Classic (non-Aero) does not change the situation.

     
  • It seems that changing my driver setting from forced (4x) Anti-Aliasing to 'Use Application Settings' resolved this issue.
    I will continue using AAD and report back later.

     
  • Confirmed.
    Used AAD several times without freezes with 'Use Application Settings'.
    After finishing my work, I re-enabled the forced anti-aliasing restarted AAD (again) and the freezing behaviour returned immediately.

     
  • AlexVallat
    AlexVallat
    2011-07-14

    Thank you for reporting this. It sounds like a bug with the way AMDs forced anti-aliasing interacts with WPF. Could you try running some other WPF application and see if you get the same issues? (a bit of software that comes with windows: "All Programs\Accessories\Windows Power Shell\Windows PowerShell ISE" uses WPF, or you could install something like http://www.metrotwit.com/)

    Given the types of issues you are seeing, though, I strongly suspect that there will be nothing I can do about it from AAD, and your best solution will be to turn off forced anti-aliasing for AAD either globally, or by making a specific profile for it.

     
  • Well, the PowerShell ISE doesn't show the same behaviour. At least I haven't been able to reproduce it.
    I'll keep an eye out whether Catalyst 11.7 changes anything.

     
  • charlesr
    charlesr
    2011-07-28

    Just a quick note that the same behaviour occurs on my PC.

     
  • AlexVallat
    AlexVallat
    2011-07-28

    charlesrr, do you have forced anti-aliasing set in the Catalyst control panel? If so, could you try restoring that to "Use Application Settings", or set AlbumArt.exe specifically not to have forced anti-aliasing?

     
  • Update:
    - Installed Catalyst 11.7: no difference.
    - Installed AAD 0.41: no difference.

    Perhaps the following is of any use:
    Sometimes (usually the first time) instead of the 'display driver has recovered' notification, I get a dialog stating that the display driver was unable to set the refresh rate on the DisplayPort device.
    Again, such errors are extremely rare for me, but perhaps my monitor setup is influencing the issue:
    AMD 5770 HDMI --> Pioneer receiver --> TV
    AMD 5770 DisplayPort --> Passive DP-to-VGA converter --> 1280x1024 LCD
    AMD 5770 DVI --> 1920x1080 LCD

    Perhaps charlesrr can comment on his monitor setup to determine whether this is indeed a factor in this issue.

     
  • AlexVallat
    AlexVallat
    2011-08-01

    That's weird, it shouldn't even be possible to change the refresh rate without being a full-screen application. Needless to say, there's nothing in AAD that is intentionally dealing working with the screen at that low level, it doesn't try and set refresh rate or resolution or anything like that.

    The only thing I can suggest, if disabling forced anti-aliasing for AAD doesn't work, and if you are comfortable editing the registry, is to try turning of hardware acceleration for WPF. You can do this by adding the value:

    [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics]
    "DisableHWAcceleration"=dword:00000001