Dear Sir/Madam
Please help. I'm unable to launch X4 collector's edition from Steam. I try to launch the game from Steam and I get a rotating blue windows cursor, followed by a black screen, then a white screen. After about 30 seconds, I get the message "X4: Foundations is not responding". I click "Cancel program" and return to desktop.
I've tried various fixes:
Ran X4 as admin
Deleted X4.exe and re-validated integrity
Restarted steam
Re-installed nvidia drivers
Unchecked read/write permission of user docs and X4 steam files
Created AVG File Shield & Enhanced Firewall exceptions
Checked X4 has access through Windows Firewall
Disabled AVG
Tried looking for and deleting C:\WINDOWS\System32\amd-vulkan64.json - file wasn't there, never used an AMD card previously
Took Thrustmaster T16000M FCS USB out of port
Uninstalled Oculus client
Took Rift USBs and sensors out of port
Disabled Steam overlay
Right clicked on the X4: Foundations folder and checked individual files that "Compress contents to save disk space" was unchecked
Moved Egosoft folder from D:\<Users>\<Profile>\Docs\Egosoft\X4\67821922\config to same drive as where X4 is installed - game launched once, but after changing display settings, X4 locked and I'm back to same issue described above
Other info
Version and language - 1.0 Hotfix 1
Whether or not your game is modified using any third party scripts or mods (see note below) - No
Any possibly relevant changes you have made to your game, system, or software before the issue occurred. - no changes made
Where appropriate, additional symptoms, error messages, links to screenshots and crash dump files (see this FAQ entry) - N/A
Your system specifications in the form of a DxDiag report and vulkaninfo (see this FAQ entry) - See below
Many thanks for your help
DXDIAG / VULKANINFO
------------------
System Information
------------------
Time of this report: 11/30/2018, 18:08:33
Machine name: DESKTOP-ELNEVO6
Machine Id: {91D3A181-9B2D-4AB4-9BF4-C1FDF358D6BA}
Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 0430 (type: UEFI)
Processor: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 CPUs), ~3.7GHz
Memory: 16384MB RAM
Available OS Memory: 16322MB RAM
Page File: 7592MB used, 11162MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode
------------------
System Information
------------------
Time of this report: 11/30/2018, 18:08:33
Machine name: DESKTOP-ELNEVO6
Machine Id: {91D3A181-9B2D-4AB4-9BF4-C1FDF358D6BA}
Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 0430 (type: UEFI)
Processor: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 CPUs), ~3.7GHz
Memory: 16384MB RAM
Available OS Memory: 16322MB RAM
Page File: 7592MB used, 11162MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Input Tab: No problems found.
Midi Renderers:
Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.17134.0001
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.17134.0001
WDM Streaming Capture Devices:
Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
MicIn,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.17134.0001
BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.17134.0001
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.17134.0001
--------------------------------------------
Media Foundation Enabled Hardware Categories
--------------------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT]
EnableDecoders = 1
EnableEncoders = 1
-------------------------------------
Media Foundation Byte Stream Handlers
-------------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers]
[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred]
<file ext. or MIME type>, <handler CLSID>, <brief description>[, Preferred]
--------------------------------
Media Foundation Scheme Handlers
--------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers]
[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred]
---------------
EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)
Quality Flags: 2576
Enabled:
Force throttling
Allow half deinterlace
Allow scaling
Decode Power Usage: 100
Balanced Flags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 50
PowerFlags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 0
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2191901707716452550, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0
I used to have an AMD card in the past before I upgraded to NVidia, which apparently left an old vulkan file on my computer. The message I got after running vulkaninfo from the command prompt was "C:\WINDOWS\System32\amd-vulkan64.json does not have an 'api_version' field".
I deleted the file C:\WINDOWS\System32\amd-vulkan64.json
My game now works.
I started this build in 1999 and upgraded it to play the X games as they were released.
MSI Z87-G45 Motherboard
Water cooled i7 - 4770s
32GB Ballistix Sport Ram
EVGA 1070TI.
Win 10 64bit Pro.
Same problem here. Tried everything, disabling Antivirus, reinstalled, upgraded to new driver etc. Other games are working without problems.
Here is my DXDIAG:
------------------
System Information
------------------
Time of this report: 11/30/2018, 21:13:51
Machine name: BEHEMOTH
Machine Id: {756CEB26-EE35-45EA-878C-6F5524635C07}
Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: German (Regional Setting: German)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 4011 (type: UEFI)
Processor: AMD Ryzen 7 1700 Eight-Core Processor (16 CPUs), ~3.0GHz
Memory: 16384MB RAM
Available OS Memory: 16316MB RAM
Page File: 8373MB used, 10374MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Sound Tab 5: No problems found.
Sound Tab 6: No problems found.
Input Tab: No problems found.
Midi Renderers:
Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.17134.0001
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.17134.0001
WDM Streaming Capture Devices:
Steam Streaming Microphone Wave,0x00200000,2,2,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Steam Streaming Speakers Wave,0x00200000,2,2,ksproxy.ax,10.00.17134.0001
Logitech USB Headset,0x00200000,3,2,ksproxy.ax,10.00.17134.0001
,0x00000000,0,0,,
WDM Streaming Rendering Devices:
AMD HD Audio HDMI out #3,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Steam Streaming Speakers Wave,0x00200000,2,2,ksproxy.ax,10.00.17134.0001
Realtek HDA SPDIF Out,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
Logitech USB Headset,0x00200000,3,2,ksproxy.ax,10.00.17134.0001
Steam Streaming Microphone Wave,0x00200000,2,2,ksproxy.ax,10.00.17134.0001
BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.17134.0001
BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.17134.0001
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.17134.0001
--------------------------------------------
Media Foundation Enabled Hardware Categories
--------------------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT]
EnableDecoders = 1
-------------------------------------
Media Foundation Byte Stream Handlers
-------------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers]
[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred]
<file ext. or MIME type>, <handler CLSID>, <brief description>[, Preferred]
--------------------------------
Media Foundation Scheme Handlers
--------------------------------
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers]
[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred]
---------------
EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)
Quality Flags: 2576
Enabled:
Force throttling
Allow half deinterlace
Allow scaling
Decode Power Usage: 100
Balanced Flags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 50
PowerFlags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 0
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_237bb00b
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 1ca7ccbe-c5fd-4a41-a785-9c95c9457b3d
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER1 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_22e5de30
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 02a8da84-340f-4203-af9d-118ce93bc890
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER2 +++:
Fehlerbucket 1972086429361836388, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 7c77695a-bc80-426b-94b4-0dba061a1a42
Berichtstatus: 268435456
Bucket mit Hash: f26d5ed6e378feefeb5e4228b07b1164
CAB-Datei-Guid: 0
+++ WER3 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_03ddf415
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: b4d8f895-5544-4630-9ce0-90550405db52
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER4 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_2751b1a7
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: fe539eee-6b27-4dda-b189-aba125c08676
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER5 +++:
Fehlerbucket 94588461392, Typ 5
Ereignisname: CLR20r3
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_hpstatusalerts.e_4f38816da72a2545c404d3bee09cfbac21a920_00000000_3df1022d
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 24543936-947d-4d5f-af82-30ec0d9ddcc5
Berichtstatus: 268435456
Bucket mit Hash: e9af05ed67c64ba6b7fe0f2187e51901
CAB-Datei-Guid: 0
+++ WER6 +++:
Fehlerbucket 1400014203542007029, Typ 5
Ereignisname: BEX64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AUEPMaster.exe_5eba38ccd36e6a271e069ed652d15a28e2d36a1_fc159700_2da229da
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: c878f824-52f2-4d39-b223-b83375777224
Berichtstatus: 268435456
Bucket mit Hash: 22e3be32896cead3d36dd980229f6cf5
CAB-Datei-Guid: 0
+++ WER7 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_0bdc82c5
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: caf8d3b1-91af-4658-a061-fd274f506973
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER8 +++:
Fehlerbucket 2191901707716452550, Typ 5
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_3e6fbff0c2f3762b4b4036e32cda1a6e904fe7_5581dddc_163bde09
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 02de6cb7-8a5e-4dbe-99c8-531fd969d5dc
Berichtstatus: 1
Bucket mit Hash: 9e544b020da28b440e6b32fd6f02e0c6
CAB-Datei-Guid: 0
+++ WER9 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_X4.exe_ace5a658c0dfea14453a6e50d52178896e68e0d_9175a884_699e2f50
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: a917d27e-5d4d-4ab5-81f7-ee309ec633be
Berichtstatus: 97
Bucket mit Hash:
CAB-Datei-Guid: 0
Dear Support
Have you got a suggested solution to this problem that I and many others are having please? 15 hours since launch and still unable to launch the game.
CBJ wrote: ↑Sat, 1. Dec 18, 10:00
Do either of you have any crashdump (.dmp) files in your game folder? If so, please send them to crash@egosoft.com along with a link to this thread.
Another thing to check is whether your drive or game folder is compressed. If so then try switching this off.
Thanks for the reply. There are no .dmp files in any X4 folders or anything that looks like a crashlog. X4 seems to just hang, rather than crash. In fact it stops responding.
As per my OP, I've already checked folder/file compression and neither are compressed. I also checked my SSD.
EDIT
Might have a potential solution. In this Steam thread (https://steamcommunity.com/app/392160/d ... 083992443/)
- Adam says this "I noticed that the game will crash on launch if you install on a different drive than the C:// drive".
Spyware says this - For those of you having the problem where you start the game, it doesn't crash but hangs on a black screen, then turns white and you have to close the application using the "Application not responding" windows dialog:
Mine started working when my Documents folder (where X4 saves its config) was on the same drive as the game installation.
My Docs folder was on D: and my game folder was on C:. Moved the game folder to D: and it loaded right up. If you have a similar setup, this may be why your game won't start.
My Steam account is installed on my D drive and my docs on C. If only my C drive was big enough for my Steam games. Perhaps a solution is to refund on Steam and buy on GoG or wait for a hotfix from Egosoft
Unfortunately I don't think moving it from the D drive to the C drive will help in and of itself. I too run the game from the D drive, and it's fine that way. The only way it might help if there is some other issue with the specific drive it's on (such as the compression thing, which seems to cause exactly the symptoms you describe) that isn't then the case on the drive you move it to.
CBJ wrote: ↑Sat, 1. Dec 18, 10:45
Unfortunately I don't think moving it from the D drive to the C drive will help in and of itself. I too run the game from the D drive, and it's fine that way. The only way it might help if there is some other issue with the specific drive it's on (such as the compression thing, which seems to cause exactly the symptoms you describe) that isn't then the case on the drive you move it to.
Thanks again for the reply. I've triple checked both my SSDs and neither have any sort of compression ticked.
Funny thing though, I just moved my Egosoft docs folder to my D drive and the game launched! From the main menu I changed the display settings to Ultra, the menu disappeared, the music kept playing, the X4 splash screen still showed, my FPS counter still moved a little, but the game stopped responding. I had to End task. Now when I boot up again, I go back to the same issue I had from the OP.
That really does sound like something interfering with the game's access to the files it needs, but I'm struggling to think what if it's not compression and it's not AV software.
CBJ wrote: ↑Sat, 1. Dec 18, 12:24
That really does sound like something interfering with the game's access to the files it needs, but I'm struggling to think what if it's not compression and it's not AV software.
What is the path that X4 needs access to for the config file please?
Before I moved it, it was: C:\Users\zarra\Documents\Egosoft\X4\67821922. Now I've moved the file it is D:\Egosoft\X4\67821922
EDIT
I've changed the path to D:\Users\zarra\Documents\Egosoft\X4\67821922, but still doesn't work. Same issue as described in OP. Going to have a break from trying to fixing it now, getting a tiny bit wound up
Last edited by zarrazee on Sat, 1. Dec 18, 13:21, edited 1 time in total.
I have one SSD splitted into two partitions C:\ (System) and E:\ (Data). Drive D:\ is my DVD ROM-Drive.
My user data is on E:\; the Config.xml was created correctly (even as the game was crahsing). I've dinstalled X4, created a new game library on C:\ and re-installed X4. Now it's starting, I can create a new game and save. Also quitting and starting it again works.
@Egosoft: You really messed up something here. File access shoulöd work regardless where you install the game in