Intel® Arc™ Discrete Graphics
Get answers to your questions or issues when gaming on the world’s best discrete video cards with the latest news surrounding Intel® Arc™ Discrete Graphics.
4177 讨论

Star Citizen Vulkan Crash

ATO3FIX
初学者
35,441 次查看

Clean Windows 11 install + all updates + driver updates.

Driver installed:
(Date: December 26, 2024

Driver Version: 32.0.101.6332 Non-WHQL and 32.0.101.6253 Non-WHQL)

Game: Star Citizen 4.0 Preview


Issue: Switching from DirectX11 to Vulkan results in immediate crashing after loading past the anti-cheat splash screen

Steps: Load the game normally in DX11. Switch to Vulkan in graphics settings, restart the game, reload. After the anti-cheat splash screen, the game will crash. However, extreme rare cases I have seen it load at times where it displays its optimising shaders, but this will also result in a crash.

Specs:

Intel Xeon E5-2690 V4
Intel Arc A750 8GB LE
64GB DDR4 ECC
750W Platinum PSU

Windows 11 is installed on a 500GB SSD drive.

Star Citizen is installed on a 1TB NVME drive that's in a PCI-E Adaptor.

Error displayed in Star Citizen log file:

Exception STATUS_CRYENGINE_FATAL_ERROR(0x2BADF00D) addr=0x00007FFA2EE3837A digest=13556302989d4ec43a77b364423ee9af
Run from internal: No
Is fatal error: Yes
- Fatal error message: [.../DisplaySystem/VulkanDisplay.cpp:609 CVulkanDisplay::WaitForPresentQueueSlot] (0x1) A fence or query has not yet completed. Acquire Next Image Failed
Is reported bug: No
Is GPU crash: No
Is Timeout: No
Is out of system memory: No
Is out of video memory: No

 

0 项奖励
25 回复数
NormanS_Intel
主持人
3,338 次查看

Hello ATO3FIX and Dovador, 

 

Since I haven't received a response from you, I will be closing this inquiry. If you need further assistance, please submit a new question, as this thread will no longer be monitored. 

 

Best regards,

Norman S.

Intel Customer Support Engineer

 

0 项奖励
TheRiddler
新手
2,628 次查看

Hello there,

 

I am replying here because I have a very similar issue with the same game and the same graphics card:

 

