search

IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
113 stars 3 forks source link

Vulkan vkCreateDevice fails with ERROR_INITIALIZATION_FAILED #299

Closed Neo-Zhixing closed 1 year ago

Neo-Zhixing commented 1 year ago

Checklist [README]

Game / Application [Required]

Quake II RTX; All Vulkan games with VK_KHR_acceleration_structure enabled

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Intel Core i9 10850k

Graphic Card [Required]

Intel Arc A770 (16G)

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

aaa.txt

Description and steps to reproduce [Required]

With VkAccelerationStructureKHR extension enabled, vkCreateDevice fails with return value ERROR_INITIALIZATION_FAILED.

image

Steps to reproduce:

  1. Clone this repository: https://github.com/EmbarkStudios/kajiya , or download Quake II RTX on Steam, or any other repository that uses Vulkan Ray Tracing
  2. On startup, Vulkan device creation fails with VK_ERROR_INITIALIZATION_FAILED
  3. If you remove VK_KHR_acceleration_structure from the list of enabled device extensions, device creation succeed.

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

N/A

Device / Platform name

No response

Crash dumps [Required, if applicable]

Validation layer output: terminator_CreateDevice: Failed in ICD C:\Windows\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_be925909b882ee5b\.\igvk64.dll vkCreateDevice call vkCreateDevice: Failed to create device chain.

Save game

No response

Arturo-Intel commented 1 year ago

Hi @Neo-Zhixing ! I try to use the kajiya repo but i found an compilation error that is already reported in their github site, so I went and use Quake II rtx instead.

If I run the game with the defaults I can play the demo with out any error, so I assume VkAccelerationStructureKHR extension is not enabled or is not used.

I went to the video options and under ray tracing API there are 2 options with "KHR": image image

I can play normally with both options maybe I am missing something

Can you share your game configuration? --r2

Edit: https://youtu.be/0o1F3my-tfo

Neo-Zhixing commented 1 year ago

@Arturo-Intel It seems that this was caused by a conflict between the Intel driver and the AMD driver. Uninstalling the AMD Driver made it work for me.

I used to have an AMD 6600XT GPU and when I replaced it with the Intel Arc A770, the AMD driver wasn't uninstalled.

It's not clear which driver caused the problem exactly. It would be great if you can help reproducing this problem. Just install both GPUs at the same time and see if that causes any problems. I will also report this problem to AMD as well.

Thank you for your time helping with this!

Arturo-Intel commented 1 year ago

oh ok, so there was 2 drivers installed (Intels and AMDs) I am glad you found the root cause. That's why we recommend to use DDU to do a cleanup before installing a new driver/GPU.

BTW that option was the one to enable the VkAccelerationStructureKHR structure?

Neo-Zhixing commented 1 year ago

Technically both would be using VkAccelerationStructureKHR . In my case Quake RTX just crashes on start saying "Failed to create a Vulkan Device".

I would not say that "having two drivers installed" is the root cause tho. One (esp graphics programmers) might want to install both GPUs on the same system for easy testing. The AMD integrated graphics on the Ryzen 7xxx series might also conflict with Intel although I wasn't able to test it out.

Afaik Intel Arc and NVIDIA cards coexists on the same system without issues.

Let's keep this issue open in case other people run into this problem in the future.

Arturo-Intel commented 1 year ago

I will create an article to share this to the community, also I need to confirm if having both drivers (AMD + Intel) should behave like this.

I would not say that "having two drivers installed" is the root cause tho. We can change this to drivers conflict, how about that?

One (esp graphics programmers) might want to install both GPUs on the same system for easy testing. Normally you want to tests your apps/games in a normal environment (only one driver installed) because is what your customer mostly will have.

Arturo-Intel commented 1 year ago

@Neo-Zhixing if the issue is not present we can close this issue, we will document this in our knowledge database.

Neo-Zhixing commented 1 year ago

Thanks. I will close this for now.