There is a problem with Radeon Instinct MI25 MxGPU device. For more information, search for 'graphics device driver error code 43'

Wolfgang 31

I have Windows 10, 1909 installed on a NV4as_v4
After installation of the AMD Driver according to https://learn.microsoft.com/en-us/azure/virtual-machines/windows/n-series-amd-driver-setup
I get the error:

There is a problem with Radeon Instinct MI25 MxGPU device. For more information, search for graphics device driver error code 43

any ideas ?

jakaruna-MSFT 596 Reputation points Microsoft Employee

2020-03-30T13:14:19.48+00:00

Can you stop the machine once and start again and try?
Robert 1 Reputation point

2020-05-04T21:29:12.71+00:00

Hi, I was stuck with the same error code. What worked for me is ignoring the installer from the official Azure account. I used the Microsoft Windows® 10 (64-bit) for Workstation link.

https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q1

Not sure if it was related, but I had Windows 10 Pro instead of Enterprise in the Virtual Machine.
Vijay Kanchanahalli 36 Reputation points Microsoft Employee

2020-05-12T05:00:44.993+00:00

Hi, Only AMD drivers published at https://learn.microsoft.com/en-us/azure/virtual-machines/windows/n-series-amd-driver-setup are supported on NVv4 VMs. If you hit the error code 43 issue on NVv4 VMs then please open a support case and our teams will assist to fix the issue. Please do not install any drivers published on the AMD portal.
Mike Dawson 11 Reputation points

2020-05-20T17:51:05.4+00:00
Experiencing the same issue here, code 43 using official drivers linked by Microsoft

Several thoughts:

This is an especially bad issue if it happens unpredictably; you could have 100 users with Radeon Instinct VDI desktops and some users could have broken drivers, and not know why their graphics software is running poorly. They may get a bad impression of GPU-Accelerated VDI in general if this happens

I feel like you should credit back everyone's account that spent time running these instances while this problem is occuring

Why do you still offer them for sale if this has been a reported issue for months?
Koffski, Joshua A 6 Reputation points

2020-05-22T16:46:25.727+00:00

So I put this question out on https://learn.microsoft.com/en-us/azure/virtual-machines/windows/n-series-amd-driver-setup as well, but does anyone know if these drivers even support 1909 and 2004? The article only recommends 1903 as the latest. I'm assuming so since it's just the normal GA drivers, but wanted to verify.
Koffski, Joshua A 6 Reputation points

2020-05-22T21:04:40.86+00:00

Got my answer. NVv4 are not supported to run on 1909 or 2004.
Mike Dawson 11 Reputation points

2020-05-22T21:06:49.177+00:00

FYI I notified AMD
They said they found the issue and gave MS the fix, they will be validating it and will deploy it during the next scheduled maintenance cycle
Koffski, Joshua A 6 Reputation points

2020-05-22T23:13:10.84+00:00

That's fantastic news thank you for sharing the outcome. Did they mention if any action would be required on the administrators behalf such as patch or hotfix, or will this be something they modify directly at the VM Resource level?
Vijay Kanchanahalli 36 Reputation points Microsoft Employee

2020-05-23T00:14:54.023+00:00

We expect to rollout the fix starting next week. The fix is at the Azure platform level and will require customers to stop/start the VM so the VM comes up again on the updated infrastructure.

11 answers

Victor Bustos 1 Reputation point

2020-06-08T15:58:36.127+00:00

Hi Vijay i would like to know if the Issue/Bug was resolved over the NV4v Virtual Machines?
Do I have to do something new? like upgrade the GPU drivers?

Please tell us, we are wating for the feedback,
Thanks...
Please sign in to rate this answer.
Vijay Kanchanahalli 36 Reputation points Microsoft Employee

2020-06-08T18:31:00.513+00:00

@Victor Bustos , We have finished the rollout across all regions. Customers need to verify that only the supported drivers published by Azure are installed on the VM. No other change/action is required by the customers.

Koffski, Joshua A 6 Reputation points

2020-06-08T18:35:18.247+00:00

If users have outstanding servers affected by the issue should they simply reboot, disable\enable the adapter, stop\start the VM, etc.? Or will the OS auto-correct the error while running?

Vijay Kanchanahalli 36 Reputation points Microsoft Employee

2020-06-08T22:11:17.087+00:00

If the VMs are using the Azure specific GPU driver version published here then there is no action needed. Any VM running a GPU driver downloaded from external sources will now see Code 43(by design) to block unsupported driver versions. Customers will need to uninstall the unsupported driver using the AMD cleanup utility and then install the driver published by Microsoft.

Vijay Kanchanahalli 36 Reputation points Microsoft Employee

2020-06-08T22:23:14.333+00:00

The version of the driver certified for Azure is 26.20.13025.4034. Any other version needs to be removed and replaced with 26.20.13025.4034

jmol11 1 Reputation point

2020-12-25T21:01:09.287+00:00

Looks like driver certified for Azure has change to 26.20.13025.17004 - I have this in Win10 Ent v1809 and it was working under Citrix but when I stopped deallocated the machine and powered on after 3 days the card is not identified via directx when in Citrix session, it now falls back to the Citrix indirect display adapter. Really need AMD working - to test I created a new VM same as other one that was working before and its working. They are the same, only difference I see in directx is driver date - the one that used to work read as 9/23/2020 but now says 9/24/2020. The new one and working one says 9/23/2020 - very weird. Please help.
Sign in to comment