Quietgoomba
New Member
Game Version
2026.8.22.5348
Operating System
Windows 10 IoT Enterprise, 22H2 (build 19045)
What Happened
KSA crashes to desktop immediately on launch, every time. Windows Event Viewer shows the process crashing inside KERNELBASE.dll with exception code 0x80131506 (COR_E_EXECUTIONENGINE — a fatal internal .NET/CoreCLR runtime error, not a managed/user-code exception). The crash occurs at the identical fault offset (0x000000000010fb62) across multiple independent launch attempts and after a clean reinstall, indicating a deterministic runtime-level bug rather than a local file/config issue.
No log file is generated — "Documents\My Games\Kitten Space Agency\Logs\" does not exist on this system, so no in-game log is available to attach.
Full Event Viewer entry:
Faulting application name: KSA.exe, version: 2026.8.22.5348, time stamp: 0x6a3e0000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1949, time stamp: 0xcb12e58e
Exception code: 0x80131506
Fault offset: 0x000000000010fb62
Faulting application path: C:\Program Files\Kitten Space Agency\KSA.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
This matches an open upstream .NET runtime bug: dotnet/runtime#122528 ("[.NET 10 runtime internal error with exit code 0x80131506") — described there as "a native crash inside CoreCLR, not a managed exception." If KSA bundles an affected .NET 9/10 build, that would fully explain this crash.
Separately: KSA's own crash-dump collector (Brutal.Monitor.Subprocess.exe) attempted to capture a minidump via createdump.exe. The resulting file in %TEMP% (dump.<PID>.dmp) was correctly named for the crash, but its actual contents belonged to a different process (explorer.exe) — consistent with a PID-reuse race between the crash and dump collection. This dump is not usable for diagnosis and is noted here so it isn't mistaken for a valid crash dump if found elsewhere.
What Was Expected
KSA launches normally to the main menu.
Reproduction Steps
1. Launch KSA.exe (via desktop shortcut or directly from install folder)
2. Game window never appears
3. Process crashes immediately; Windows generates an Application Error event in Event Viewer
Reproduction Rate
Always (100% — reproduced across multiple separate attempts, at the identical fault offset each time)
Additional Info
* Video/Screenshots: None (crash occurs before any window renders)
* Save File: Not applicable — crash occurs before reaching the main menu
* Other Notes:
- System specs: AMD Ryzen 5 5600X3D, AMD RX 6800 XT, 32GB DDR4-3600, ASUS PRIME B550M-A (Wi-Fi)
- Troubleshooting already performed (all unsuccessful, same crash signature persists):
1. Clean reinstall of KSA — ruled out corrupted/partial install files
2. Confirmed running latest available version — ruled out a stale build
3. Forced workstation (non-server) GC via DOTNET_gcServer=0 and DOTNET_GCHeapHardLimit=0 environment variables at launch — no change
4. Checked Windows Defender Controlled Folder Access / AV exclusions and settings.toml permissions — not the blocker here, since this is a runtime crash rather than a launch-blocked/no-log scenario
- OS was recently upgraded in-place from Windows 10 IoT LTSC 2021 to Windows 10 IoT Enterprise 22H2 prior to first encountering this issue, if that's a useful data point
- Happy to test a rollback/pinned runtime build or provide further diagnostics if that would help narrow this down
2026.8.22.5348
Operating System
Windows 10 IoT Enterprise, 22H2 (build 19045)
What Happened
KSA crashes to desktop immediately on launch, every time. Windows Event Viewer shows the process crashing inside KERNELBASE.dll with exception code 0x80131506 (COR_E_EXECUTIONENGINE — a fatal internal .NET/CoreCLR runtime error, not a managed/user-code exception). The crash occurs at the identical fault offset (0x000000000010fb62) across multiple independent launch attempts and after a clean reinstall, indicating a deterministic runtime-level bug rather than a local file/config issue.
No log file is generated — "Documents\My Games\Kitten Space Agency\Logs\" does not exist on this system, so no in-game log is available to attach.
Full Event Viewer entry:
Faulting application name: KSA.exe, version: 2026.8.22.5348, time stamp: 0x6a3e0000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1949, time stamp: 0xcb12e58e
Exception code: 0x80131506
Fault offset: 0x000000000010fb62
Faulting application path: C:\Program Files\Kitten Space Agency\KSA.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
This matches an open upstream .NET runtime bug: dotnet/runtime#122528 ("[.NET 10 runtime internal error with exit code 0x80131506") — described there as "a native crash inside CoreCLR, not a managed exception." If KSA bundles an affected .NET 9/10 build, that would fully explain this crash.
Separately: KSA's own crash-dump collector (Brutal.Monitor.Subprocess.exe) attempted to capture a minidump via createdump.exe. The resulting file in %TEMP% (dump.<PID>.dmp) was correctly named for the crash, but its actual contents belonged to a different process (explorer.exe) — consistent with a PID-reuse race between the crash and dump collection. This dump is not usable for diagnosis and is noted here so it isn't mistaken for a valid crash dump if found elsewhere.
What Was Expected
KSA launches normally to the main menu.
Reproduction Steps
1. Launch KSA.exe (via desktop shortcut or directly from install folder)
2. Game window never appears
3. Process crashes immediately; Windows generates an Application Error event in Event Viewer
Reproduction Rate
Always (100% — reproduced across multiple separate attempts, at the identical fault offset each time)
Additional Info
* Video/Screenshots: None (crash occurs before any window renders)
* Save File: Not applicable — crash occurs before reaching the main menu
* Other Notes:
- System specs: AMD Ryzen 5 5600X3D, AMD RX 6800 XT, 32GB DDR4-3600, ASUS PRIME B550M-A (Wi-Fi)
- Troubleshooting already performed (all unsuccessful, same crash signature persists):
1. Clean reinstall of KSA — ruled out corrupted/partial install files
2. Confirmed running latest available version — ruled out a stale build
3. Forced workstation (non-server) GC via DOTNET_gcServer=0 and DOTNET_GCHeapHardLimit=0 environment variables at launch — no change
4. Checked Windows Defender Controlled Folder Access / AV exclusions and settings.toml permissions — not the blocker here, since this is a runtime crash rather than a launch-blocked/no-log scenario
- OS was recently upgraded in-place from Windows 10 IoT LTSC 2021 to Windows 10 IoT Enterprise 22H2 prior to first encountering this issue, if that's a useful data point
- Happy to test a rollback/pinned runtime build or provide further diagnostics if that would help narrow this down
Upvote
0
