RX 590 DX12 Issue

[DymonddZ]

Hello folks,
I'm new to this forum as an LTT viewer since about 2 years. And as it's stated in various videos here are some pretty smart guys that can probably give me a hint of what is causing this issue.
I formerly posted this on /r/AMDHelp (hence this text formatting, little bit edited and updated) but there has no one answered until now.

 

Computer Type: Desktop, Custom built 3 months ago

GPU: Sapphire RX 590 Nitro+ Special Edition, 8GB GDDR5 currently on stock, before that Vcore: 1600 MHz @ 1,175V and vRAM set to 2200 MHz @ 1.0V (issue persists, no matter if OC'd or not; see Troubleshooting section below)

CPU: AMD R5 2600, currently at stock settings, before that it was 4.0 GHz @ 1.4V, LLC Level 3 (yea I know, silicon lottery is not on my side) (same here: issue persists, no matter if OC'd or not; see Troubleshooting section below)

Scythe Mugen 5 Rev. B CPU Cooler

Motherboard: MSI B450 Gaming Plus

RAM: 2x 8GB G.SKILL Ripjaws V 3200 CL16 (F4-3200C16D-16GVKB) now at stock, before that setup as XMP rated (again here: no matter if running at stock, A-XMP or manually setting frequency, timing and voltage)

PSU: Thermaltake Berlin 630W

 

Operating System & Version: Windows 10 18362.239 (currently latest)

GPU Drivers: Issue persists on both latest drivers: 19.7.2 optional and 19.5.2 stable, same issue

Chipset Drivers: 1.07.07.0725 (AMDs latest chipset driver from amd.com)

 

Background Applications: None 3rd party, fresh windows install

 

Description of Original Problem: I started the benchmark from userbenchmark.com, where the graphics benchmark portion threw out an error. Using Passmark, every test went fine except for DX12 test, where it would start and run the first few seconds of the 3D benchmark when it suddenly crashes. But i was able to see the first 2 or 3 seconds of the rendered benchmark (Aircraft flying through space I guess). Benchmarking has never been an issue since I built my rig and oh boy.. I did a lot of them :D DX12 Titles even worked on this this rig The last working benchmark was like 1 or 2 weeks ago. I even noticed that in the running benchmarks like DirectX11, OpenGL and so on, the coil whine of the GPU is far less audible than before (never missed it so much). Maybe related to lower fps or physical damage OR lower fps because of physical damage.

 

Troubleshooting: Tried literally everthing: Reboot, reset WattMan, used DDU in safemode, tried stable display driver 19.5.2 after that, changed BIOS switch position on GPU (from gaming to silence), set CPU and RAM to stock in BIOS, cleared CMOS, and finally formatted and reinstalled my whole windows 10 installation (sigh). My BIOS is already latest (7B86v19). Nothing seems to help.

 

So my question is: can this DX12 error be software related as it seems to be the only problem according to PassMark. Is it even possible for a hardware failure to cause such an issue? I read that many people had issues with directx12 in the past so maybe I just have to wait for driver updates. As the new Ryzen and Radeon Navi Parts are out now and we heard of BIOS issues, maybe thats related? Against that, my system worked fine before on same BIOS version.

Thanks in advance guys :) I will happily follow every hint :)
 

[Jurrunio]

what if you use an older driver? 

[DymonddZ]

12 hours ago, Jurrunio said:

what if you use an older driver? 

I just ran DDU again and tried the 19.4.1 driver from april, no success.

I have forgot to mention that in 90% of the cases in which I install a new graphics driver, I get a weird graphical glitch: either I get a far over exaggerated red, pink, green, blue or yellow (the colors I remember, I think it's RGB + the first additions of these colors) screen where I can barely see the "restart now" button of the driver installer or normal colors just gets a little bit paler. This even happens at the same odds when I plug in my second monitor, but deactivating the monitor in device manager and reactivating it fixes the issue. This happened ever since I got the card and was a bitter taste, but never stopped me from playing all my favorite games (including DX12 mode in "Sniper Elite 4") at the fps I expected from various tests on the internet.

[Jurrunio]

Maybe cable?

[DymonddZ]

Just now, Jurrunio said:

Maybe cable?

2 different HDMI do the same and my second monitor is DVI. I doubt that all 3 cables are broken, especially the DVI is new and thick.