Driver installed:
(Date: November 26, 2025

Driver Version: 32.0.101.8331 

Game: Star Citizen 4.5 LIVE


Issue: Starting the game results in fragmented display of the main menu and crash to desktop shortly thereafter

Steps: Start the Game

Specs:

AMD Ryzen 5 5600
Intel Arc A750 8GB 
32GB DDR4 ECC

Windows 11 and Star Citizen are installed on a 500GB SSD NVME drive.
Error displayed in Star Citizen game.log file:

-- GPU CRASH
<2025-12-27T14:33:20.020Z>
GPU crash message: GPU Crash Vulkan ( async Intel - Device Lost - RenderPass [FRAME\Fixed Pipeline] - Consider enabling r_vulkanCPUValidation or r_RenderGraph_ImmediateMode and r_enable_full_gpu_sync = 2. Check gpu_error.log for additional information.

HenryS
初学者
2,539 次查看

Hi there,

 

Id like to add im also experiencing the same problem, since Star citizen 4.5 - Vulkan has become the default, had to manually go into the gamedata to set it to DX11 to be able to start SC

Although it works with DX11 the performance is poor.

 

Im running the following:

 

Ryzen 7 - 5800X

MB - B550 (ReBar on)

64GB DDR4 3200 CL16

Intel ARC B580 (brand new)

 

Did a DDU, installed brand new drivers, tryed it twice just to be sure.

Tryed various settings, tweeks and so on but everytime i switch it to Vulkan it crashes, then i need to manually set SC to DX11 in the localappdata folder in order te be able to start SC.

 

Just as a try, i set the system to low setting and a screen of 720p, still crashes

Game log:

-- GPU CRASH
<2025-12-30T21:53:38.763Z>
GPU crash message: GPU Crash Vulkan ( async Intel - Device Lost - RenderPass [FRAME\Fixed Pipeline] - Consider enabling r_vulkanCPUValidation or r_RenderGraph_ImmediateMode and r_enable_full_gpu_sync = 2. Check gpu_error.log for additional information.

Process Memory Status: 4347MB working set size, 7203MB commit size (7382MB peak), 59348MB left to commit
System Memory Status: 65457MB total physical, 53195MB free physical, 76209MB system wide commit limit

=== Level Profile Statistics===
Frames : 2
Entities : Min: -1 Max: 0 Avg: 0
Component Updates : Avg: 0
Component Events : Avg: 0
Memory (Committed) : Min: 6727.55 MB Max 7366.43
Memory (WorkingSet) : Min: 4433.61 MB Max 4505.27
Buckets : Avg |<16ms|<20ms|<25ms|<30ms|<35ms|<40ms|<45ms|<50ms|slower
CPU (MainThread) : 46.8 FPS (21.4 ms)|50.0%| 0.0%| 0.0%| 0.0%|50.0%| 0.0%| 0.0%| 0.0%| 0.0%
CPU (WholeFrame) : 7.5 FPS (133.8 ms)| 0.0%| 0.0%| 0.0%| 0.0%|50.0%| 0.0%| 0.0%| 0.0%|50.0%


Cloud Imperium Games public crash handler taking over...
Details for StarCitizen.exe (md5=0877da8139c21eb14e5971861c82f4f6)...
* Base of Image : 0x00007FF6EFD70000 (mod), 0x00007FF6EFD70000 (modc)
* Size of Image : 300617728 (diskoh), 300617728 (memoh), 300617728 (mod), 300617728 (modc)
* Size of Code : 125292544 (diskoh), 125292544 (memoh)
* Size of Headers : 1024 (diskoh), 1024 (memoh)
* Size of Initialized Data : 175311360 (diskoh), 175311360 (memoh)
* Size of Uninitialized Data : 0 (diskoh), 0 (memoh)
* Checksum : 0 (diskoh), 0 (memoh)
Saved dump file to C:\Users\*****\AppData\Local\Star Citizen\Crashes\error.dmp (md5=368aded938748fc7b7ebfb2a4662ff1e)
Exception STATUS_CRYENGINE_GPU_CRASH(0x2BADFF59) addr=0x00007FFBD491782A digest=4db9578db3bc834bf401b76a8a25e96c
Run from internal: No
Is fatal error: No
Is reported bug: No
Is GPU crash: Yes
- GPU crash message: GPU Crash Vulkan ( async Intel - Device Lost - RenderPass [FRAME\Fixed Pipeline] - Consider enabling r_vulkanCPUValidation or r_RenderGraph_ImmediateMode and r_enable_full_gpu_sync = 2. Check gpu_error.log for additional information.
Is Timeout: No
Is out of system memory: No
Is out of video memory: No

 

 

At the moment DX11 is a workable patch but its more then likely DX11 wil be discontinued in one of the future updates.

 

Is this something thats in the works?

0 项奖励
TheRiddler
新手
2,533 次查看

Thanks. Yes I also tried changing to DX11 but I'm still getting the issue for some reason...

 

It's good to know its not only the ARC A750 but also other ARC GPUs. 

0 项奖励
Dovador
初学者
2,358 次查看

I had the same issue.


Vulkan no longer works with version 4.5, which is unfortunate because only Vulkan natively supports virtual reality in Star Citizen, and performance with DX11 is very poor.

 

DX11 initially still caused crashes for me as well. In my case, deleting the shader folder and restarting the game with DX11 was enough. After that, I was able to play a full session without issues.

0 项奖励
回复