Crash report: BEX64 / SOFTWARE_NX_FAULT_NULL_INVALID_POINTER_EXECUTE

Fixed
AspiringFate [github] · 11 months ago

Issue description

Game consistently crashes within seconds of starting a new save, even after full reinstall, OS upgrade, and driver clean-install.

Game version | v0.7.9 (b495)
Platform | Steam (64-bit)
OS | Windows 11 Pro 23H2 (build 22631.2 / 22621.1)
Hardware | [11900k, 3090, 64GB ram]
Storage location | H:\SteamLibrary\steamapps\common\Captain of Industry
Overlays | None (all disabled)
Clocks | Stock (no OC, XMP disabled)
Antivirus | Windows Defender only
Reinstalled DirectX & VC++ runtimes | ✅ yes
Game reinstalled clean | ✅ yes
Saved data tested | ✅ crashes even on new save

From Windows Reliability Monitor / WinDbg dump analysis:
Problem Event Name: BEX64
Application Name: Captain of Industry.exe
Application Version: 6000.0.50.61213
Exception Code: c0000005
Exception Type: Execute (Access violation)
Fault Module Name: StackHash_2264
Exception Offset: PCH_84_FROM_unknown+0x0000000000000000

WinDbg detailed analysis:
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_NULL_INVALID_POINTER_EXECUTE_c0000005_Captain_of_Industry.exe!unknown_error_in_process
Attempt to execute non-executable address 0000000000000000
PROCESS_NAME: Captain of Industry.exe
MODULE_NAME: Captain_of_Industry
IMAGE_NAME: Captain of Industry.exe
EXCEPTION_CODE: c0000005
EXCEPTION_ADDRESS: 0000000000000000

Interpretation:

The process attempted to execute code at a null memory address (0x0), triggering a DEP (Data Execution Prevention) violation.
This indicates a null function pointer call or JIT execution attempt inside the main executable — no external DLLs (DirectX, GPU driver, etc.) appear in the fault stack.

Notes for Developers

This crash signature points to a software NX fault (null pointer execute) in the main executable, likely within a thread calling into engine-generated code or an uninitialized callback.
No external modules are implicated, so this appears to be an internal engine or script bug, possibly introduced in 0.50.61213.

Reproduction steps

Steps to reproduce:

Launch the game.

Create a new save.

As soon as gameplay starts (e.g., issue first build order or camera move), game crashes to desktop.

Frequency: Every attempt.
Occurs with mods: No (completely clean install).
Occurs in previous versions: Unknown (fresh install).

Game version and build number

v0.7.9 (b495)

Operating system

Windows

Attachments

Player-prev.log, Player.log

2 attachments only for registered users
AspiringFate [github] · 11 months ago

Apparently Riva Statics Tuner was still somehow running in the background even though afterbunner was not and this was the cause of the issue.

Closed as ✅ Fixed

7 Showing 1–2 of 2