Solved Pc specs for White screen then close on start

This question has been answered or resolved.
maybe there are multiple errors that have the same symptom because for me i was able to fix it by allowing it access via windows defender
1763137286945.png
 
SOLUTION FOUND: It's the CPU, AMD onboard graphics fucking everything up. Did a clean install of NVIDIA and that hadnt fixed it, full update of the onboard graphics drivers did it, along with setting gpu as default.
 
  • Like
Reactions: Allie_Gat0r :3
Faulting application name: KSA.exe, version: 2025.11.4.2791, time stamp: 0x67200000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1706, time stamp: 0x458acb5b
Exception code: 0xc0000602
Fault offset: 0x000000000010fa32
Faulting process id: 0x1890
Faulting application start time: 0x01dc55a9a0c753db
Faulting application path: C:\Program Files\Kitten Space Agency\KSA.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 999d3d84-735c-450c-89da-7296a3a34ace
Faulting package full name:
Faulting package-relative application ID:

I still don't have any logs to see where or what it's failing from. I tried changing the runtime conf to dotnet 8.0 (Lol) and it had the same issue.
Microsoft.NETCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Are currently listed and detected. Weird thing is, the event log doesn't even mention DotNet until I force an error by deleting a Runtime config.
Maybe there's some sort of compatibility option that can be enabled in the compilation, because a *LOT* of computers still run Windows 10, and older revisions due to actually being, ahem, stable or the only option on slightly older devices
 
Last edited:
SOLUTION FOUND: It's the CPU, AMD onboard graphics fucking everything up. Did a clean install of NVIDIA and that hadnt fixed it, full update of the onboard graphics drivers did it, along with setting gpu as default.
Great. I have my iGPU disabled so at least for me it's not that, not surprised it failed with the iGPU, often times Vulkan has weird device order settings/outputs and leads to some programs running on the wrong place