DX11 feature level 10.0 is required to run the engine.

[cybergrimes]

Hello,

I've had a recurring issue since building with an A380 a couple months ago. It seems like it loses knowledge of it's DX11 capabilities system wide. Games don't start, Emby Media Server can no longer transcode and VNC Server does not allow DirectX tracking to capture screen.

Restarting the PC will allow everything to work correctly until eventually the issue returns. Sometimes I can run the DirectX Diagnostic Tool included with Windows and everything goes back to normal without a restart. This does not always work, restarting is the best bet.

07:12:29.725 ffmpeg version 5.1-emby_2023_04_28 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC
07:12:29.725   built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
07:12:29.725 Execution Date: 2023-05-13 07:12:29
07:12:29.730 [AVHWDeviceContext @ 0000018c80f8dcc0] Using D3D11 device 8086:56a5 (Intel(R) Arc(TM) A380 Graphics).
07:12:29.743 [AVHWDeviceContext @ 0000018c80f8dcc0] Failed to create Direct3D11 device (8007000e)
07:12:29.743 Device creation failed: -1313558101.
07:12:29.743 Failed to set value 'qsv=dev1:hw,child_device=0,qsv_use_dx11=1' for option 'init_hw_device': Unknown error occurred
07:12:29.743 Error parsing global options: Unknown error occurred
07:12:29.744 EXIT

thanks,
Matthew

[ItzAlif]

I have the same issue while starting valorant. It rarely happens. I'm an arc a750 user. I just restart my pc and till now, it solved the problem every time.
Hope Intel fixes it with their future updates.

[Hugo_Intel]

Hello cybergrimes

Thank you for posting on the Intel® ARC™ Graphics Communities. I am sorry you are experiencing issues with your Intel® Arc™ A380 Graphics Direct11 support capabilities.

Let's try uninstalling the current driver using Display Driver Uninstaller. Once uninstalled and while in safe mode update to the latest driver version 31.0.101.4335.

If the issue persists, please share with us the following information:

• Is Driftland the only game triggering the issue?
• Create a System report following these instructions. Only use the instructions under Intel Graphics Command Center (Intel GCC): Report for Intel® Graphics Drivers
• Right after the issue happens, create a report from the DirectX Diagnostic Tool and attach it as well.

Best Regards,

Hugo O.

Intel Customer Support Technician.

[cybergrimes]

---

@Hugo_Intel wrote:

If the issue persists, please share with us the following information:

• Is Driftland the only game triggering the issue?
• Create a System report following these instructions. Only use the instructions under Intel Graphics Command Center (Intel GCC): Report for Intel® Graphics Drivers
• Right after the issue happens, create a report from the DirectX Diagnostic Tool and attach it as well.

---

I don't play a lot of games on this PC so I only know of Driftland at the moment, like I mentioned though it affects other software when this happens. I can't replicate the issue easily but I'll get a DXDIAG report next time it occurs. Attached the GCC report for now.

I'll also update the driver now. Fwiw this has happened on the two most recent driver releases since I got the A380.

thanks!

[Hugo_Intel]

Hello @ItzAlif

Thank you for posting. Please share with us the same information from the above post and in addition, create and share the log file from the Intel® System Support Utility in order to get your hardware configuration.

Best Regards,

Hugo O.

Intel Customer Support Technician.

[Hugo_Intel]

Hello cybergrimes

Thank you for letting us know. Please share the Dxdiag log once you are able to create it as it will help us to find the source of the issue.

There is a newer driver that has been just released version 31.0.101.4369, let's try updating to this version which includes several fixes. do the installation with Display Driver Uninstaller as well.

In addition, I would also recommend updating your BIOS to the latest version provided by your motherboard manufacturer to allow for full compatibility their latest version seems to be F37c.

Best Regards,

Hugo O.

Intel Customer Support Technician.

[Hugo_Intel]

Hello cybergrimes

I hope you are doing fine. 

Were you able to check the previous post? 

Let us know if you still need assistance. 

Best regards,  

Hugo O.  

Intel Customer Support Technician. 

[cybergrimes]

Hi Hugo, yes I saw the previous response. I have updated the driver already. The BIOS update you referenced is for the full ATX version of my motherboard, however I have the mini ITX version which is up to date (same release date just different version#)

Anyway I am still watching for the error to return but it’s nice outside so I am not sitting down to play much lately.

Thanks!

[cybergrimes]

@Hugo_Intel 

I was able to recreate the error this morning and captured the DxDiag output right away. See attached. Thanks!

[Hugo_Intel]

Hello cybergrimes

Thank you for the information and for sharing the report with us. We will check this issue internally with our team and will get back to you as soon as I have an update.

Best Regards,

Hugo O.

Intel Customer Support Technician.

[Hugo_Intel]

Hello cybergrimes

After checking all the information that you have provided so far, we have determined that this is a known issue that we are currently working to come up with a fix in which the Operating System no longer detects the GPU DirectX features. At the moment there is no estimated time for the fix to be released but it will be through a driver update and should be released soon.

At the moment when this issue happens you can go to Device Manager> Display Adapters from there locate the ARC GPU, right-click on the ARG GPU, click on disable, and once disabled right click on the ARC GPU again and re-enable it. This has proven to work as a workaround for several customers. Please look forward to future driver updates that should contain the fix for this issue. In case you want to get an update later on you can reference the Bug ID 14018789847 in future threads or in case you contact us directly.

Best Regards,

Hugo O.

Intel Customer Support Technician.

[Hugo_Intel]

Hello cybergrimes

I see there are no further questions related to this topic so we will be closing this thread. Please look forward to future driver updates that should contain the fix for this issue. Once again was want to thank you for reporting this issue to us.

Best Regards,

Hugo O.

Intel Customer Support Technician.