Affects Version/s: 1.0
Fix Version/s: None
You landed on this page because we have detected a crash in "X4 - Foundations".
It's likely the crash occurred due to some issues between the game engine and your graphics card.
Common solutions which might help in such a case:
For NVIDIA graphics cards, make sure to upgrade drivers to 385.41 or later.
For AMD graphics cards, upgrade drivers to 17.9.1 or later.
On Windows 8.1 the 17.9.1 drivers are officially not supported by AMD. If you run Windows 8.1 you should use the AMD drivers 17.7.1 instead.
On Windows 8 the 17.7.1 drivers are not supported either. We recommend to upgrade to Windows 8.1 instead (which is free for all Windows 8 installations).
Also try out the latest optional drivers, if the current stable version doesn't work for you.
If you switched the graphics card in your system (for example replacing an AMD card with an NVIDIA card), you are STRONGLY encouraged to double check that there are no left-overs from the other graphics card's drivers. Verify that all old drivers of the removed card have been cleanly uninstalled from your system (i.e. check Windows' add/remove programs list and verify also that no left over Vulkan runtime installations exists from the old drivers). If in doubt, we suggest to perform a clean reinstallation of the graphics card drivers as explained on this page.
In some cases the Vulkan runtime installation can be broken. To check whether this is the case, simply run vulkaninfo from a command line. If you get the output that the command could not be found, please double check the graphics card drivers. All supported cards/drivers are providing the command and if it's reported as missing, you most likely don't have the drivers installed correctly on your machine.
If the output just displays a header like this (note that the reported version number might differ)
Unable to render embedded object: File (vulkaninfo-header.png) not found.
the vulkan installation is most likely corrupted on your machine. Try to do a clean installation of your graphics card drivers and the Vulkan runtime as described on this page.
We are aware of some drivers (especially older ones) having issues when trying to run together with later Vulkan runtime versions. In general we suggest that the Vulkan runtime installed alongside the graphics card drivers is used.
There are two ways to resolve the issue:
- Try installing the latest drivers as suggested in the previous step.
- If installing the latest drivers is not an option for you (or doesn't solve the issue), verify that you have installed the proper Vulkan runtime for your drivers. To do that:
- uninstall the current graphics drivers
- go to "Add and Remove programs" in Windows and look for any installed instance of a Vulkan runtime - uninstall all of these
- restart the machine
- verify that there's no remaining vulkan-1.dll in your Windows' system32 directory
- install your intended graphics card driver version
- restart the machine
Vulkan runtime issue with NVIDIA graphics cards if an AMD card was previously installed in the same system
In certain cases there can be an issue with the Vulkan runtime, if on a machine the AMD drivers 17.7.1 (or older) were previously installed and later on the AMD graphics card was replaced with an NVIDIA card. To verify that you are impacted by this issue, first follow these steps:
- Open a command prompt in Windows
- Enter vulkaninfo
- Verify that at the top of the output the following line exists:
WARNING: [Loader Message] Code 0 : loader_icd_scan: ICD JSON C:\WINDOWS\System32\amd-vulkan64.json does not have an 'api_version' field.
Only if such a line exists AND you DON'T have an AMD card installed in your machine, you are impacted by the issue and can perform the following steps at your own risk!
In the Windows/System32 directory check for an amd-vulkan64.json file and move it outside the system32-directory (so to keep a backup of the file, in case you need to restore it).
Be careful with these instructions. Messing around with Windows system files can be dangerous and result in an unbootable machine.
Also we don't recommend following this approach, if you still have an AMD card installed in the system. In such a case, upgrading the current drivers should fix the issue without any risks.
Note that in such cases it's acceptable that the vulkaninfo issues the warning stated above. This can be ignored.
If your computer has more than a single graphics card, try disabling the one which you don't want to use with the game (f.e. an integrated Intel graphics card if your system has a more powerful NVIDIA/AMD graphics card installed as well).
If you were presented with a "Fatal Error"-popup stating that something "Failed with err -4", then you are running into the so called: "lost device" issue.
Technically this means that the graphics card is resetting and the game lost access to the card.
There are multiple possible causes for such an issue. It's possible that there's an issue between the monitor and the graphics card (if you have multiple monitors attached to the card, see if only connecting a single monitor solves the issue).
It's also possible if there's unstable hardware involved (also a potential overheating graphics card). Try to reduce the game graphic settings and see if this circumvents the crash.
If you were presented with a "Fatal Error"-popup stating that "Vulkan::CreateMemoryHeaps() Couldn't allocate heap [...]" then you might try to run the game on a machine with hardware which is below our minimum specs. In particular this seems to happen with certain types of AMD APUs.
If you want to help us to provide further details and verify that you are indeed running into this issue, please send the following details to firstname.lastname@example.org with the Subject: "X4-2 - CreateMemoryHeaps":
- a screenshot of the popup the game presented
- your dxdiag (this page explains how to retrieve it: https://www.egosoft.com:8444/confluence/display/X4WIKI/Retrieving+DXDiag+and+VulkanInfo)
We identified a regression in 3.0 which triggers this crash. This only applies to, if the crash window states the following error: "[IDBase::AssignNewID] Failed to assign an ID to the object.". A fix for this particular issue was shipped with 3.20 Beta 1.
Try to remove the config.xml file located in the "My documents" folder under Egosoft\X4.
- the crash occurs, if you update the graphics card drivers while the game is running
In 3.10 we improved the game's error handling to better identify certain crashes/start up problems. As of today (2020-05-25) players running X4 3.10HF1 or later and are suffering a specific problem related to the Vulkan runtime are now presented with a different troubleshooting page here and are no longer taken to this generic crash/startup issue page.
If you previously failed to start the game, please try it once more and if you get directed to the new page now, follow the instructions pointed out there for further support.
As of 3.20 Beta 2 Hotfix 1, these types of crashes which previously all redirected to this generic troubleshooting page, now redirect to more specific pages. This no longer causes the current confusion of mixing up completely independent crashes with one another and should significantly help to identify what is going wrong.
In addition to that, a bug was fixed which resulted in this troubleshooting page not being opened in the webbrowser, if the game was running in fullscreen mode.