XCOM EW crash on in-mission load

[OH72]

Dug out XCOM EW again (fresh install). Installed Mutator Enabler, Sightlines and Commander's Choice Mods. Now I reproducibly have the problem that while I can load saves in base without a problem, any load of an in-mission save results in a crash. Disabling cloud access does nothing, alas. Would appreciate any help.

[dubiousintent]

Please see the wiki article "Troubleshooting Basics - XCOM-EU 2012"; especially the section on "Windows Error Messages". If you are getting a CTD, then you should have a Windows error message as well.

 

-Dubious-

[OH72]

Please see the wiki article "Troubleshooting Basics - XCOM-EU 2012"; especially the section on "Windows Error Messages". If you are getting a CTD, then you should have a Windows error message as well.

 

-Dubious-

Well, my system is running in German, but I assume you'll be able to make sense out of this:

 

Name der fehlerhaften Anwendung: XComEW.exe, Version: 1.0.0.9040, Zeitstempel: 0x531774e6

Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.15063.502, Zeitstempel: 0xc3955624

Ausnahmecode: 0x00000001

Fehleroffset: 0x000eb802

ID des fehlerhaften Prozesses: 0x10cc

Startzeit der fehlerhaften Anwendung: 0x01d31d207b4adcb4

Pfad der fehlerhaften Anwendung: D:\SteamLibrary\steamapps\common\XCom-Enemy-Unknown\XEW\Binaries\Win32\XComEW.exe

Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll

Berichtskennung: 5fa590e3-fabd-4ec7-bc66-a118e7d65eb8

Vollständiger Name des fehlerhaften Pakets:

Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

Name der fehlerhaften Anwendung: XComEW.exe, Version: 1.0.0.9040, Zeitstempel: 0x531774e6

Name des fehlerhaften Moduls: XComEW.exe, Version: 1.0.0.9040, Zeitstempel: 0x531774e6

Ausnahmecode: 0xc0000005

Fehleroffset: 0x00e77ce1

ID des fehlerhaften Prozesses: 0x10cc

Startzeit der fehlerhaften Anwendung: 0x01d31d207b4adcb4

Pfad der fehlerhaften Anwendung: D:\SteamLibrary\steamapps\common\XCom-Enemy-Unknown\XEW\Binaries\Win32\XComEW.exe

Pfad des fehlerhaften Moduls: D:\SteamLibrary\steamapps\common\XCom-Enemy-Unknown\XEW\Binaries\Win32\XComEW.exe

Berichtskennung: 4b135ebf-efd1-4ce4-8b9d-148bf64b1fd5

Vollständiger Name des fehlerhaften Pakets:

Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

These were the two Error-Level events during the last crash, the upper one at 23:33:10 and the lower one at 23:33:28 local time.

There were two information events as well.

At 23:33:28 was this:

 

Fehlerbucket , Typ 0

Ereignisname: APPCRASH

Antwort: Nicht verfügbar

CAB-Datei-ID: 0

Problemsignatur:

P1: XComEW.exe

P2: 1.0.0.9040

P3: 531774e6

P4: KERNELBASE.dll

P5: 10.0.15063.502

P6: c3955624

P7: 00000001

P8: 000eb802

P9:

P10:

Angefügte Dateien:

\\?\C:\Users\ohaus\AppData\Local\Temp\WERA779.tmp.WERDataCollectionStatus.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB0D.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB2D.tmp.txt

Diese Dateien befinden sich möglicherweise hier:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XComEW.exe_369ee9e476fb6d5cee1ff5779ed8ffddd32ddf7_f70ab2b7_19bed898

Analysesymbol:

Es wird erneut nach einer Lösung gesucht: 0

Berichts-ID: 5fa590e3-fabd-4ec7-bc66-a118e7d65eb8

Berichtstatus: 97

Bucket mit Hash:

 

And at 23:33:45 this:

 

Fehlerbucket 73132839866, Typ 1

Ereignisname: APPCRASH

Antwort: Nicht verfügbar

CAB-Datei-ID: 0

Problemsignatur:

P1: XComEW.exe

P2: 1.0.0.9040

P3: 531774e6

P4: XComEW.exe

P5: 1.0.0.9040

P6: 531774e6

P7: c0000005

P8: 00e77ce1

P9:

P10:

Angefügte Dateien:

\\?\C:\Users\ohaus\AppData\Local\Temp\WEREEE2.tmp.WERDataCollectionStatus.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER269.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER289.tmp.txt

Diese Dateien befinden sich möglicherweise hier:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XComEW.exe_b5efd5f08ae3532595d07bc77fce37912e5ffa9_f70ab2b7_09371c48

Analysesymbol:

Es wird erneut nach einer Lösung gesucht: 0

Berichts-ID: 4b135ebf-efd1-4ce4-8b9d-148bf64b1fd5

Berichtstatus: 268435456

Bucket mit Hash: a70c1d4158f87c3da46ce58b5684f6ee

[dubiousintent]

For the first error log message, Google Translation gives:
Ausnahmecode (Exception code): 0x00000001
Pfad des fehlerhaften Moduls (Path of the faulty module): C:\Windows\System32\KERNELBASE.dll

The following are taken from Microsoft responses to similar questions.

