X2: Entering Brennans Triumph games crashed

Ask here if you experience technical problems with X³: Reunion, X²: The Threat, X-Tension or X-Beyond The Frontier

Moderators: timon37, Moderators for English X Forum

Xenon_Slayer
EGOSOFT
EGOSOFT
Posts: 11239
Joined: Sat, 9. Nov 02, 12:45
x4

Re: X2: Entering Brennans Triumph games crashed

Post by Xenon_Slayer » Sun, 17. Mar 19, 01:30

It's fine. The save was when you were docked at the Goner Temple and was followed by a long cutscene. I then flew to Brennans Triumph and had the next scene with a Teladi character without a crash. I did see something odd with the cutscene when you enter Brennans Triumph, where it looked like the camera was in the wrong position, but that was all.

I don't think there's anything else right now that I can suggest that Alan hasn't. Verifying the game files via Steam would be my first bet, but I think you said you did that. I can try again on a different system on Monday, but given that others haven't reported this issue, I expect it's something to solve on your side.

Thesamy1993
Posts: 27
Joined: Tue, 26. Feb 19, 19:05

Re: X2: Entering Brennans Triumph games crashed

Post by Thesamy1993 » Sun, 17. Mar 19, 04:20

Okay. I tested also several compabilitys like xp vista windows 8,7 etc. all didnt help. If you have some useful advices what I can still try to do the next days I would rly admire this since Im stucking there and cant do anything. If you need stuff from me still I will provide this for sure.

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 20368
Joined: Fri, 16. Apr 04, 19:21
x4

Re: X2: Entering Brennans Triumph games crashed

Post by Alan Phipps » Sun, 17. Mar 19, 18:04

What about the missing bit of the DxDiag?
A dog has a master; a cat has domestic staff.

Thesamy1993
Posts: 27
Joined: Tue, 26. Feb 19, 19:05

Re: X2: Entering Brennans Triumph games crashed

Post by Thesamy1993 » Sun, 17. Mar 19, 22:20

-------------------------------------
Preferred Media Foundation Transforms
-------------------------------------

[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred]

<media subtype GUID>, [<transform friendly name>, ]<transform CLSID>

{EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}
{E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}
MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
{A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
{73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}
MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
{63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}
MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
{53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}
MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
{3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT
MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT
MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
{33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject
MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject
MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject
MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject
MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}
MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
{30395056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000}
{30385056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000}
MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
{0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}
{00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}
{0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}
{00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}
{00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject
MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}
{00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}
{00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}
WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject
MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject
KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}
{00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}
KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}


-------------------------------------
Disabled Media Foundation Transforms
-------------------------------------

[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse]

<transform CLSID>



------------------------
Disabled Media Sources
------------------------

[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse]

<media source CLSID>


---------------
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 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERACF3.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD13.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD24.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD28.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD48.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_23ecb0cb

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 3481badf-c676-4718-be8c-ee63ece0a0ba
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER1 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA86F.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA89F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8AF.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8B1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8C2.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_1944ac57

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 2c22b242-1187-40bf-98df-3e652c153351
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER2 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3FA.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA41A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA42B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA42B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA44B.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_084ca7d3

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: bc7f7821-9220-43a7-b85b-db9ff759bd59
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER3 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F28.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F67.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F88.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F86.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F96.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_3a3ca36e

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: df2f66b6-af0e-4df3-aaeb-b2ca17b89030
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER4 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F5A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F8A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F8B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F8F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FB0.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_152241eb

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: da374d4b-35ab-4b7b-8980-171b19f54d88
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER5 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C4D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C7D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C90.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CA0.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_18023edd

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: fd01e458-9bbe-433d-bb92-bbabf9cb53f5
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER6 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38C3.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER38F3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3914.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_368e3bc1

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 2554145a-f4c2-42c0-bece-596fdc06b6bc
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER7 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3548.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3588.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35A8.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35C6.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_1c7a3846

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 7970a069-a43c-46d9-bea7-57295c3c004d
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER8 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB13.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB43.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB44.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB48.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB68.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_3583bda3

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 23cd0952-19be-4ee0-8151-0275484ec316
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0
+++ WER9 +++:
Fehlerbucket 1709679018794578923, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: ATKEX_cmd.exe
P2: 0.0.0.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.17134.556
P6: adca2670
P7: 0eedfade
P8: 001118a2
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB75A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB78A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB79A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB79C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7AD.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b8b256b64eae4d332e759d124a9c4b53e9a6ce_3ae784bb_2ec3b9ea

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: c69ce23d-a832-4ca1-9a28-0ce486d1af4f
Berichtstatus: 268435456
Bucket mit Hash: 20c0c9c542260ced87ba0002633073eb
CAB-Datei-Guid: 0

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 20368
Joined: Fri, 16. Apr 04, 19:21
x4

Re: X2: Entering Brennans Triumph games crashed

Post by Alan Phipps » Sun, 17. Mar 19, 23:13

