Game start crash

Hello, I have an issue with starting the game. When I try to launch it, the game crashes immediately and shows an error message, offering the option to report the error. It also creates a log, which I will send. I have already tried reinstalling the graphics card drivers. I tried installing an older version of the drivers. I have tested all possible graphics card settings to launch the game, but nothing helps. All other games work fine, so the issue must be related specifically to Crossout.I couldn’t find anyone with the exact same issue as mine. Most people had problems where the game launched but then crashed while playing, but I can’t even get it to start.

Here is log:
17:04:02.472 00 | gfx: CreateDevice() adapter=“NVIDIA GeForce RTX 4060 Laptop GPU”
17:04:02.473 00 | gfx: Adapter ids vendorId=0x10de deviceId=0x28a0
17:04:02.476 00 | gfx: Adapter driver date: 3.12.2024
17:04:02.476 00 | gfx: Adapter driver version: 32.00.15.6636
17:04:02.476 00 | gfx: Adapter dedicated video memory: 8343519232
17:04:02.476 00 | gfx: Adapter dedicated system memory: 0
17:04:02.476 00 | gfx: Adapter shared system memory: 7355494400
17:04:02.476 00 | gfx: Ultra low quality forced via command line
17:04:02.798 00 | gfx: NvApi initialized. Interface version: NVidia Complete Version 1.10. Driver version: 56636. Build branch: r566_31
17:04:08.125 00 | gfx: Driver features:
17:04:08.125 00 | gfx: DriverConcurrentCreates: true
17:04:08.125 00 | gfx: DriverCommandLists: true
17:04:08.125 00 | gfx: MapNoOverwriteOnDynamicConstantBuffer: true
17:04:08.125 00 | gfx: MapNoOverwriteOnDynamicSrv: true
17:04:08.126 00 | gfx: Gpu counters activated
17:04:08.126 00 | gfx:
17:04:08.126 00 | gfx: ------------ Autodetecting defaults ------------
17:04:08.126 00 | gfx: OS: Windows 10 Home 24H2 (10.0.26100.2605) x64
17:04:08.126 00 | gfx: CPU: 13th Gen Intel(R) Core™ i5-13500H
17:04:08.126 00 | gfx: CPU cores: 12
17:04:08.126 00 | gfx: CPU threads: 16
17:04:08.126 00 | gfx: RAM: 14029 MB
17:04:08.126 00 | gfx: Memory Load: 42%
17:04:08.126 00 | gfx: Physical: 13.7 GB total, 5.8 GB used, 7.9 GB available
17:04:08.126 00 | gfx: Page File: 22.2 GB total, 11.2 GB used, 11.0 GB available
17:04:08.126 00 | gfx: Log disk free space: 430.3 GB (45.16%)
17:04:08.126 00 | gfx: GPU: NVIDIA GeForce RTX 4060 Laptop GPU
17:04:08.126 00 | gfx: VRAM: 7957 MB
17:04:08.126 00 | gfx: Feature level: 11_1
17:04:08.126 00 | gfx: Auto-detected default graphics quality: [High]
17:04:08.126 00 | gfx: ------------------------------------------------
17:04:08.126 00 | gfx:
17:04:08.224 00 | gfx: CreateSwapChain(ModeDesc.Width = 1422, ModeDesc.Height = 693, BufferCount = 2, Flags = 0x802, SwapEffect = FlipSequential)
17:04:12.824 00 ERROR | gfx: DXGI_ERROR_DEVICE_REMOVED: The video card has been physically removed from the system, or a driver upgrade for the video card has occurred.The application should destroy and recreate the device.For help debugging the problem, call ID3D10Device::GetDeviceRemovedReason
17:04:12.824 00 ERROR | gfx: Failed to create swapChain
17:04:12.824 00 ERROR | gfx: Device removed, reason S_OK: No error occurred
17:04:12.824 00 | gfx: Driver threading features:
DriverConcurrentCreates: true
DriverCommandLists: true
17:04:12.826 00 | gfx: Memory Load: 43%
17:04:12.826 00 | gfx: Physical: 13.7 GB total, 5.9 GB used, 7.8 GB available
17:04:12.826 00 | gfx: Page File: 22.2 GB total, 11.3 GB used, 10.9 GB available

try this ?

Try reinstalling DirectX being that you’ve already worked on the drivers.

Is the GPU driver hanging and or thinking the GPU has been removed for whatever reason. The calls are from Direct3D which is part of DirectX

Outside of that try running sfc /scannow just to look for any system file corruption. I run this often when I get odd crashes.

I’ve already tried reinstalling the drivers several times, but unfortunately, there was no change. When I ran the sfc /scannow command, it didn’t find any issues :frowning:

I tried that, and there was no change.

i’m still looking,so what i find i’ll post them here…

here’s another one…

another one…

Did you do the DirectX portion that I mentioned though that’s separate from the drivers.

I couldn’t find how to reinstall DirectX separately in Windows 11.

Thank you for the tips, but I’ve already read that, and I can’t even access the menu to configure anything. I’ve also tried reinstalling the drivers several times.