This STOP error can occur during startup or at other times. The 8 digit hexadecimal number 0x00000001 translates to the error APC_INDEX_MISMATCH which may be caused by the following:

A kernel-level application or device driver running in kernel mode created a mismatch of thread and asynchronous procedure calls (APC) indexes. This is probably due to a file system mismatch in the number of processes that entered the critical area compared to those that left. Allowing the software to run at this point will corrupt or damage the system.
This could be due to newly added hardware or software issues.
This error can pop up when a CD or DVD is inserted into the drive
This error also happens when the computer uses the Windows Vista Aero color scheme.
Sometimes, when we unlock the computer and login to the default desktop this STOP error shows up.
This STOP error sometimes occurs after the computer transitions into to sleep mode repeatedly (by customer usage).
This problem can also happen in a secure desktop environment (when we lock the computer) where an application has registered an “event hook” using an Application Programming Interface
Problems in the Windows system file win32k.sys can trigger this STOP error.
Memory corruption can also create these conditions.
Too much RAM (> 2GB) may exceed motherboard and BIOS capabilities and create this STOP Error.


Solution:

Verify that all your hardware is compatible with the Vista operating system.
Verify that all the software updates are installed for the current Operating system as well as on all device drivers and external third party software on the system.
If this error showed up when the computer was restarting, go to Step 8. If the computer was operating normally when this error occurred, then continue to Step 4.
Check the “Problem Reports and Solutions” page or VISTA. Click on Start->Control Panel->System and Maintenance->Problem Reports and Solutions. This facility searches online for device driver updates and solutions to problems caused by external hardware or software.
If the error appears during restart (and the restart is successful in spite of the error) , set the Windows Memory Diagnostic to get more details about the problems during restart. Then go to Step 8.

a. Click on Start->All Programs->Accessories. Right-click on Command-Prompt and choose “Run as administrator”
b. Enter mdshed.exe at the command prompt. Schedule the tool to run at the next restart.
Run the Memory Diagnostics Tool on Vista to see if the memory is corrupted. This is a very useful application that can detect memory errors during restarts. To configure this tool:

a. Close all applications.
b. Click on the Start button and in the Search field, type “Memory Diagnostics Tool”.
c. Choose what type of tests you want to run from the options provided.
d. Choose the cache setting for each test and the pass count ( number of times to repeat each test)
e. Set it to run immediately and follow the prompts. Computer restarts.
f. If the tool finds memory errors, it reports it immediately.
Try to restore the system to a previous restore point. Click on the Windows Start button and type “System Restore” into the Search field. The System Restore application comes up. Choose a restore point and continue to restore system.
Try to restart the computer again. If you cannot restart it using the mouse or keyboard options, shut down the computer by pressing down the manual Power button for a few seconds. When the computer has completely shut down, press the button again to restart the computer.
As the computer restarts, press and hold the F8 key before the Windows Logo appears.
Use the arrow keys to select “Repair the computer” in the “Advanced Boot Options” menu.
Choose a keyboard layout and login using username and password. You will need administrator password if it is set on the system. If you have never set it, then just click on “Continue”.
Choose Startup Repair from the menu for “System Recovery Options”. The Startup Repair process will try to repair the computer.
If this does not solve the problem, check the CD-ROM driver and try to install another one. Open up the chassis and check the motherboard. Reseat the memory chips. Check the power supply. If you have testing equipment for the hardware, use them to detect any hardware malfunctions
If none of the above works, you may have to reformat the drive and re-install the operating system.

KERNELBASE.DLL is a system file. Let's diagnose the issue by referring to the following suggestion and check the issue status.

You can try reregistering kernelbase.dll and check if that helps.

a. Click Search and type cmd in start search. Right click on Command Prompt and select Run as Administrator.

b. Type "regsvr32 KERNELBASE.dll" without the quotes and Press Enter.

c. Restart your computer and check

I would also suggest you to perform a "clean boot" and check if it helps.

Clean boot will check if any third party application is causing the issue, as clean boot helps in eliminating software conflicts.

How to troubleshoot problem by performing clean boot in Windows:
http://support.microsoft.com/kb/929135

Note: Once you are done with the troubleshooting, perform the steps in “How to reset the computer to start as usual after troubleshooting with clean boot “to reset computer as usual.

Also suggest you to check the issue status by running "System File Checker tool". Steps referred in the following link are applicable to Windows 10 Technical Preview as well.

Use the System File Checker tool to repair missing or corrupted system files.
http://support.microsoft.com/kb/929833/en-us

For the second error log message, Google Translation gives:
Ausnahmecode (Exception code): 0xc0000005
Pfad des fehlerhaften Moduls (Path of the faulty module): D:\SteamLibrary\steamapps\common\XCom-Enemy-Unknown\XEW\Binaries\Win32\XComEW.exe

This unfortunately too common error indicates an attempt to access memory beyond that allocated to the application. The "Faulting" app is usually the victim of another app which overwrote some of it's instructions, so it is very difficult to track down the actual source of the original error. In this instance "XComEW.exe" is almost certainly the "victim". Please see this article on the "ERRORLIVE" site.

Fixing the first error may solve the second as a by-product.

-Dubious-