its not letting me upload the .ckan file
#Keeps crashing after ~2 hrs of gameplay and ~20 spacecraft loads of varying complexities
calm stone
let me copy my system config
Device name Galahad
Processor AMD Ryzen 7 5800XT 8-Core Processor (4.20 GHz)
Installed RAM 64.0 GB
Graphics card NVIDIA GeForce RTX 5060 (8 GB)
Storage 887 GB of 2.73 TB used
Device ID (HAHA NO)
Product ID (HAHA NO)
System type 64-bit operating system, x64-based processor
Pen and touch Pen and touch support with 2 touch points
CPU/GPU inbalance has been ruled out
stone pumice
sweet mica
Yeah, check your logs. Hardware specs don't help much... it's 99% a mod problem
calm stone
t'was a mod issue, I coded a program to fix it!
Wait, no it was not
It was a Direct3D issue
answer from Claude because im too dumb for this
The Crash: D3D11 Access Violation
The game hit a hard crash in d3d11.dll — specifically inside D3DKMTOpenResource. This is a Direct3D 11 kernel-mode call that opens a shared GPU resource. The crash was a null pointer dereference (it tried to read from address 0x00000000000000C9, which is essentially null + a small offset).
What likely caused it
The crash trace points to D3DKMTOpenResource → UnityPlayer graphics code → BuiltinRuntimeReflectionSystem.TickRealtimeProbes(). That last one is Unity's reflection probe update system — it renders environment reflections. Something in KSP's Unity renderer tried to access a GPU resource that had already been freed or was invalid, and d3d11 blew up.
There's also a notable detail in the thread list: Windhawk (a Windows system modification tool) has a hook running inside KSP's process. That's the GlobalHookSessionStart entry in Thread 43712. Windhawk injects into all processes by default, and while it's usually harmless, it can occasionally interfere with DirectX calls or cause instability in games.
Also spotted: the crash metadata confirms you're running KSP 1.12.4 on your RTX 5060, which is a very new GPU. The driver support for KSP's old Unity 2019.4 engine + DX11 can be shaky on the latest Nvidia drivers.
end of Claude response
Likely it's Windhawk, but it could be Scatterer and/or EVE
I found the issue so I'm gonna mark this thread as SOLVED but I'm going to find what exactly caused this and write a full report for ppl to use later
calm stone
Summary:
After a couple hours of gameplay and multiple launches & spacecraft loads, my game crashes with the screen we all know and hate. The classic "ubuntucrashmanager.exe" "Kerbal Exclamation of Death" (KEoD) if it hasn't been coined already, I have now coined that term.
This issue was caused by a mix of issues that led to a D3D11 Access Violation (details above). These issues include GFX reflection mods like Scatterer and EVE, Windows 11 modification program Windhawk, and an overarching support issue between Kerbal and Nvidia 50-series GPUs and Drivers. As of May 19, 2026 (which was <t:1779166800:R> as of now (adapted from CDT)), the latest Game Ready driver causes no immediate issues, however the previous driver may cause Kerbal to crash on startup.
The solution:
As of <t:1779166800:R> there is no easy way to truly fix this problem besides trying to uninstall GFX mods and Windhawk mods (none of us like doing that). I will, however, report back here with more info if I do find one
I will attempt to paste the log file from the crash below. Happy lithobraking!