I got the ASUS STRIX Radeon R9 Fury card. It has a DVI port on it, and I am using that to connect to a Samsung 2343BWX monitor, which has a resolution of 2048x1152 and only has dual link DVI. I have sent an email off to ASUS as well on this, but I want to open the issue here to see if others have similar problems.
To start, I had the resolution at 2048x1152. After about an hour after boot up and being anywhere in Windows 7, the screen shrinks down and has glitched lines in it. After about a minute, the system goes into a blue screen of death and reboots. Sometimes, the computer give beep code errors regarding to GPU failure, but a power down/up cycle resolves that. If I change the resolution while the glitched image occurs, it clears up the screen, and I think recovers the driver.
My current solution was to reduce resolution to 1920x1080. Instead of the screen going weird, the system comes up with "Display driver amdkmdap stopped responding and has successfully recovered." Sometimes, this error comes in a batch of 3 or 4 over 15 minutes. My current leads at this time is either a really faulty GPU, the Fury GPUs are Fury X's that didn't pass for Fury X, and the DVI modification by ASUS has some issues in implementation.
Regardless of my thoughts, I have reviewed the Event Viewer on the most recent attempts over this issue and tried to paste other errors that lead up to the "display driver stopped responding" error into a text file, attached.
CPU: Intel Core i7-3820
Motherboard: Gigabyte GA-x79-UD3
RAM: Corsair 2133MHz 4x4GB
GPU: ASUS STRIX Radeon R9 Fury
OS: Windows 7
Driver: Catalyst 15.7.1
Issue existed in Catalyst 15.7 as well
Currently, I am testing underclocking to check for stability. I will try connecting to my TV when I have time to move my PC this week to eliminate possibility of the DVI port feature having problems. I am posting the error logs to see if someone may recognize the error messages and determine another culprit.
I purchased the same Asus Strix Fury card from Amazon.com, experienced this issue on 2 occasions. On the second occasion, attempted to switch display from LCD to the second display output I use (TV Screen), at which point I got a BSOD and automatic reboot.
I just contacted Amazon who are sending me a replacement card this very moment. Although, coming upon this thread, I have NO idea if the replacement is going to be upto snuff... I can only hope, otherwise that gets sent back, this time for a refund.....
This really sucks, I wish Asus would acknowledge the problem, maybe it just requires a bios update?
BTW, I forgot to mention some important details:
1) The problem is identical for me too. Except, it doesnt happen that often, so far, its consistently been every 3-4 days, and happens at a time when card is not under any stress (just browsing internet. The screen shrinks to a different resolution, and there are moving horizontal lines across it.
2) Resolution is 1920x1080@60Hz. After the first time, I turned on the flag "Alternate DVI Operational mode" in Catalyst settings. Problem still occured. Then I turned on the other flag "Reduce DVI Frequency.." and then the problem happened again literally minutes later.
3) Running Windows 7 x64, Catalyst version 15.7. Also, prior to installing the new card, I did a full uninstall of drivers, and reinstalled it fresh on startup.
I returned 3 fury xs (sapphire, xfx, and then msi) because of this and now the regular fury I have (asus) is doing this. I was using a 390x at one point and had 0 problems like this.
I've used various cables. DVI, HDMI, DP, even a DVI > DP Adapter.
And it has happened on previous driver versions.
Motherboard: MSI Z170A Gaming M7
GPU: ASUS Strix R9 Fury (15.8 beta)
Memory: G.SKILL Ripjaws DDR4 3000 (F4-3000C15D-16GRK)
PSU: be quiet! Dark Power Pro 10 850W (BN603)
OS: Windows 10 64-bit
This is what it looks like. The screen shrinks upward, the bottom third of the screen turning black (or green when on hdmi), random lines all over the place, and then eventually a bsod/reboot.
For anyone interested, I've read that it is a ULPS problem. So I've gone ahead and disabled that through the registry. Will report findings after I've had a chance to use it for a while.
I haven't had it happen since I went through and changed every entry of EnableULPS to 0, however this problem is so sporadic that I'm hesitant to say it actually worked.
Hi Leondre, for me, it happens every 3-4 days so I guess I'd wait a few days to make sure
Also, are there any downsides to disabling this at the registry level aside from increased power usage? Any negative performance issues? I hate having to make manual registry modifications if I can help it ...
Thanks a lot for your input here..