6.6.5 AMD Drivers after 18.9.3 Breaking System

Quote

I found a few other cases of this when researching solutions

Can you provide the links?

Reviewing my prior searches I only found - 

Which is pretty similar to symptoms I am seeing.   I thought I had found more, but was searching "amd rx 580 unraid driver black screen"

Any update on this?  It's been a month, and I am experiencing some issues in a game and want to try updating my drivers.  

Any Updates?

A few days ago, I found myself attempting to try out Unraid on my HP z820 (dual E5-2690 with 128GB, 2x 1TB SSD, 5x 3TB SAS drives, and 3x RX 480 4GB). The USB mapping was an eye opener in order to pass keyboards and mice for 3 separate Windows 10 x64 Pro VM's. After that and mapping which RX 480 was which in the hardware mapping, I was able to get all 3 VM's working. They load the RX 480 driver from Windows 10 Updates, but anytime I attempt to load any AMD drivers, that system will go black and CPU cores will be constantly pegged out. At this time, I have to boot the VM as a VNC VM instead of using the RX 480. This seems to be the only way I can get to a point to use the DDU and uninstall the AMD driver. I have been trial and erroring and working my way backwards from the current release in hopes that I do find something that works with AMD driver features. Even the 18.9.3 drivers caused issues with my setups. 

I've spent most of the day trouble shooting this issue and it seems that it is just the graphics driver, as opposed to the audio, and other drivers/utilities in the AMD driver packages.  

 

One thing I did notice is that when it goes to install the newer drivers, I hear the windows, new device found/installed noise, and then I hear a device disconnected noise and the system (guest) goes unresponsive.  I am not seeing cores being pegged at this time.  

 

I did however have my host become unresponsive while trying to reboot my W10 X64 Pro guest.  I had to force shutdown the host, which caused issues with some dockers and network settings, which I have since resolved.  I did take a diagnostics once the system came back up after the forced shutdown, but before I noticed network and docker issues.  

 

Currently I am stuck using 4 month old drivers, which will only get older, and possibly cause issues.  

 

This issue is getting closer to becoming a show stopper for how I use unraid, and it'd be nice to know that something is being done about this.

 

I have attached the new diagnostics in case that shines more light.

tower-diagnostics-20190207-1424.zip

Due to the lack of support/response on this five month old issue, albeit only reported two months ago, I have migrated off unRaid for my hybrid VM solution.  

 

I am very disappointed in the level of support I received for this, which has tarnished my view of unRaid.  

 

I understand troubleshooting issues, isn't straight forward, and that the architecture unRaid is built on isn't fully designed by the unRaid team, but 1 response in two months is unacceptable.

 

I am closing this report, as I have exhausted my troubleshooting methods (upgraded to 6.6.6 as well, which I hadn't shared) and have simply abandoned using unRaid for the purpose I intended when I purchased it.

 

Changed Status to Closed