Gigabyte RX 580 (4GB) and Radeon 18.6.1: Sudden Problems?

Scott Sullivan

Honorable
Apr 18, 2013
34
0
10,530
Edit: Clean install drivers, rolled back to 18.5.1. Not sure if the original problem is present or not, since it happened randomly before. All is well, but the colors still get washed out whenever I change settings in a game.

CPU: Core i5-3570k (3.4GHz)
GPU: Gigabyte Aorus 4GB RX 580
Motherboard: Gigabyte Z77X UD3H
Memory: Corsair Vengeance 8GB (GDDR5)
Hard Drive: WD Black 1 Terabyte (for games)
Hard Drive: HyperX 3K 120GB SSD (for OS/Some Programs)
Radeon Adrenalin Software: 18.6.1

I received my card on Saturday (purchased Wednesday). I tested it with Furmark for ~20 minutes, with no artifacts, acceptable temperatures ranges, etc. Typically I avoid long-term stress testing, and opt for a short 15-20 minute test, and then real world experience in games I'm actually going to play.

World of Warcraft had some minor shadow flicker/behavior. Chiefly the shadows would turn off if you looked at them from the proper angle, or sometimes 'flicker' if you could angle it right. There was also a minor issue where the skybox turned white and back to normal almost instantly, but never happened again. The shadow thing has occured before with other cards, so I'm not sure what it 'means' except for maybe being an issue with the game itself. The skybox never flicked before.

However: Fallout 4 has given me a minor issue I'm concerned with.

I left the computer (and game) running for about 10 minutes while I went to grab a package from the mail man. In this time, the screen 'turned off', as though it put the display to sleep (the computer is set to do this, but I've not seen it happen in a game before). I could not wake the screen.

When I put my head phones on, the games sounds were still playing, but very choppy with pieces missing. It sounded like the computer was struggling with the game somehow.I pressed the power button once, and the monitor came back on, but the game was still very laggy.

I tried to open the Task Manager to see if something had happened in the background. I found that Radeon Settings: Host Application, and Windows Explorer were chewing up ~30% CPU, and 25% CPU respectively, and everything was very laggy. I could not engage the start menu properly, while it would open, I couldn't select anything. I had to Ctrl-Alt-Delete and then power down from there.

I'm unclear if this is a hardware issue or a software issue. I can get an exchange on my card through NewEgg, but I don't want to do that if it's a software issue. I'm also not even sure what started the issue in the first place, because I wasn't there.

Could someone offer some advice?

Edit:

I forgot to add that gamma settings are not consistent. When I change graphics settings in a game, it becomes 'washed out' like the gamma is wrong. Alt-tabbing fixes this immediately, but it's a bit disconcerting as to why it happens.


Edit:

Checked Event Viewer.

5:53:55 PM
Faulting application name: dwm.exe, version: 10.0.17134.1, time stamp: 0xf5178e97
Faulting module name: dwmcore.dll, version: 10.0.17134.112, time stamp: 0x76be26a7
Exception code: 0xc00001ad
Fault offset: 0x00000000001ce082
Faulting process id: 0x1044
Faulting application start time: 0x01d40b140d1e10d6
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\dwmcore.dll
Report Id: 3867117f-844e-4eb3-ade8-58fa300f575c
Faulting package full name:
Faulting package-relative application ID:

5:57:06 PM

Faulting application name: dwm.exe, version: 10.0.17134.1, time stamp: 0xf5178e97
Faulting module name: dwmcore.dll, version: 10.0.17134.112, time stamp: 0x76be26a7
Exception code: 0xc00001ad
Fault offset: 0x00000000001ce082
Faulting process id: 0x19c8
Faulting application start time: 0x01d40ccf39244daa
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\dwmcore.dll
Report Id: b4f961e3-bc09-4241-8a2c-e49c3229cdab
Faulting package full name:
Faulting package-relative application ID:

I also have:


The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: Radeon RX 580 Series)

The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 1, Primary display device ID: Radeon RX 580 Series)

The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: Radeon RX 580 Series)

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Fallout4.exe (4756) consumed 4427882496 bytes, RadeonSettings.exe (8148) consumed 713105408 bytes, and firefox.exe (6220) consumed 318963712 bytes.

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Fallout4.exe (4756) consumed 4427882496 bytes, RadeonSettings.exe (8148) consumed 713576448 bytes, and firefox.exe (2512) consumed 314605568 bytes.



I don't have any personal idea what this means, if I'm being honest. It *looks* like "RadeonSettings.exe" was consuming more VRAM than Fallout 4. Which... sounds like a drivers issue, I guess, yeah. Unless I'm wrong?

I'm going to try to install an older set of drivers. Is there a way to use a different version of "RadeonSettings.exe" or should using older drivers manage that on it's own?
 

Scott Sullivan

Honorable
Apr 18, 2013
34
0
10,530


I believe it's a Corsair 750 PSU. I'll have to open it and check.

It was just supporting a Radeon 7950 without issue, which I understand is supposed to be much more power hungry (it used 2 4 pin connectors, vs the RX 580's single 4 pin and single 2 pin.)

Edit:

Corsair GS 700. 50 less than I expected, but I had expected 700 to be more than enough.

 

Scott Sullivan

Honorable
Apr 18, 2013
34
0
10,530
Update:

Completely removed all drivers and software, full restart (power off, then on), and installed 18.5.1 instead of 18.6.1. So far it's working.

I'm unsure of what happened to Fallout 4 (where the whole computer locked up), but the gamma changing issue from WoW (changing any graphics setting made everything slightly washed out) has resolved itself.