yes ... i tried to turn it off and on again...
There is a problem with Radeon Instinct MI25 MxGPU device. For more information, search for 'graphics device driver error code 43'
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 ?
Can you stop the machine once and start again and try?
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.
Not sure if it was related, but I had Windows 10 Pro instead of Enterprise in the Virtual Machine.
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.
Experiencing the same issue here, code 43 using official drivers linked by Microsoft
- 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?
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.
Got my answer. NVv4 are not supported to run on 1909 or 2004.
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
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?
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.
Sign in to comment
Sort by: Most helpful
Sorry for the inconvenience you are facing.
Are you still seeing the issue?
If you are still facing the issue, I request you to open a support request to get the issue checked by Azure Support.
Sign in to comment
Same here. I got it to work. But after restarting the VM its stopped working again.
I get the same following instructions from https://learn.microsoft.com/en-us/azure/virtual-machines/windows/n-series-amd-driver-setup
I have tried
- Windows 10 EVD - Build 1903 (sku: 19h1-evd)
- Windows 10 - Build 1809 (sku: rs5-pro-g2)
Same. Once I de-allocate the VM, I lose the ability to use the video device. Any attempt to revive it has been unsuccessful. I've tried to rebuild the VM with the same disk image, no luck. I've tried changing sizes, no luck. When I start a fresh VM and fresh drive, it's inconsistent if the driver and video device come online successfully. I've ended up spending $80 on just trying to get a new instance up and working again, then spend time to re-apply any of my own environment to it.
I was completely unable to get the Radeon card working with Win10 at all, but was able to get it to work win Win Server 2016 in Azure. However after reboot (or update?) it seems to have the same issue:
Windows has stopped this device because it has reported problems. (Code 43)
@mechgt Apologies for the issue you are facing. We are investigating the code 43 related issue with the GPU and working on a fix. We expect the fix to be ready in the next few days. Please do not install any driver that is not published by Microsoft. If you have not done already then please open a support case so we can notify you when the fix is rolled out.
I posted in the Azure forums with a few more details on my situation:
Since it's been a few days any any update on resolving this issue? And is there anything that should be referenced when opening a support case since this appears to be a known issue?
Sign in to comment