All of your reported crashes are serious ATKEX_cmd.exe KERNELBASE.dll AppCrash issues. That exe is part of an old sound-related suite associated with the ASUS Motherboard Utility and is not essential for gaming sound playback but can cause issues if it is not working, corrupt or unwanted. See if you can find all instances of ATKEX_cmd.exe on your PC and just rename them to something like ATKEX_cmd.old and then see if your games still crash. (If you have an ASUS folder such as C:\Program Files\ASUS ... (HDA maybe) then look in there, otherwise look in the similar folders of Realtek or any other sound devices you have there in Program Files.
A dog has a master; a cat has domestic staff.

Thesamy1993
Posts: 27
Joined: Tue, 26. Feb 19, 19:05

Re: X2: Entering Brennans Triumph games crashed

Post by Thesamy1993 » Sun, 17. Mar 19, 23:39

so the reason for those crashes are in connection with my mainboard right ?
I just have the rename some files and then it works again ? erm okay...

Im rly not a computer nerd so finding these files will be hard for me but ty.

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 20368
Joined: Fri, 16. Apr 04, 19:21
x4

Re: X2: Entering Brennans Triumph games crashed

Post by Alan Phipps » Sun, 17. Mar 19, 23:47

Not quite as you describe, but you have that file ATKEX_cmd.exe from ASUS which is either corrupt or should not be on your computer and is causing applications to crash when it is called by those applications. If you find and rename all the unwanted/broken files of that name then that file cannot be causing the issues in Brennan's Triumph. Of course if renaming them fixes the crashes then great!
A dog has a master; a cat has domestic staff.

Dimushka
Posts: 22
Joined: Tue, 24. Apr 18, 16:11

Re: X2: Entering Brennans Triumph games crashed

Post by Dimushka » Wed, 25. Dec 19, 16:48

[quote=Thesamy1993 post_id=4856152 time=1552858793 user_id=533850]
so the reason for those crashes are in connection with my mainboard right ?
I just have the rename some files and then it works again ? erm okay...

Im rly not a computer nerd so finding these files will be hard for me but ty.
[/quote]

I had had the same problem. So I did start searching and have resolved problem finally. These 2 things I`ve done:
1. I had noticed that my .sav files were not in X2 folder on system disk. They were somewhere in AppData in users folder. So I copied .sav to Program Files 86/X2 and so on.
2. I had started X2 in compatibility mode (with XP SP3) and I had activated 256-color mode.
After that my problem (crashing while entering Brennan`s Triumph) had gone. Good luck, pal, and don`t mind any yokels (this is not about me surely).

P.S. After using compatibility mode your X2 gets admin privileges. So it no longer saves games in AppData but in root folder (system disk/Program Files/X2 and so on). For that reason you should copy your .sav in root (where X2.exe contains).

Alan Phipps
Moderator (English)
Moderator (English)
Posts: 20368
Joined: Fri, 16. Apr 04, 19:21
x4

Re: X2: Entering Brennans Triumph games crashed

Post by Alan Phipps » Wed, 25. Dec 19, 22:12

@ Dimushka: I have no idea why your unaltered saves would be anywhere other than in the game folder as per the X2 FAQ. That said, where your saves are located will only potentially cause gamesave saving or loading issues and will not cause a crash in a specific sector while playing.

The much more likely cause for any resolution of issues is your moving to system administrator status. See the note at the end of this FAQ.
A dog has a master; a cat has domestic staff.

Dimushka
Posts: 22
Joined: Tue, 24. Apr 18, 16:11

Re: X2: Entering Brennans Triumph games crashed

Post by Dimushka » Sat, 28. Dec 19, 09:09

Except original game I have native Russian version, Alan. I bought it 12-13 years ago. It saves where I had written. And what a surprise. I`ve got this problem again in Priest Rings while getting LFL-device. Right after I`d posted previous comment. In last case my method seems to be failing, but I`ve found decision.
1. At first I`ve installed original game version and copied saves. But it still crashed.
2. Yesterday I pulled external GPU (Videocard) out and installed driver for internal (motherboard) one.
3. It still crashed. But then I`ve launched game in compatibility mode right as I`d written above (with XP SP3)... and now it works. I am already about to explore Ore belt`s asteroids. And game doesn`t crash.

I am also to copy my saves in X2 folder manually.
Last edited by Dimushka on Sun, 5. Jan 20, 20:08, edited 5 times in total.

Dimushka
Posts: 22
Joined: Tue, 24. Apr 18, 16:11

Re: X2: Entering Brennans Triumph games crashed

Post by Dimushka » Sat, 28. Dec 19, 09:24

[quote="Alan Phipps" post_id=4904562 time=1577304757 user_id=96461]
@ Dimushka: I have no idea why your unaltered saves would be anywhere other than in the game folder as per [url=https://www.egosoft.com/support/faq/faq ... &version=4]the X2 FAQ[/url]. That said, where your saves are located will only potentially cause gamesave saving or loading issues and will not cause a crash in a specific sector while playing.

The much more likely cause for any resolution of issues is your moving to system administrator status. See the note at the end of [url=https://www.egosoft.com/support/faq/faq ... &version=4]this FAQ[/url].
[/quote]

I have seen more weird things than this. Once upon a time right after getting LFL Saya destroyed her ship because of collision. She`d collided with the west gate. Game had crashed. That time I`d launched script editor, destroyed west gate in Priest Rings via object command. And it helped well. Later I`ve rebuilt gate with other script command.

Post Reply

Return to “X³: Reunion, X²: The Threat, X-T and X-BTF - Technical Support”