Sorry not thinking fully… it’s generally build into the system post win10.

Run dxdiag and flip through the pages to see if it detects any problems.

There’s a deeper scan for corruption and issues that can be run:

DISM command with CheckHealth option

The “CheckHealth” option with the DISM tool lets you determine any corruptions inside the local Windows 10 image. However, the option does not perform any repairs.

To check the image of Windows 10 for issues with DISM, use these steps:

  1. Open Start.
  2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.
  3. Type the following command to perform a quick check and press Enter:
    DISM /Online /Cleanup-Image /CheckHealth

Once you complete the steps, the Deployment Image Servicing and Management tool will run and verify any data corruption that may require fixing.

DISM command with ScanHealth option

The “ScanHealth” option performs a more advanced scan to determine whether the image has any problems.

To check image problems with the ScanHealth option on Windows 10, use these steps:

  1. Open Start.
  2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.
  3. Type the following command to perform an advanced DISM scan and press Enter:
    DISM /Online /Cleanup-Image /ScanHealth

After you complete the steps, the scan may take some time to check whether the Windows 10 image needs any fixing.

DISM command with RestoreHealth option

If there are problems with the system image, use DISM with the “RestoreHealth” option to automatically scan and repair common issues.

To repair Windows 10 image problems with the DISM command tool, use these steps:

  1. Open Start.
  2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.
  3. Type the following command to repair the Windows 10 image and press Enter:
    DISM /Online /Cleanup-Image /RestoreHealth

if all this don’t work,then keep trying to install the game with out using steam…( by the way do you use steam? )

DISM /Online /Cleanup-Image /CheckHealth: No component store corruption detected
DISM /Online /Cleanup-Image /ScanHealth: No component store corruption detected
Dxdiag : No issues were detected.

1 Like

The first time, I tried installing the game directly from the website. Then I tried it through Steam, but there was no change.

I’m still pondering over this:
When you were updating your drivers, did you make sure you were picking the “Clean Installation” option?
Did you try the NVIDIA Studio Driver too or just the game ready one? I normally use the Studio Driver and have the card model up from yours.

Look around to see if you have an option for GPU Switching GPU switching - Wikipedia . If it’s on turn it off. This could be could be causing the system to think the cards been disabled and turned back on while loading. Little more on it: Nvidia Optimus - Wikipedia List of Gaming Laptops with MUX Switch & Advanced Optimus - Jarrod's Tech You might have to look in the bios to change it too.

So the story continues. In the BIOS of my laptop, I couldn’t find any option to adjust the MUX Switch. So, I tried disabling the integrated graphics in the Device Manager. After restarting, the screen resolution got messed up to a lower setting, but I decided to launch the game. The game did start, and I managed to get to the menu, but since it was apparently running on the integrated graphics (which I don’t understand because I had disabled it), everything was lagging badly. When I reverted everything back to the original setup, the game crashed immediately again.

I also tried reinstalling the drivers, switching to the Studio ones, but there was no change, so it seems like we might not solve this issue after all. I was thinking about asking on an NVIDIA forum to see if anyone there might have insights into the problem. It’s strange because I have War Thunder from Gaijin, and it works perfectly fine without any issues.

War Thunder and Crossout have different game engines so they would both deal with the same issue differently.

I’d say progress is made though we know for sure that it is the video card that is causing the issue and it’s not like we’ve exhausted the topic of GPU switching. We just don’t know how to turn it off yet.

I would ask on the laptop’s manufacturers support page too. As well as file an issue on crossout’s issue page: Community Bug Reporting System

In the meantime, what’s the laptops model/make? As the GPU switching is normally used for conserving battery power there should be someway of turning it off. However it might be hidden even in the registry if it’s not accessible via the desktop’s GUI.

This is from Dell but has some instructions on how they do their switching:
How to Make Nvidia Card Primary and Enable Switchable Graphics Mode on Dell Laptops | Dell US It might be the same on others.

I tried all the settings in the NVIDIA graphics settings to force the game to run using the NVIDIA graphics card, but nothing worked. What’s strange is that even when I set everything to launch the game through the integrated graphics, the game still wouldn’t start and kept showing the same log indicating that it was trying to launch with the NVIDIA graphics. It only worked when I disabled the integrated graphics in Device Manager, and then the game launched through the integrated graphics without crash.

Notebook model is: VICTUS by HP 16-r0902nc Mica Silver

I happened to spot this which has some of the similar issues within the same family of models:

They were cleaning off the drivers with AutoDDU but the problem kept coming back, so I don’t see that as being a great solution.

I noticed there are lot of these Victus models having similar issues. I went back to relooking at the GPU switching topic. A number of them were saying that their laptops were switching off the GPU during game play and crashing the games so it’s not the same exact issue but it is similar enough.

They were doing the same method of going into Nvidia’s control panel and it wasn’t fixing their switching issue either. At the bottom of that thread there is a command line program for switching the GPU’s globally as someone else wasn’t happy with how their similar switching issue was going: GitHub - reticivis-net/win_global_gpu: A Windows program that sets your preferred GPU globally, manually or automatically I would try this as it sets it globally at registry level