I do hope that Intel can provide a fix for that issue soon. My educated guess is that the cause of the bug is related to how the driver communicates with the DirectX subsystem of Windows as apparently at some point the communication just seems to break down. It should show "12_2, 12_1.", which are the feature levels that are queried by DirectX applications upon start to determine if a compatible GPU is present. On the second tab (display) confirm that the entry "feature levels" is not empty. The feature levels should now be back.ħ) to confirm this click the start button or press the Windows key, type "dxdiag" and press Enter Arc Control will show an API error.ĥ) right click the GPU again and select "activate device"Ħ) the screen will go black again and then return, as the regular Arc driver is loaded again.
It will likely also work with integrated Xe GPUs.ġ) If the error occurs open the Windows device managerĢ) find your Intel Arc GPU (listed unter graphic cards)ģ) right click and select "deactivate device" + confirmĤ) the screen will go black for a moment and then return, as your system switches to the Microsoft Basic Display Adapter driver. I can verify this method for Windows 11, but it should also work in Windows 10 and for all Intel Arc dedicated GPUs (A380, A750, A770). Also reinstalling the same GPU driver only sometimes does the trick.īut I discovered, that there is a simple workaround that is also reliable.
Unfortunately, simply resetting the GPU driver via Win+Ctrl+Shift+B usually does not work. Usually this error is mitigated by rebooting the system, but that takes a bit of time and can also interrupt work. The result is that DirectX dependent games and apps will not run, giving error messages like "couldn't initialize GPU", "no DirectX compatible graphics device found" and the like. Some of us Arc owners are plagued by the problem, that the GPU driver will at some point "forget" its DirectX feature levels.
0 kommentar(er)
